diff --git a/core/src/main/resources/hudson/triggers/SCMTrigger/help.html b/core/src/main/resources/hudson/triggers/SCMTrigger/help.html index 0f877c77da93eb7c06fe143266fc1379f6e681e4..6b4ce05d44453bdbfd4eef3d1bab578c84261079 100644 --- a/core/src/main/resources/hudson/triggers/SCMTrigger/help.html +++ b/core/src/main/resources/hudson/triggers/SCMTrigger/help.html @@ -1,9 +1,9 @@
Note that this is going to be an expensive operation for CVS, as every polling - requires Hudson to scan the entire workspace and verify it with the server. + requires Jenkins to scan the entire workspace and verify it with the server. Consider setting up a "push" trigger to avoid this overhead, as described in this document -
Bedenken Sie, dass dies für das Versionsverwaltungssystem CVS eine äußerst - ressourcenintensive Operation darstellt, da Hudson bei jeder Abfrage den + ressourcenintensive Operation darstellt, da Jenkins bei jeder Abfrage den kompletten Arbeitsbereich überprüfen und mit dem CVS-Server abgleichen muß. Ziehen Sie daher alternativ einen "Push"-Auslöser in Betracht, wie er in diesem Dokument beschrieben wird. -
Notez que cette opération est consommatrice de ressources pour CVS, - car chaque scrutation signifie que Hudson va scanner l'ensemble du + car chaque scrutation signifie que Jenkins va scanner l'ensemble du workspace et le comparer avec le serveur. Envisagez d'utiliser un trigger de type 'push' pour éviter cette surcharge, comme décrit dans ce document. -
- ポーリング毎に、Hudsonはワークスペースをスキャンしてサーバーと検証する必要があるので、 + ポーリング毎に、Jenkinsはワークスペースをスキャンしてサーバーと検証する必要があるので、 CVSにとって負荷の高い操作ということに注意してください。 このオーバーヘッドを避けるために、 このドキュメントにあるように、 "push"トリガーの設定を検討してください。 - \ No newline at end of file + diff --git a/core/src/main/resources/hudson/triggers/SCMTrigger/help_pt_BR.html b/core/src/main/resources/hudson/triggers/SCMTrigger/help_pt_BR.html index fdc722b74cf5512e081ff41ca51c0ba6d13a04b7..3b215a115f056e07ab990ee3e45acb3738b49c44 100644 --- a/core/src/main/resources/hudson/triggers/SCMTrigger/help_pt_BR.html +++ b/core/src/main/resources/hudson/triggers/SCMTrigger/help_pt_BR.html @@ -1,9 +1,9 @@
Note que isto vai ser uma operação custosa para o CVS, como toda consulta - requer que o Hudson examine o workspace inteiro e verifique-o com o servidor. + requer que o Jenkins examine o workspace inteiro e verifique-o com o servidor. Considere configurar um disparador de construção periódico ("Construir periodicamente") para evitar esta sobrecarga, como descrito nesta documentação
Обратите внимание, что эта операция вызывает достаточно высокую нагрузку @@ -7,4 +7,4 @@ сверка содержимого с данными на сервере. Лучшим вариантом будет настройка вашей SCM на инициацию сборки при внесении в неё изменений, как описано в этом документе. -
- Unutmayın, bu işlem CVS için biraz yüklü olacaktır, çünkü her kontrolde Hudson tüm çalışma alanını + Unutmayın, bu işlem CVS için biraz yüklü olacaktır, çünkü her kontrolde Jenkins tüm çalışma alanını tarayacak ve bunu CVS sunucusu ile karşılaştıracaktır. Bunun yerine bu dokümanda anlatıldığı gibi "push" tetikleyicisini ayarlayın. -
- This feature is primarily for using Hudson as a cron replacement, + This feature is primarily for using Jenkins as a cron replacement, and it is not ideal for continuously building software projects. When people first start continuous integration, they are often so used to @@ -11,9 +11,9 @@ this feature. However, the point of continuous integration is to start a build as soon as a change is made, to provide a quick feedback to the change. To do that you need to - hook up SCM change notification to Hudson.. + hook up SCM change notification to Jenkins..
So, before using this feature, stop and ask yourself if this is really what you want. - \ No newline at end of file + diff --git a/core/src/main/resources/hudson/triggers/TimerTrigger/help_de.html b/core/src/main/resources/hudson/triggers/TimerTrigger/help_de.html index dfce7a9984b0c5617685690763ddee4a867f9b0d..01515ec9f412202143747b71f2c8ef7f62cf9a10 100644 --- a/core/src/main/resources/hudson/triggers/TimerTrigger/help_de.html +++ b/core/src/main/resources/hudson/triggers/TimerTrigger/help_de.html @@ -13,9 +13,9 @@ sobald eine Änderung im Code vorgenommen wurde, um möglichst schnell eine Rückmeldung zu bekommen. Dazu müssen sie eine Änderungsabfrage (SCM change - notification) in Hudson einrichten. + notification) in Jenkins einrichten.
Bevor Sie also dieses Merkmal nutzen, halten Sie kurz inne und fragen Sie sich, ob dies wirklich das ist, was Sie eigentlich wollen. - \ No newline at end of file + diff --git a/core/src/main/resources/hudson/triggers/TimerTrigger/help_fr.html b/core/src/main/resources/hudson/triggers/TimerTrigger/help_fr.html index f4ae804b49ab2625d50f204d43f737d9baece875..b86f236ba50cf9a43b053beea3dc57d97dd4a1e5 100644 --- a/core/src/main/resources/hudson/triggers/TimerTrigger/help_fr.html +++ b/core/src/main/resources/hudson/triggers/TimerTrigger/help_fr.html @@ -4,7 +4,7 @@ afin d'exécuter le projet périodiquement.
- Cette fonction est prévue principalement pour utiliser Hudson comme un + Cette fonction est prévue principalement pour utiliser Jenkins comme un remplacement de cron. Elle n'est pas faite pour la construction continue de projets logiciel. @@ -15,9 +15,9 @@ chaque changement dans la base de code, afin de donner un retour rapide sur ce changement. Pour cela, vous devez - associer la notification des changements de l'outil de gestion de version à Hudson.. + associer la notification des changements de l'outil de gestion de version à Jenkins..
Donc, avant d'utiliser cette fonctionnalité, demandez-vous si c'est bien ce que vous voulez faire. - \ No newline at end of file + diff --git a/core/src/main/resources/hudson/triggers/TimerTrigger/help_ja.html b/core/src/main/resources/hudson/triggers/TimerTrigger/help_ja.html index 918a5b4638688b3c9d254b3989802bf2eee5ef7a..4aaeba320487eea02194299f11cdaaee23938310 100644 --- a/core/src/main/resources/hudson/triggers/TimerTrigger/help_ja.html +++ b/core/src/main/resources/hudson/triggers/TimerTrigger/help_ja.html @@ -2,7 +2,7 @@ このプロジェクトを定期的に実行するクーロンのような機能を提供します。
- この機能は、クーロンの代替品としてHudsonを使用するのが第一なので、 + この機能は、クーロンの代替品としてJenkinsを使用するのが第一なので、 プロジェクトの継続的なビルドに使用するのは、望ましくありません。 継続的インテグレーションのやりはじめの頃は、 @@ -10,9 +10,9 @@ この機能を使用します。しかしながら、継続的インテグレーションのポイントは、 変更したらすぐにビルドを開始し、変更へのフィードバックをすばやくすることです。 そうするには、 - SCMの変更通知をHudsonに中継する必要があります。 + SCMの変更通知をJenkinsに中継する必要があります。
上記の通り、この機能を使用する前に、この機能が本当にあなたが必要とするものなのか、 考えてみてください。 - \ No newline at end of file + diff --git a/core/src/main/resources/hudson/triggers/TimerTrigger/help_pt_BR.html b/core/src/main/resources/hudson/triggers/TimerTrigger/help_pt_BR.html index 6d8bc727fbd4ebb5edd8a34767a1ba091b62b723..aac4c5db34882464a27231690783a6f326b9b123 100644 --- a/core/src/main/resources/hudson/triggers/TimerTrigger/help_pt_BR.html +++ b/core/src/main/resources/hudson/triggers/TimerTrigger/help_pt_BR.html @@ -3,7 +3,7 @@ para periodicamente executar este projeto.
- Esta funcionalidade é para usar o Hudson no lugar do cron, + Esta funcionalidade é para usar o Jenkins no lugar do cron, e não é ideal para projetos de software de construção contínua. Quando as pessoas iniciam na integração contínua, elas frequentemente são levadas @@ -11,7 +11,7 @@ usam esta funcionalidade. Porém, o ponto principal da integração contínua é iniciar uma construção tão logo uma mudança seja feita, para fornecer um feedback rápido sobre a mudança. Para fazer isto você precisa - ligar a notificação de mudança do SCM ao Hudson.. + ligar a notificação de mudança do SCM ao Jenkins..
Assim, antes de usar esta funcionalidade, pare e pergunte a si mesmo se isto é o que realmente você quer. diff --git a/core/src/main/resources/hudson/triggers/TimerTrigger/help_ru.html b/core/src/main/resources/hudson/triggers/TimerTrigger/help_ru.html index d5657d4eeda7f6c91ee5b4735214ca6a627620c9..574e3cf648d00d37e3143b2b0bb3e86e6acc410e 100644 --- a/core/src/main/resources/hudson/triggers/TimerTrigger/help_ru.html +++ b/core/src/main/resources/hudson/triggers/TimerTrigger/help_ru.html @@ -3,7 +3,7 @@ 㪠 ᯨᠭ ᡮப .
- 㭪 ᭮ 㦭 ᯮ짮 Hudson ⢥ + 㭪 ᭮ 㦭 ᯮ짮 Jenkins ⢥ cron, 稬 ࠧ 室 ਮ ᡮન ⮢. 짮⥫ ⠫ 楯樥 뢭 ⥣樨 @@ -13,11 +13,11 @@ ᥭ , ண 祭 १ ࠧࠡ稪. - ⮡ Hudson 뫮 ⠪, ன + ⮡ Jenkins 뫮 ⠪, ன 饭 SCM.
, । ⥬ ᯮ짮 㭪, ⠭ ᥡ, ⢨⥫쭮 ⮣. - \ No newline at end of file + diff --git a/core/src/main/resources/hudson/triggers/TimerTrigger/help_tr.html b/core/src/main/resources/hudson/triggers/TimerTrigger/help_tr.html index 7bd057c5087c65a8d50685f1b1727049fc4fc100..68b87b9cc73455e30123e6e52c7fc4e7fa3b7b50 100644 --- a/core/src/main/resources/hudson/triggers/TimerTrigger/help_tr.html +++ b/core/src/main/resources/hudson/triggers/TimerTrigger/help_tr.html @@ -3,16 +3,16 @@ gibi çalıştırabilmeyi sağlar.
- Hudson'ı cron'un alternatifi olarak kullanmak için tasarlanmıştır ve kesinlikle + Jenkins'ı cron'un alternatifi olarak kullanmak için tasarlanmıştır ve kesinlikle sürekli yapılandırılan yazılım projeleri için değildir. Sürekli entegrasyon metodu olarak, düzenli gecelik/haftalık yapılandırmalar planlanabilir. Bu özellik de bu amaç için kullanılabilse de, sürekli entegrasyonun asıl noktasının herhangi bir değişiklik olur olmaz yapılandırmanın başlatılması olduğu ve bu değişikliğe ait geri bildirimin çabucak verilmesi gerektiği unutulmamalıdır. - Bunun için SCM değişikliklerini Hudson'a bildirecek mekanizmanın + Bunun için SCM değişikliklerini Jenkins'a bildirecek mekanizmanın ayarlanması gerekir.
Yani, bu özelliği kullanmadan önce yapmak istediğinizin bu yöntem ile mi yapılması gerektiğini sorgulayın. - \ No newline at end of file +