diff --git a/core/src/main/resources/hudson/triggers/SCMTrigger/help.html b/core/src/main/resources/hudson/triggers/SCMTrigger/help.html index 6b4ce05d44453bdbfd4eef3d1bab578c84261079..bc1da6300c4f5c9be917a73a2cff23b72736803a 100644 --- a/core/src/main/resources/hudson/triggers/SCMTrigger/help.html +++ b/core/src/main/resources/hudson/triggers/SCMTrigger/help.html @@ -5,5 +5,5 @@ Note that this is going to be an expensive operation for CVS, as every polling 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 + this document diff --git a/core/src/main/resources/hudson/triggers/SCMTrigger/help_de.html b/core/src/main/resources/hudson/triggers/SCMTrigger/help_de.html index e1003ac119e2376b8d1b27c422b32bd14e798d78..c0bfa8607983cafdc2e4239ef60de48583966ae7 100644 --- a/core/src/main/resources/hudson/triggers/SCMTrigger/help_de.html +++ b/core/src/main/resources/hudson/triggers/SCMTrigger/help_de.html @@ -7,6 +7,6 @@ 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 + diesem Dokument beschrieben wird. diff --git a/core/src/main/resources/hudson/triggers/SCMTrigger/help_fr.html b/core/src/main/resources/hudson/triggers/SCMTrigger/help_fr.html index 9532f449b5bfe6fac4742e8b083ddeb26b074267..e8a9b9c1d2d031d277b1590f84bc7c412575beb0 100644 --- a/core/src/main/resources/hudson/triggers/SCMTrigger/help_fr.html +++ b/core/src/main/resources/hudson/triggers/SCMTrigger/help_fr.html @@ -8,5 +8,5 @@ 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. + ce document. diff --git a/core/src/main/resources/hudson/triggers/SCMTrigger/help_ja.html b/core/src/main/resources/hudson/triggers/SCMTrigger/help_ja.html index 3b12aec40626f399feb405b7c9aa7f6a40d0262a..4be674d0a0bee2243d1ae5ca31f24c418cf92ac2 100644 --- a/core/src/main/resources/hudson/triggers/SCMTrigger/help_ja.html +++ b/core/src/main/resources/hudson/triggers/SCMTrigger/help_ja.html @@ -5,6 +5,6 @@ ポーリング毎に、Jenkinsはワークスペースをスキャンしてサーバーと検証する必要があるので、 CVSにとって負荷の高い操作ということに注意してください。 このオーバーヘッドを避けるために、 - このドキュメントにあるように、 + このドキュメントにあるように、 "push"トリガーの設定を検討してください。 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 3b215a115f056e07ab990ee3e45acb3738b49c44..ffbfbca42fdcdd75fd9daa2588cce257e84315b4 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 @@ -5,5 +5,5 @@ Note que isto vai ser uma operação custosa para o CVS, como toda consulta 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 + nesta documentação diff --git a/core/src/main/resources/hudson/triggers/SCMTrigger/help_ru.html b/core/src/main/resources/hudson/triggers/SCMTrigger/help_ru.html index 1eee239e08b9cedf9f34269134c8adf418a0a863..9b3a4a550f634c711f48bcd82d90c5f4d0ac2592 100644 --- a/core/src/main/resources/hudson/triggers/SCMTrigger/help_ru.html +++ b/core/src/main/resources/hudson/triggers/SCMTrigger/help_ru.html @@ -6,5 +6,5 @@ на SCM, так как каждый опрос представляет собой сканирование сборочной директории и сверка содержимого с данными на сервере. Лучшим вариантом будет настройка вашей SCM на инициацию сборки при внесении в неё изменений, как описано - в этом документе. + в этом документе. diff --git a/core/src/main/resources/hudson/triggers/SCMTrigger/help_tr.html b/core/src/main/resources/hudson/triggers/SCMTrigger/help_tr.html index 7f9dd35d8a641a404c2bf0d5b359ec802c28e724..a03b8733d05e66e2b84090032fc3cd248e0236a9 100644 --- a/core/src/main/resources/hudson/triggers/SCMTrigger/help_tr.html +++ b/core/src/main/resources/hudson/triggers/SCMTrigger/help_tr.html @@ -4,6 +4,6 @@

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 + Bunun yerine bu dokümanda anlatıldığı gibi "push" tetikleyicisini ayarlayın. diff --git a/core/src/main/resources/hudson/triggers/TimerTrigger/help.html b/core/src/main/resources/hudson/triggers/TimerTrigger/help.html index efc2ec0a3beba304189ac342359cfcb38e6ba8b7..6c1966041d4c13a4354ab23d2a67db64af0f711c 100644 --- a/core/src/main/resources/hudson/triggers/TimerTrigger/help.html +++ b/core/src/main/resources/hudson/triggers/TimerTrigger/help.html @@ -11,7 +11,7 @@ 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 Jenkins.. + hook up SCM change notification to Jenkins..

So, before using this feature, stop and ask yourself if this is really what you want. 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 01515ec9f412202143747b71f2c8ef7f62cf9a10..24e6c7f2335182a81c356e321610139f384a4181 100644 --- a/core/src/main/resources/hudson/triggers/TimerTrigger/help_de.html +++ b/core/src/main/resources/hudson/triggers/TimerTrigger/help_de.html @@ -12,7 +12,7 @@ kontinuierlichen Integration liegt jedoch darin, einen neuen Build zu starten, sobald eine Änderung im Code vorgenommen wurde, um möglichst schnell eine Rückmeldung zu bekommen. Dazu müssen sie eine - Änderungsabfrage (SCM change + Änderungsabfrage (SCM change notification) in Jenkins einrichten.

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 b86f236ba50cf9a43b053beea3dc57d97dd4a1e5..9375f214a887e5b6bebe0135a99becb0095894c7 100644 --- a/core/src/main/resources/hudson/triggers/TimerTrigger/help_fr.html +++ b/core/src/main/resources/hudson/triggers/TimerTrigger/help_fr.html @@ -15,7 +15,7 @@ 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 à Jenkins.. + 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 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 4aaeba320487eea02194299f11cdaaee23938310..301b2379ab703d74ccabce9f41494c0cb7a23856 100644 --- a/core/src/main/resources/hudson/triggers/TimerTrigger/help_ja.html +++ b/core/src/main/resources/hudson/triggers/TimerTrigger/help_ja.html @@ -10,7 +10,7 @@ この機能を使用します。しかしながら、継続的インテグレーションのポイントは、 変更したらすぐにビルドを開始し、変更へのフィードバックをすばやくすることです。 そうするには、 - SCMの変更通知をJenkinsに中継する必要があります。 + SCMの変更通知をJenkinsに中継する必要があります。

上記の通り、この機能を使用する前に、この機能が本当にあなたが必要とするものなのか、 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 aac4c5db34882464a27231690783a6f326b9b123..b83f673b38e8d7b96f241099f50b1afdde8700c6 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 @@ -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 Jenkins.. + 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 574e3cf648d00d37e3143b2b0bb3e86e6acc410e..91c0eb2289fd22be79ade92beb9036ddbbb1c8ba 100644 --- a/core/src/main/resources/hudson/triggers/TimerTrigger/help_ru.html +++ b/core/src/main/resources/hudson/triggers/TimerTrigger/help_ru.html @@ -1,23 +1,23 @@

- ।⠢ cron-like 㭪樮쭮 - 㪠 ᯨᠭ ᡮப ஥. + �।��⠢��� cron-like �㭪樮���쭮��� + ��� 㪠����� �ᯨᠭ�� ᡮப �஥��.

- 㭪 ᭮ 㦭 ᯮ짮 Jenkins ⢥ - cron, 稬 ࠧ 室 ਮ᪮ ᡮન ஥⮢. + �� �㭪�� � �᭮���� �㦭� ��� �ᯮ�짮����� Jenkins � ����⢥ + ������ cron, � �� ��稬 ��ࠧ�� ���室�� ��� ��ਮ���᪮� ᡮન �஥�⮢. - 짮⥫ ⠫ 楯樥 뢭 ⥣樨 - (continuous integration), 筮 㬠 ॣ୮ ᪥ ᡮப, த - . - , 祢 뢭 ⥣樨 ᪠ ᡮப ᫥ - ᥭ , ண 祭 १ - ࠧࠡ稪. + ����� ���짮��⥫� ����� �⠫�������� � ���楯樥� �����뢭�� ��⥣�樨 + (continuous integration), ���筮 ��� �㬠�� � ॣ��୮� ����᪥ ᡮப, �த� + ����� ��� ��������. + ������, ���祢�� ���� �����뢭�� ��⥣�樨 � ����᪠ ᡮப ���������� ��᫥ + ���ᥭ�� ��������� � ���, ��� ����ண� ����祭�� १���� �� ���������� + ࠧࠡ��稪��. - ⮡ Jenkins 뫮 ⠪, ன - 饭 ஭ SCM. + �⮡� ��������� Jenkins �뫮 ������ ⠪��, ����ன� + �����饭�� �� ��஭� SCM.

- , । ⥬ ᯮ짮 㭪, ⠭ ᥡ, - ⢨⥫쭮 ⮣. + ��������, ��। ⥬ ��� �ᯮ�짮���� ��� �㭪��, ��⠭������ � ���� ᥡ�, + ����⢨⥫쭮 �� �� ��� ������ �⮣�.

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 68b87b9cc73455e30123e6e52c7fc4e7fa3b7b50..b8782162b051357ef3816d55826d7d7de515b5c5 100644 --- a/core/src/main/resources/hudson/triggers/TimerTrigger/help_tr.html +++ b/core/src/main/resources/hudson/triggers/TimerTrigger/help_tr.html @@ -10,7 +10,7 @@ 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 Jenkins'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.