From cbc688af5f6437411c9fb8666a075ea744b3d87b Mon Sep 17 00:00:00 2001 From: Tim Jacomb Date: Thu, 25 Aug 2022 22:07:30 +0100 Subject: [PATCH] Fix all lint errors --- .github/PULL_REQUEST_TEMPLATE.md | 17 +- .github/dependabot.yml | 2 +- .github/release-drafter.yml | 2 +- .../workflows/publish-release-artifact.yml | 4 +- CONTRIBUTING.md | 96 +- README.md | 22 +- changelog.html | 2 +- .../java/hudson/model/listeners/package.html | 9 +- core/src/main/java/hudson/model/package.html | 11 +- .../java/hudson/node_monitors/package.html | 9 +- .../main/java/hudson/scheduler/package.html | 9 +- .../java/hudson/scm/browsers/package.html | 9 +- core/src/main/java/hudson/scm/package.html | 10 +- core/src/main/java/hudson/search/package.html | 11 +- .../main/java/hudson/security/package.html | 11 +- core/src/main/java/hudson/slaves/package.html | 9 +- core/src/main/java/hudson/tasks/package.html | 14 +- .../main/java/hudson/triggers/package.html | 11 +- core/src/main/java/hudson/util/package.html | 9 +- .../resources/hudson/PluginManager/_table.js | 836 ++-- .../hudson/ProxyConfiguration/help-name.html | 26 +- .../ProxyConfiguration/help-name_bg.html | 22 +- .../ProxyConfiguration/help-name_de.html | 29 +- .../ProxyConfiguration/help-name_fr.html | 27 +- .../ProxyConfiguration/help-name_it.html | 27 +- .../ProxyConfiguration/help-name_ja.html | 21 +- .../ProxyConfiguration/help-name_nl.html | 34 +- .../ProxyConfiguration/help-name_pl.html | 25 +- .../ProxyConfiguration/help-name_pt_BR.html | 26 +- .../ProxyConfiguration/help-name_zh_TW.html | 22 +- .../ProxyConfiguration/help-noProxyHost.html | 7 +- .../help-noProxyHost_bg.html | 5 +- .../help-noProxyHost_de.html | 8 +- .../help-noProxyHost_it.html | 6 +- .../help-noProxyHost_ja.html | 6 +- .../help-noProxyHost_zh_TW.html | 6 +- .../hudson/ProxyConfiguration/help-port.html | 5 +- .../ProxyConfiguration/help-port_bg.html | 4 +- .../ProxyConfiguration/help-port_de.html | 4 +- .../ProxyConfiguration/help-port_fr.html | 2 +- .../ProxyConfiguration/help-port_it.html | 4 +- .../ProxyConfiguration/help-port_ja.html | 5 +- .../ProxyConfiguration/help-port_nl.html | 5 +- .../ProxyConfiguration/help-port_pt_BR.html | 3 +- .../ProxyConfiguration/help-port_tr.html | 5 +- .../ProxyConfiguration/help-port_zh_TW.html | 4 +- .../ProxyConfiguration/help-userName.html | 14 +- .../ProxyConfiguration/help-userName_bg.html | 9 +- .../ProxyConfiguration/help-userName_de.html | 17 +- .../ProxyConfiguration/help-userName_it.html | 11 +- .../ProxyConfiguration/help-userName_ja.html | 7 +- .../help-userName_zh_TW.html | 7 +- .../console/ExpandableDetailsNote/script.js | 22 +- .../console/ExpandableDetailsNote/style.css | 10 +- .../ReverseProxySetupMonitor/resources.css | 4 +- .../ReverseProxySetupMonitor/resources.js | 94 +- .../AbstractItem/help-displayNameOrNull.html | 13 +- .../help-displayNameOrNull_bg.html | 13 +- .../help-displayNameOrNull_de.html | 15 +- .../help-displayNameOrNull_it.html | 13 +- .../help-displayNameOrNull_ja.html | 8 +- .../help-displayNameOrNull_zh_TW.html | 9 +- .../AbstractItem/help-slaveAffinity.html | 27 +- .../AbstractItem/help-slaveAffinity_bg.html | 23 +- .../AbstractItem/help-slaveAffinity_fr.html | 16 +- .../AbstractItem/help-slaveAffinity_it.html | 28 +- .../AbstractItem/help-slaveAffinity_ja.html | 19 +- .../AbstractItem/help-slaveAffinity_ru.html | 17 +- .../AbstractProject/help-concurrentBuild.html | 86 +- .../help-concurrentBuild_bg.html | 93 +- .../help-concurrentBuild_de.html | 52 +- .../help-concurrentBuild_fr.html | 104 +- .../help-concurrentBuild_it.html | 106 +- .../help-concurrentBuild_ja.html | 14 +- .../help-concurrentBuild_zh_TW.html | 35 +- .../model/AbstractProject/help-label.html | 170 +- .../model/AbstractProject/help-label_bg.html | 173 +- .../model/AbstractProject/help-label_it.html | 188 +- .../help-boolean-default.html | 4 +- .../help-boolean-default_bg.html | 4 +- .../help-boolean-default_de.html | 4 +- .../help-boolean-default_fr.html | 4 +- .../help-boolean-default_it.html | 4 +- .../help-boolean-default_ja.html | 4 +- .../help-boolean-default_ru.html | 4 +- .../help-boolean-default_zh_TW.html | 4 +- .../build-timeline-widget.js | 218 +- .../model/Job/buildTimeTrend_resources.css | 2 +- .../model/Job/buildTimeTrend_resources.js | 188 +- .../ListView/configure-entries-resources.js | 14 +- .../hudson/model/LoadStatistics/resources.js | 60 +- .../ParametersDefinitionProperty/help.html | 83 +- .../ParametersDefinitionProperty/help_bg.html | 87 +- .../ParametersDefinitionProperty/help_de.html | 29 +- .../ParametersDefinitionProperty/help_fr.html | 24 +- .../ParametersDefinitionProperty/help_it.html | 84 +- .../ParametersDefinitionProperty/help_ja.html | 19 +- .../ParametersDefinitionProperty/help_tr.html | 25 +- .../help_zh_TW.html | 18 +- .../PasswordParameterDefinition/help.html | 9 +- .../PasswordParameterDefinition/help_it.html | 10 +- .../hudson/model/Slave/help-remoteFS.html | 69 +- .../hudson/model/Slave/help-remoteFS_bg.html | 70 +- .../hudson/model/Slave/help-remoteFS_fr.html | 23 +- .../hudson/model/Slave/help-remoteFS_it.html | 79 +- .../hudson/model/Slave/help-remoteFS_ja.html | 14 +- .../hudson/model/Slave/help-remoteFS_ru.html | 18 +- .../StringParameterDefinition/help-trim.html | 4 +- .../help-trim_it.html | 4 +- .../TimeZoneProperty/help-timeZoneName.html | 2 +- .../help-timeZoneName_ja.html | 2 +- .../model/UpdateCenter/update-center.js | 62 +- .../model/UsageStatistics/footer-resources.js | 8 +- .../View/AsynchPeople/people-resources.js | 98 +- .../help-freeSpaceThreshold.html | 9 +- .../help-freeSpaceThreshold_bg.html | 9 +- .../help-freeSpaceThreshold_it.html | 10 +- .../help-freeSpaceThreshold_ja.html | 7 +- .../ArchitectureMonitor/help.html | 5 +- .../ArchitectureMonitor/help_bg.html | 6 +- .../ArchitectureMonitor/help_it.html | 4 +- .../ArchitectureMonitor/help_ja.html | 4 +- .../node_monitors/ClockMonitor/help.html | 12 +- .../node_monitors/ClockMonitor/help_bg.html | 11 +- .../node_monitors/ClockMonitor/help_it.html | 15 +- .../node_monitors/ClockMonitor/help_ja.html | 11 +- .../ClockMonitor/help_zh_TW.html | 9 +- .../node_monitors/DiskSpaceMonitor/help.html | 12 +- .../DiskSpaceMonitor/help_bg.html | 13 +- .../DiskSpaceMonitor/help_it.html | 11 +- .../DiskSpaceMonitor/help_ja.html | 7 +- .../ResponseTimeMonitor/help.html | 17 +- .../ResponseTimeMonitor/help_bg.html | 11 +- .../ResponseTimeMonitor/help_it.html | 17 +- .../ResponseTimeMonitor/help_ja.html | 7 +- .../SwapSpaceMonitor/help_ja.html | 36 +- .../TemporarySpaceMonitor/help.html | 23 +- .../TemporarySpaceMonitor/help_bg.html | 21 +- .../TemporarySpaceMonitor/help_it.html | 25 +- .../TemporarySpaceMonitor/help_ja.html | 16 +- .../AuthorizationStrategy/Unsecured/help.html | 11 +- .../Unsecured/help_bg.html | 11 +- .../Unsecured/help_de.html | 13 +- .../Unsecured/help_fr.html | 17 +- .../Unsecured/help_it.html | 15 +- .../Unsecured/help_ja.html | 7 +- .../Unsecured/help_pt_BR.html | 16 +- .../Unsecured/help_ru.html | 16 +- .../Unsecured/help_tr.html | 14 +- .../Unsecured/help_zh_TW.html | 7 +- .../help-allowAnonymousRead.html | 3 +- .../help.html | 10 +- .../help_bg.html | 9 +- .../help_de.html | 13 +- .../help_fr.html | 19 +- .../help_it.html | 15 +- .../help_ja.html | 5 +- .../help_pt_BR.html | 14 +- .../help_ru.html | 14 +- .../help_tr.html | 24 +- .../help_zh_TW.html | 10 +- .../help-agentProtocol.html | 6 +- .../help-agentProtocol_bg.html | 4 +- .../help-disableRememberMe.html | 5 +- .../help-disableRememberMe_bg.html | 6 +- .../help-disableRememberMe_de.html | 4 +- .../help-disableRememberMe_it.html | 4 +- .../help-disableRememberMe_ja.html | 4 +- .../help-slaveAgentPort.html | 13 +- .../help-slaveAgentPort_bg.html | 2 +- .../help-slaveAgentPort_fr.html | 12 +- .../help-slaveAgentPort_it.html | 16 +- .../help-slaveAgentPort_ja.html | 2 +- .../help-slaveAgentPort_ru.html | 9 +- .../help-useSecurity.html | 13 +- .../help-useSecurity_bg.html | 17 +- .../help-useSecurity_de.html | 38 +- .../help-useSecurity_fr.html | 35 +- .../help-useSecurity_it.html | 18 +- .../help-useSecurity_ja.html | 28 +- .../help-useSecurity_pt_BR.html | 35 +- .../help-useSecurity_ru.html | 33 +- .../help-useSecurity_tr.html | 39 +- .../help-useSecurity_zh_TW.html | 26 +- .../_entryFormPage/resources.css | 8 +- .../help-allowsSignup.html | 22 +- .../help-allowsSignup_it.html | 23 +- .../HudsonPrivateSecurityRealm/help.html | 11 +- .../HudsonPrivateSecurityRealm/help_bg.html | 11 +- .../HudsonPrivateSecurityRealm/help_de.html | 9 +- .../HudsonPrivateSecurityRealm/help_fr.html | 11 +- .../HudsonPrivateSecurityRealm/help_it.html | 9 +- .../HudsonPrivateSecurityRealm/help_ja.html | 6 +- .../help_pt_BR.html | 9 +- .../HudsonPrivateSecurityRealm/help_ru.html | 5 +- .../HudsonPrivateSecurityRealm/help_tr.html | 8 +- .../help_zh_TW.html | 7 +- .../LegacyAuthorizationStrategy/help.html | 6 +- .../LegacyAuthorizationStrategy/help_bg.html | 6 +- .../LegacyAuthorizationStrategy/help_de.html | 2 +- .../LegacyAuthorizationStrategy/help_fr.html | 11 +- .../LegacyAuthorizationStrategy/help_it.html | 6 +- .../help_pt_BR.html | 7 +- .../LegacyAuthorizationStrategy/help_ru.html | 8 +- .../LegacyAuthorizationStrategy/help_tr.html | 9 +- .../help_zh_TW.html | 6 +- .../security/LegacySecurityRealm/help.html | 14 +- .../security/LegacySecurityRealm/help_bg.html | 12 +- .../security/LegacySecurityRealm/help_de.html | 12 +- .../security/LegacySecurityRealm/help_fr.html | 23 +- .../security/LegacySecurityRealm/help_it.html | 18 +- .../security/LegacySecurityRealm/help_ja.html | 4 +- .../LegacySecurityRealm/help_pt_BR.html | 19 +- .../security/LegacySecurityRealm/help_ru.html | 19 +- .../security/LegacySecurityRealm/help_tr.html | 21 +- .../LegacySecurityRealm/help_zh_TW.html | 12 +- .../help-excludeClientIPFromCrumb.html | 10 +- .../help-excludeClientIPFromCrumb_bg.html | 10 +- .../help-excludeClientIPFromCrumb_it.html | 12 +- .../help-excludeClientIPFromCrumb_zh_TW.html | 8 +- .../help-csrf.html | 39 +- .../help-csrf_bg.html | 42 +- .../help-csrf_de.html | 23 +- .../help-csrf_it.html | 52 +- .../help-csrf_ja.html | 11 +- .../help-csrf_zh_TW.html | 17 +- .../help-instanceCapStr.html | 20 +- .../help-instanceCapStr_bg.html | 21 +- .../help-instanceCapStr_it.html | 17 +- .../slaves/JNLPLauncher/help-vmargs.html | 13 +- .../slaves/JNLPLauncher/help-vmargs_bg.html | 13 +- .../slaves/JNLPLauncher/help-vmargs_fr.html | 14 +- .../slaves/JNLPLauncher/help-vmargs_it.html | 12 +- .../slaves/JNLPLauncher/help-vmargs_ja.html | 11 +- .../slaves/JNLPLauncher/help-webSocket.html | 5 +- .../JNLPLauncher/help-webSocket_it.html | 7 +- .../help-allowEmptyArchive.html | 8 +- .../help-allowEmptyArchive_bg.html | 7 +- .../help-allowEmptyArchive_it.html | 9 +- .../help-allowEmptyArchive_zh_TW.html | 6 +- .../ArtifactArchiver/help-artifacts.html | 54 +- .../ArtifactArchiver/help-artifacts_bg.html | 14 +- .../ArtifactArchiver/help-artifacts_de.html | 15 +- .../ArtifactArchiver/help-artifacts_fr.html | 13 +- .../ArtifactArchiver/help-artifacts_it.html | 20 +- .../ArtifactArchiver/help-artifacts_ja.html | 14 +- .../ArtifactArchiver/help-artifacts_nl.html | 14 +- .../help-artifacts_pt_BR.html | 12 +- .../ArtifactArchiver/help-artifacts_ru.html | 13 +- .../ArtifactArchiver/help-artifacts_tr.html | 14 +- .../help-artifacts_zh_TW.html | 12 +- .../ArtifactArchiver/help-caseSensitive.html | 14 +- .../help-caseSensitive_bg.html | 17 +- .../help-caseSensitive_it.html | 22 +- .../tasks/ArtifactArchiver/help-excludes.html | 6 +- .../ArtifactArchiver/help-excludes_bg.html | 8 +- .../ArtifactArchiver/help-excludes_de.html | 11 +- .../ArtifactArchiver/help-excludes_fr.html | 12 +- .../ArtifactArchiver/help-excludes_it.html | 7 +- .../ArtifactArchiver/help-excludes_ja.html | 7 +- .../ArtifactArchiver/help-excludes_nl.html | 13 +- .../ArtifactArchiver/help-excludes_pt_BR.html | 10 +- .../ArtifactArchiver/help-excludes_ru.html | 12 +- .../ArtifactArchiver/help-excludes_tr.html | 11 +- .../ArtifactArchiver/help-excludes_zh_TW.html | 6 +- .../ArtifactArchiver/help-followSymlinks.html | 4 +- .../help-followSymlinks_de.html | 4 +- .../help-followSymlinks_it.html | 5 +- .../hudson/tasks/ArtifactArchiver/help.html | 35 +- .../tasks/ArtifactArchiver/help_bg.html | 13 +- .../tasks/ArtifactArchiver/help_de.html | 19 +- .../tasks/ArtifactArchiver/help_fr.html | 11 +- .../tasks/ArtifactArchiver/help_it.html | 15 +- .../tasks/ArtifactArchiver/help_pt_BR.html | 15 +- .../tasks/ArtifactArchiver/help_ru.html | 11 +- .../tasks/ArtifactArchiver/help_tr.html | 13 +- .../tasks/ArtifactArchiver/help_zh_TW.html | 7 +- .../tasks/BatchFile/help-unstableReturn.html | 16 +- .../BatchFile/help-unstableReturn_bg.html | 17 +- .../BatchFile/help-unstableReturn_it.html | 25 +- .../Fingerprinter/help-caseSensitive.html | 12 +- .../Fingerprinter/help-caseSensitive_it.html | 22 +- .../tasks/Fingerprinter/help-excludes.html | 7 +- .../tasks/Fingerprinter/help-excludes_it.html | 7 +- .../tasks/Fingerprinter/help-targets.html | 12 +- .../tasks/Fingerprinter/help-targets_bg.html | 12 +- .../tasks/Fingerprinter/help-targets_da.html | 4 +- .../tasks/Fingerprinter/help-targets_de.html | 12 +- .../tasks/Fingerprinter/help-targets_es.html | 11 +- .../tasks/Fingerprinter/help-targets_fr.html | 11 +- .../tasks/Fingerprinter/help-targets_it.html | 12 +- .../tasks/Fingerprinter/help-targets_ja.html | 8 +- .../tasks/Fingerprinter/help-targets_nl.html | 11 +- .../Fingerprinter/help-targets_pt_BR.html | 10 +- .../tasks/Fingerprinter/help-targets_ru.html | 12 +- .../Fingerprinter/help-targets_zh_TW.html | 10 +- .../hudson/tasks/Fingerprinter/help.html | 50 +- .../hudson/tasks/Fingerprinter/help_bg.html | 54 +- .../hudson/tasks/Fingerprinter/help_de.html | 59 +- .../hudson/tasks/Fingerprinter/help_fr.html | 57 +- .../hudson/tasks/Fingerprinter/help_it.html | 44 +- .../hudson/tasks/Fingerprinter/help_ja.html | 44 +- .../tasks/Fingerprinter/help_pt_BR.html | 42 +- .../hudson/tasks/Fingerprinter/help_ru.html | 50 +- .../hudson/tasks/Fingerprinter/help_tr.html | 54 +- .../tasks/Fingerprinter/help_zh_TW.html | 40 +- .../Maven/help-injectBuildVariables.html | 11 +- .../Maven/help-injectBuildVariables_bg.html | 13 +- .../Maven/help-injectBuildVariables_it.html | 13 +- .../hudson/tasks/Maven/help-properties.html | 12 +- .../tasks/Maven/help-properties_bg.html | 14 +- .../tasks/Maven/help-properties_de.html | 13 +- .../tasks/Maven/help-properties_fr.html | 12 +- .../tasks/Maven/help-properties_it.html | 13 +- .../tasks/Maven/help-properties_ja.html | 10 +- .../tasks/Maven/help-properties_zh_TW.html | 9 +- .../hudson/tasks/Maven/help-settings.html | 44 +- .../hudson/tasks/Maven/help-settings_bg.html | 46 +- .../hudson/tasks/Maven/help-settings_it.html | 44 +- .../tasks/Maven/help-settings_zh_TW.html | 30 +- .../hudson/tasks/Shell/help-shell.html | 11 +- .../hudson/tasks/Shell/help-shell_bg.html | 11 +- .../hudson/tasks/Shell/help-shell_de.html | 14 +- .../hudson/tasks/Shell/help-shell_fr.html | 12 +- .../hudson/tasks/Shell/help-shell_it.html | 10 +- .../hudson/tasks/Shell/help-shell_ja.html | 9 +- .../hudson/tasks/Shell/help-shell_nl.html | 11 +- .../hudson/tasks/Shell/help-shell_pt_BR.html | 11 +- .../hudson/tasks/Shell/help-shell_zh_TW.html | 13 +- .../tasks/Shell/help-unstableReturn.html | 8 +- .../tasks/Shell/help-unstableReturn_bg.html | 13 +- .../tasks/Shell/help-unstableReturn_it.html | 14 +- .../resources/hudson/tasks/Shell/help.html | 34 +- .../resources/hudson/tasks/Shell/help_bg.html | 40 +- .../resources/hudson/tasks/Shell/help_de.html | 23 +- .../resources/hudson/tasks/Shell/help_fr.html | 36 +- .../resources/hudson/tasks/Shell/help_it.html | 45 +- .../resources/hudson/tasks/Shell/help_ja.html | 26 +- .../hudson/tasks/Shell/help_pt_BR.html | 29 +- .../resources/hudson/tasks/Shell/help_ru.html | 30 +- .../resources/hudson/tasks/Shell/help_tr.html | 25 +- .../hudson/tasks/Shell/help_zh_TW.html | 28 +- .../help-command.html | 4 +- .../help-command_bg.html | 6 +- .../help-command_it.html | 6 +- .../help-command_ja.html | 4 +- .../help-toolHome.html | 4 +- .../help-toolHome_bg.html | 4 +- .../help-toolHome_de.html | 6 +- .../help-toolHome_it.html | 4 +- .../help-toolHome_zh_TW.html | 5 +- .../tools/AbstractCommandInstaller/help.html | 26 +- .../AbstractCommandInstaller/help_bg.html | 29 +- .../AbstractCommandInstaller/help_de.html | 30 +- .../AbstractCommandInstaller/help_it.html | 29 +- .../AbstractCommandInstaller/help_ja.html | 25 +- .../AbstractCommandInstaller/help_zh_TW.html | 24 +- .../tools/InstallSourceProperty/help.html | 22 +- .../tools/InstallSourceProperty/help_bg.html | 16 +- .../tools/InstallSourceProperty/help_it.html | 26 +- .../tools/InstallSourceProperty/help_ja.html | 10 +- .../ZipExtractionInstaller/help-subdir.html | 3 +- .../help-subdir_bg.html | 4 +- .../help-subdir_de.html | 4 +- .../help-subdir_it.html | 4 +- .../help-subdir_ja.html | 2 +- .../help-subdir_zh_TW.html | 4 +- .../ZipExtractionInstaller/help-url.html | 9 +- .../ZipExtractionInstaller/help-url_bg.html | 10 +- .../ZipExtractionInstaller/help-url_it.html | 11 +- .../ZipExtractionInstaller/help-url_ja.html | 10 +- .../tools/ZipExtractionInstaller/help.html | 11 +- .../tools/ZipExtractionInstaller/help_bg.html | 14 +- .../tools/ZipExtractionInstaller/help_de.html | 12 +- .../tools/ZipExtractionInstaller/help_it.html | 12 +- .../tools/ZipExtractionInstaller/help_ja.html | 11 +- .../ZipExtractionInstaller/help_zh_TW.html | 10 +- .../help-ignorePostCommitHooks.html | 17 +- .../help-ignorePostCommitHooks_bg.html | 21 +- .../help-ignorePostCommitHooks_it.html | 21 +- .../help-ignorePostCommitHooks_zh_TW.html | 15 +- .../SCMTrigger/help-pollingThreadCount.html | 10 +- .../help-pollingThreadCount_it.html | 13 +- .../hudson/triggers/SCMTrigger/help.html | 12 +- .../hudson/triggers/SCMTrigger/help_bg.html | 14 +- .../hudson/triggers/SCMTrigger/help_de.html | 15 +- .../hudson/triggers/SCMTrigger/help_fr.html | 13 +- .../hudson/triggers/SCMTrigger/help_it.html | 16 +- .../hudson/triggers/SCMTrigger/help_ja.html | 13 +- .../triggers/SCMTrigger/help_pt_BR.html | 13 +- .../hudson/triggers/SCMTrigger/help_ru.html | 15 +- .../hudson/triggers/SCMTrigger/help_tr.html | 16 +- .../triggers/SCMTrigger/help_zh_TW.html | 8 +- .../triggers/TimerTrigger/help-spec_bg.html | 129 +- .../triggers/TimerTrigger/help-spec_de.html | 102 +- .../triggers/TimerTrigger/help-spec_fr.html | 42 +- .../triggers/TimerTrigger/help-spec_ja.html | 40 +- .../TimerTrigger/help-spec_pt_BR.html | 34 +- .../triggers/TimerTrigger/help-spec_ru.html | 34 +- .../triggers/TimerTrigger/help-spec_tr.html | 51 +- .../TimerTrigger/help-spec_zh_TW.html | 50 +- .../hudson/triggers/TimerTrigger/help.html | 31 +- .../hudson/triggers/TimerTrigger/help_bg.html | 36 +- .../hudson/triggers/TimerTrigger/help_de.html | 33 +- .../hudson/triggers/TimerTrigger/help_fr.html | 34 +- .../hudson/triggers/TimerTrigger/help_it.html | 37 +- .../hudson/triggers/TimerTrigger/help_ja.html | 31 +- .../triggers/TimerTrigger/help_pt_BR.html | 34 +- .../hudson/triggers/TimerTrigger/help_ru.html | 36 +- .../hudson/triggers/TimerTrigger/help_tr.html | 34 +- .../triggers/TimerTrigger/help_zh_TW.html | 25 +- .../hudson/views/BuildButtonColumn/icon.js | 25 +- .../help-myViewsTabBar.html | 12 +- .../help-myViewsTabBar_bg.html | 12 +- .../help-myViewsTabBar_it.html | 14 +- .../help-myViewsTabBar_zh_TW.html | 10 +- .../help-viewsTabBar.html | 11 +- .../help-viewsTabBar_bg.html | 13 +- .../help-viewsTabBar_it.html | 13 +- .../help-viewsTabBar_zh_TW.html | 10 +- .../URICheckEncodingMonitor/adjunct.js | 23 +- .../formelementpath/form-element-path.js | 361 +- .../jenkins/install/platform-plugins.json | 207 +- .../resources.css | 212 +- .../resources.js | 164 +- .../model/BuildDiscarderProperty/help.html | 76 +- .../model/BuildDiscarderProperty/help_bg.html | 85 +- .../model/BuildDiscarderProperty/help_de.html | 9 +- .../model/BuildDiscarderProperty/help_fr.html | 30 +- .../model/BuildDiscarderProperty/help_it.html | 99 +- .../model/BuildDiscarderProperty/help_ja.html | 7 +- .../BuildDiscarderProperty/help_pt_BR.html | 26 +- .../model/BuildDiscarderProperty/help_ru.html | 22 +- .../model/BuildDiscarderProperty/help_tr.html | 27 +- .../BuildDiscarderProperty/help_zh_TW.html | 10 +- .../help-quietPeriod.html | 33 +- .../help-quietPeriod_bg.html | 40 +- .../help-quietPeriod_de.html | 18 +- .../help-quietPeriod_fr.html | 30 +- .../help-quietPeriod_it.html | 39 +- .../help-quietPeriod_ja.html | 2 +- .../help-quietPeriod_pt_BR.html | 29 +- .../help-quietPeriod_ru.html | 28 +- .../help-quietPeriod_tr.html | 32 +- .../help-quietPeriod_zh_TW.html | 14 +- .../model/Jenkins/help-markupFormatter.html | 24 +- .../Jenkins/help-markupFormatter_bg.html | 19 +- .../Jenkins/help-markupFormatter_it.html | 25 +- .../Jenkins/help-markupFormatter_ja.html | 20 +- .../Jenkins/help-markupFormatter_zh_TW.html | 19 +- .../help-adminAddress.html | 6 +- .../help-adminAddress_bg.html | 6 +- .../help-adminAddress_de.html | 9 +- .../help-adminAddress_fr.html | 8 +- .../help-adminAddress_it.html | 6 +- .../help-adminAddress_ja.html | 3 +- .../help-adminAddress_nl.html | 3 +- .../help-adminAddress_pt_BR.html | 7 +- .../help-adminAddress_ru.html | 7 +- .../help-adminAddress_tr.html | 4 +- .../help-adminAddress_zh_TW.html | 4 +- .../help-url.html | 13 +- .../help-url_bg.html | 11 +- .../help-url_de.html | 11 +- .../help-url_fr.html | 13 +- .../help-url_it.html | 13 +- .../help-url_ja.html | 8 +- .../help-url_nl.html | 13 +- .../help-url_pt_BR.html | 12 +- .../help-url_ru.html | 9 +- .../help-url_tr.html | 13 +- .../help-url_zh_TW.html | 9 +- .../help-description.html | 4 +- .../help-description_bg.html | 4 +- .../help-description_de.html | 5 +- .../help-description_it.html | 6 +- .../DefaultGlobalSettingsProvider/help.html | 4 +- .../help_bg.html | 5 +- .../help_it.html | 6 +- .../help_zh_TW.html | 6 +- .../mvn/DefaultSettingsProvider/help.html | 4 +- .../mvn/DefaultSettingsProvider/help_bg.html | 5 +- .../mvn/DefaultSettingsProvider/help_it.html | 6 +- .../DefaultSettingsProvider/help_zh_TW.html | 6 +- .../help-path.html | 5 +- .../help-path_bg.html | 6 +- .../help-path_ja.html | 4 +- .../help-path_zh_TW.html | 4 +- .../FilePathGlobalSettingsProvider/help.html | 5 +- .../help_bg.html | 8 +- .../help_it.html | 8 +- .../help_ja.html | 6 +- .../help_zh_TW.html | 7 +- .../FilePathSettingsProvider/help-path.html | 5 +- .../help-path_bg.html | 6 +- .../help-path_ja.html | 4 +- .../help-path_zh_TW.html | 4 +- .../mvn/FilePathSettingsProvider/help.html | 5 +- .../mvn/FilePathSettingsProvider/help_bg.html | 7 +- .../mvn/FilePathSettingsProvider/help_it.html | 7 +- .../mvn/FilePathSettingsProvider/help_ja.html | 6 +- .../FilePathSettingsProvider/help_zh_TW.html | 7 +- .../ApiTokenProperty/help-tokenStore.html | 40 +- .../ApiTokenProperty/help-tokenStore_bg.html | 11 +- .../ApiTokenProperty/help-tokenStore_fr.html | 33 +- .../ApiTokenProperty/help-tokenStore_it.html | 26 +- .../ApiTokenProperty/help-tokenStore_ja.html | 9 +- .../help-tokenStore_zh_TW.html | 9 +- .../security/ApiTokenProperty/resources.css | 178 +- .../security/ApiTokenProperty/resources.js | 207 +- .../ResourceDomainConfiguration/help-url.html | 106 +- .../help-url_it.html | 114 +- .../UpdateSiteWarningsConfiguration/help.html | 26 +- .../help_bg.html | 28 +- .../help_it.html | 27 +- .../help-creationOfLegacyTokenEnabled.html | 8 +- .../help-creationOfLegacyTokenEnabled_it.html | 6 +- ...help-tokenGenerationOnCreationEnabled.html | 8 +- ...p-tokenGenerationOnCreationEnabled_it.html | 6 +- .../help-usageStatisticsEnabled.html | 14 +- .../help-usageStatisticsEnabled_it.html | 7 +- .../resources.css | 34 +- .../resources.js | 229 +- .../seed/UserSeedProperty/help-resetSeed.html | 17 +- .../UserSeedProperty/help-resetSeed_it.html | 19 +- .../UserSeedProperty/help-resetSeed_ja.html | 15 +- .../seed/UserSeedProperty/resources.css | 12 +- .../seed/UserSeedProperty/resources.js | 50 +- .../help-disabled.html | 8 +- .../help-disabled_bg.html | 8 +- .../help-disabled_it.html | 8 +- .../help-failIfWorkDirIsMissing.html | 5 +- .../help-failIfWorkDirIsMissing_bg.html | 5 +- .../help-failIfWorkDirIsMissing_it.html | 5 +- .../help-internalDir.html | 4 +- .../help-internalDir_bg.html | 4 +- .../help-internalDir_it.html | 4 +- .../help-workDirPath.html | 5 +- .../help-workDirPath_bg.html | 5 +- .../help-workDirPath_it.html | 6 +- .../help-retainCharacteristicEnvVars.html | 15 +- .../help-variables.html | 6 +- .../impl/RetainVariablesLocalRule/help.html | 99 +- .../triggers/ReverseBuildTrigger/help.html | 16 +- .../triggers/ReverseBuildTrigger/help_bg.html | 9 +- .../triggers/ReverseBuildTrigger/help_de.html | 15 +- .../triggers/ReverseBuildTrigger/help_fr.html | 12 +- .../triggers/ReverseBuildTrigger/help_it.html | 9 +- .../triggers/ReverseBuildTrigger/help_ja.html | 6 +- .../ReverseBuildTrigger/help_pt_BR.html | 16 +- .../triggers/ReverseBuildTrigger/help_ru.html | 16 +- .../triggers/ReverseBuildTrigger/help_tr.html | 21 +- .../ReverseBuildTrigger/help_zh_TW.html | 5 +- .../resources/lib/form/advanced/advanced.js | 81 +- .../main/resources/lib/form/apply/apply.js | 157 +- .../form/breadcrumb-config-outline/init.css | 10 +- .../form/breadcrumb-config-outline/init.js | 37 +- .../resources/lib/form/combobox/combobox.js | 46 +- core/src/main/resources/lib/form/confirm.js | 191 +- .../filter-menu-button/filter-menu-button.js | 26 +- .../lib/form/hetero-list/hetero-list.js | 314 +- core/src/main/resources/lib/form/link/link.js | 44 +- .../resources/lib/form/password/password.css | 46 +- .../resources/lib/form/password/password.js | 22 +- .../lib/form/radioBlock/radioBlock.js | 127 +- .../lib/form/repeatable/repeatable.js | 426 +- .../lib/form/secretTextarea/secret.css | 68 +- .../lib/form/secretTextarea/secret.js | 82 +- core/src/main/resources/lib/form/section_.js | 135 +- .../main/resources/lib/form/select/select.js | 222 +- .../resources/lib/form/textarea/textarea.css | 2 +- .../resources/lib/form/textarea/textarea.js | 169 +- .../lib/form/validateButton/adjunct.js | 13 +- .../lib/hudson/newFromList/validation.js | 40 +- .../resources/lib/hudson/projectViewNested.js | 64 +- .../main/resources/lib/layout/breadcrumbs.js | 433 +- .../lib/layout/confirmationLink/adjunct.js | 37 +- .../lib/layout/copyButton/copyButton.css | 34 +- .../lib/layout/copyButton/copyButton.js | 50 +- .../progressiveRendering.js | 56 +- war/.babelrc | 2 +- war/.eslintrc.js | 61 +- war/.stylelintrc.js | 6 +- war/jest.config.json | 4 +- war/postcss.config.js | 4 +- war/src/main/js/add-item.js | 276 +- war/src/main/js/api/pluginManager.js | 370 +- war/src/main/js/api/securityConfig.js | 77 +- war/src/main/js/config-scrollspy.js | 247 +- war/src/main/js/config-scrollspy.less | 4 +- war/src/main/js/config-tabbar.js | 50 +- war/src/main/js/config-tabbar.less | 5 +- war/src/main/js/filter-build-history.js | 913 ++-- war/src/main/js/handlebars-helpers/id.js | 2 +- war/src/main/js/handlebars-helpers/ifeq.js | 2 +- war/src/main/js/handlebars-helpers/ifneq.js | 2 +- .../main/js/handlebars-helpers/in-array.js | 2 +- war/src/main/js/handlebars-helpers/replace.js | 2 +- war/src/main/js/page-init.js | 50 +- war/src/main/js/plugin-manager-ui.js | 110 +- war/src/main/js/pluginSetupWizard.js | 19 +- war/src/main/js/pluginSetupWizardGui.js | 2715 ++++++----- war/src/main/js/section-to-tabs.js | 50 +- war/src/main/js/sortable-drag-drop.js | 34 +- war/src/main/js/util/behavior-shim.js | 4 +- war/src/main/js/util/jenkins.js | 431 +- war/src/main/js/util/jenkinsLocalStorage.js | 32 +- war/src/main/js/util/jquery-ext.js | 42 +- war/src/main/js/util/localStorage.js | 54 +- war/src/main/js/util/page.js | 72 +- war/src/main/js/widgets/add/addform.less | 84 +- .../widgets/config/model/ConfigRowGrouping.js | 96 +- .../js/widgets/config/model/ConfigSection.js | 410 +- .../config/model/ConfigTableMetaData.js | 607 +-- war/src/main/js/widgets/config/model/util.js | 4 +- war/src/main/js/widgets/config/tabbar.js | 279 +- war/src/main/js/widgets/config/tabbar.less | 52 +- war/src/main/js/widgets/form/form-mixins.less | 22 +- war/src/main/js/widgets/layout-mixins.less | 20 +- war/src/main/less/abstracts/theme.less | 17 +- war/src/main/less/base/layout-commons.less | 7 +- war/src/main/less/base/style.less | 380 +- war/src/main/less/base/typography.less | 2 +- war/src/main/less/base/visibility-utils.less | 3 - war/src/main/less/base/yui-compatibility.less | 2 +- war/src/main/less/form/checkbox.less | 30 +- war/src/main/less/form/radio.less | 15 +- war/src/main/less/form/reorderable-list.less | 70 +- war/src/main/less/form/toggle-switch.less | 7 +- war/src/main/less/modules/badges.less | 31 +- war/src/main/less/modules/breadcrumbs.less | 6 +- war/src/main/less/modules/buttons-temp.less | 2 +- war/src/main/less/modules/buttons.less | 32 +- war/src/main/less/modules/icon-size.less | 22 +- war/src/main/less/modules/icons.less | 4 +- war/src/main/less/modules/page-footer.less | 2 +- war/src/main/less/modules/page-header.less | 256 +- .../main/less/modules/panes-and-bigtable.less | 10 +- .../main/less/modules/progress-animation.less | 87 +- .../main/less/modules/side-panel-widgets.less | 6 +- war/src/main/less/modules/spinner.less | 3 +- war/src/main/less/modules/table.less | 42 +- war/src/main/less/modules/tabs.less | 5 +- war/src/main/less/pages/plugin-manager.less | 3 +- .../main/less/pages/setupWizardFirstUser.less | 3 +- war/src/main/less/pluginSetupWizard.less | 1641 ++++--- war/src/main/less/simple-page.less | 4 +- war/src/main/less/styles.less | 82 +- war/src/main/webapp/css/color.css | 10 +- war/src/main/webapp/css/loading.css | 48 +- war/src/main/webapp/css/responsive-grid.css | 247 +- war/src/main/webapp/css/signup.css | 4 +- .../main/webapp/help/LogRecorder/logger.html | 31 +- .../webapp/help/LogRecorder/logger_bg.html | 23 +- .../webapp/help/LogRecorder/logger_de.html | 28 +- .../webapp/help/LogRecorder/logger_fr.html | 27 +- .../webapp/help/LogRecorder/logger_it.html | 27 +- .../webapp/help/LogRecorder/logger_ja.html | 25 +- .../webapp/help/LogRecorder/logger_zh_TW.html | 21 +- .../main/webapp/help/LogRecorder/name.html | 10 +- .../main/webapp/help/LogRecorder/name_bg.html | 6 +- .../main/webapp/help/LogRecorder/name_de.html | 14 +- .../main/webapp/help/LogRecorder/name_fr.html | 10 +- .../main/webapp/help/LogRecorder/name_it.html | 8 +- .../main/webapp/help/LogRecorder/name_ja.html | 8 +- .../webapp/help/LogRecorder/name_zh_TW.html | 8 +- .../help/parameter/boolean-default_it.html | 4 +- .../main/webapp/help/parameter/boolean.html | 7 +- .../webapp/help/parameter/boolean_bg.html | 6 +- .../webapp/help/parameter/boolean_de.html | 10 +- .../webapp/help/parameter/boolean_fr.html | 9 +- .../webapp/help/parameter/boolean_it.html | 5 +- .../webapp/help/parameter/boolean_ja.html | 6 +- .../webapp/help/parameter/boolean_ru.html | 7 +- .../webapp/help/parameter/boolean_zh_TW.html | 6 +- .../webapp/help/parameter/choice-choices.html | 5 +- .../help/parameter/choice-choices_bg.html | 4 +- .../help/parameter/choice-choices_de.html | 6 +- .../help/parameter/choice-choices_fr.html | 5 +- .../help/parameter/choice-choices_it.html | 3 +- .../help/parameter/choice-choices_ja.html | 4 +- .../help/parameter/choice-choices_ru.html | 5 +- .../help/parameter/choice-choices_zh_TW.html | 4 +- .../main/webapp/help/parameter/choice.html | 8 +- .../main/webapp/help/parameter/choice_bg.html | 6 +- .../main/webapp/help/parameter/choice_de.html | 9 +- .../main/webapp/help/parameter/choice_fr.html | 9 +- .../main/webapp/help/parameter/choice_it.html | 8 +- .../main/webapp/help/parameter/choice_ja.html | 6 +- .../webapp/help/parameter/choice_zh_TW.html | 6 +- .../webapp/help/parameter/description.html | 4 +- .../webapp/help/parameter/description_bg.html | 4 +- .../webapp/help/parameter/description_de.html | 4 +- .../webapp/help/parameter/description_fr.html | 4 +- .../webapp/help/parameter/description_it.html | 4 +- .../webapp/help/parameter/description_ja.html | 4 +- .../webapp/help/parameter/description_ru.html | 4 +- .../help/parameter/description_zh_TW.html | 4 +- .../main/webapp/help/parameter/file-name.html | 6 +- .../webapp/help/parameter/file-name_bg.html | 6 +- .../webapp/help/parameter/file-name_de.html | 6 +- .../webapp/help/parameter/file-name_fr.html | 6 +- .../webapp/help/parameter/file-name_it.html | 6 +- .../webapp/help/parameter/file-name_ja.html | 6 +- .../help/parameter/file-name_zh_TW.html | 6 +- war/src/main/webapp/help/parameter/file.html | 59 +- .../main/webapp/help/parameter/file_bg.html | 64 +- .../main/webapp/help/parameter/file_de.html | 21 +- .../main/webapp/help/parameter/file_fr.html | 38 +- .../main/webapp/help/parameter/file_it.html | 73 +- .../main/webapp/help/parameter/file_ja.html | 27 +- .../webapp/help/parameter/file_zh_TW.html | 15 +- war/src/main/webapp/help/parameter/name.html | 7 +- .../main/webapp/help/parameter/name_bg.html | 5 +- .../main/webapp/help/parameter/name_de.html | 7 +- .../main/webapp/help/parameter/name_fr.html | 14 +- .../main/webapp/help/parameter/name_it.html | 8 +- .../main/webapp/help/parameter/name_ja.html | 7 +- .../main/webapp/help/parameter/name_ru.html | 7 +- .../webapp/help/parameter/name_zh_TW.html | 7 +- .../webapp/help/parameter/run-filter.html | 7 +- .../webapp/help/parameter/run-filter_bg.html | 5 +- .../webapp/help/parameter/run-filter_it.html | 7 +- .../webapp/help/parameter/run-filter_ru.html | 9 +- .../webapp/help/parameter/run-project.html | 9 +- .../webapp/help/parameter/run-project_bg.html | 11 +- .../webapp/help/parameter/run-project_de.html | 6 +- .../webapp/help/parameter/run-project_fr.html | 6 +- .../webapp/help/parameter/run-project_it.html | 11 +- .../webapp/help/parameter/run-project_ja.html | 4 +- .../webapp/help/parameter/run-project_ru.html | 12 +- .../help/parameter/run-project_zh_TW.html | 11 +- war/src/main/webapp/help/parameter/run.html | 11 +- .../main/webapp/help/parameter/run_bg.html | 10 +- .../main/webapp/help/parameter/run_de.html | 11 +- .../main/webapp/help/parameter/run_fr.html | 11 +- .../main/webapp/help/parameter/run_it.html | 10 +- .../main/webapp/help/parameter/run_ja.html | 8 +- .../main/webapp/help/parameter/run_zh_TW.html | 12 +- .../webapp/help/parameter/string-default.html | 5 +- .../help/parameter/string-default_bg.html | 4 +- .../help/parameter/string-default_de.html | 6 +- .../help/parameter/string-default_fr.html | 5 +- .../help/parameter/string-default_it.html | 4 +- .../help/parameter/string-default_ja.html | 4 +- .../help/parameter/string-default_zh_TW.html | 4 +- .../main/webapp/help/parameter/string.html | 8 +- .../main/webapp/help/parameter/string_bg.html | 6 +- .../main/webapp/help/parameter/string_de.html | 9 +- .../main/webapp/help/parameter/string_fr.html | 19 +- .../main/webapp/help/parameter/string_it.html | 7 +- .../main/webapp/help/parameter/string_ja.html | 6 +- .../webapp/help/parameter/string_zh_TW.html | 6 +- .../main/webapp/help/parameter/trim_it.html | 4 +- .../webapp/help/project-config/batch.html | 17 +- .../webapp/help/project-config/batch_bg.html | 17 +- .../webapp/help/project-config/batch_de.html | 16 +- .../webapp/help/project-config/batch_fr.html | 21 +- .../webapp/help/project-config/batch_it.html | 15 +- .../webapp/help/project-config/batch_ja.html | 8 +- .../help/project-config/batch_pt_BR.html | 16 +- .../webapp/help/project-config/batch_ru.html | 16 +- .../webapp/help/project-config/batch_tr.html | 21 +- .../help/project-config/batch_zh_TW.html | 13 +- .../block-downstream-building.html | 4 +- .../block-downstream-building_bg.html | 7 +- .../block-downstream-building_it.html | 8 +- .../block-downstream-building_ja.html | 4 +- .../block-upstream-building.html | 4 +- .../block-upstream-building_bg.html | 5 +- .../block-upstream-building_de.html | 6 +- .../block-upstream-building_it.html | 8 +- .../block-upstream-building_ja.html | 4 +- .../help/project-config/custom-workspace.html | 43 +- .../project-config/custom-workspace_bg.html | 41 +- .../project-config/custom-workspace_de.html | 60 +- .../project-config/custom-workspace_fr.html | 49 +- .../project-config/custom-workspace_it.html | 51 +- .../project-config/custom-workspace_ja.html | 28 +- .../project-config/custom-workspace_tr.html | 38 +- .../custom-workspace_zh_TW.html | 35 +- .../help/project-config/defaultView.html | 9 +- .../help/project-config/defaultView_bg.html | 8 +- .../help/project-config/defaultView_de.html | 13 +- .../help/project-config/defaultView_it.html | 10 +- .../help/project-config/defaultView_ja.html | 8 +- .../project-config/defaultView_zh_TW.html | 8 +- .../help/project-config/description.html | 5 +- .../help/project-config/description_bg.html | 5 +- .../help/project-config/description_de.html | 6 +- .../help/project-config/description_fr.html | 7 +- .../help/project-config/description_it.html | 4 +- .../help/project-config/description_ja.html | 5 +- .../project-config/description_pt_BR.html | 5 +- .../help/project-config/description_ru.html | 2 +- .../help/project-config/description_tr.html | 7 +- .../project-config/description_zh_TW.html | 5 +- .../webapp/help/project-config/disable.html | 22 +- .../help/project-config/disable_bg.html | 20 +- .../help/project-config/disable_de.html | 20 +- .../help/project-config/disable_fr.html | 19 +- .../help/project-config/disable_it.html | 24 +- .../help/project-config/disable_ja.html | 7 +- .../help/project-config/disable_pt_BR.html | 21 +- .../help/project-config/disable_ru.html | 20 +- .../help/project-config/disable_tr.html | 30 +- .../help/project-config/disable_zh_TW.html | 8 +- .../help/project-config/downstream.html | 42 +- .../help/project-config/downstream_bg.html | 43 +- .../help/project-config/downstream_de.html | 14 +- .../help/project-config/downstream_fr.html | 17 +- .../help/project-config/downstream_it.html | 46 +- .../help/project-config/downstream_ja.html | 7 +- .../help/project-config/downstream_pt_BR.html | 14 +- .../help/project-config/downstream_ru.html | 14 +- .../help/project-config/downstream_tr.html | 17 +- .../help/project-config/downstream_zh_TW.html | 11 +- .../project-config/scmCheckoutRetryCount.html | 33 +- .../scmCheckoutRetryCount_bg.html | 37 +- .../scmCheckoutRetryCount_de.html | 6 +- .../scmCheckoutRetryCount_it.html | 42 +- .../scmCheckoutRetryCount_ja.html | 2 +- .../scmCheckoutRetryCount_zh_TW.html | 5 +- .../help/project-config/triggerRemotely.html | 46 +- .../project-config/triggerRemotely_bg.html | 20 +- .../project-config/triggerRemotely_de.html | 15 +- .../project-config/triggerRemotely_fr.html | 22 +- .../project-config/triggerRemotely_it.html | 21 +- .../project-config/triggerRemotely_ja.html | 10 +- .../project-config/triggerRemotely_pt_BR.html | 25 +- .../project-config/triggerRemotely_ru.html | 19 +- .../project-config/triggerRemotely_tr.html | 21 +- .../project-config/triggerRemotely_zh_TW.html | 11 +- .../webapp/help/run-config/description.html | 5 +- .../help/run-config/description_bg.html | 5 +- .../help/run-config/description_de.html | 8 +- .../help/run-config/description_it.html | 8 +- .../help/run-config/description_ja.html | 6 +- .../help/run-config/description_zh_TW.html | 6 +- .../webapp/help/run-config/displayName.html | 6 +- .../help/run-config/displayName_bg.html | 5 +- .../help/run-config/displayName_de.html | 5 +- .../help/run-config/displayName_it.html | 6 +- .../help/run-config/displayName_ja.html | 4 +- .../help/run-config/displayName_zh_TW.html | 5 +- .../main/webapp/help/scm-browsers/list.html | 7 +- .../webapp/help/scm-browsers/list_bg.html | 8 +- .../webapp/help/scm-browsers/list_de.html | 11 +- .../defaultJobNamingStrategy.html | 3 +- .../defaultJobNamingStrategy_fr.html | 3 +- .../defaultJobNamingStrategy_it.html | 3 +- .../defaultJobNamingStrategy_ja.html | 4 +- .../defaultJobNamingStrategy_zh_TW.html | 4 +- .../globalEnvironmentVariables.html | 8 +- .../globalEnvironmentVariables_bg.html | 6 +- .../globalEnvironmentVariables_de.html | 8 +- .../globalEnvironmentVariables_fr.html | 5 +- .../globalEnvironmentVariables_it.html | 7 +- .../globalEnvironmentVariables_ja.html | 4 +- .../globalEnvironmentVariables_zh_TW.html | 4 +- .../help/system-config/homeDirectory.html | 45 +- .../help/system-config/homeDirectory_bg.html | 56 +- .../help/system-config/homeDirectory_de.html | 31 +- .../help/system-config/homeDirectory_fr.html | 25 +- .../help/system-config/homeDirectory_it.html | 51 +- .../help/system-config/homeDirectory_ja.html | 18 +- .../system-config/homeDirectory_pt_BR.html | 31 +- .../help/system-config/homeDirectory_ru.html | 31 +- .../help/system-config/homeDirectory_tr.html | 36 +- .../system-config/homeDirectory_zh_TW.html | 21 +- .../master-slave/availability.html | 109 +- .../master-slave/availability_bg.html | 102 +- .../master-slave/availability_de.html | 61 +- .../master-slave/availability_fr.html | 110 +- .../master-slave/availability_it.html | 118 +- .../master-slave/availability_ja.html | 55 +- .../master-slave/availability_nl.html | 63 +- .../master-slave/availability_zh_TW.html | 57 +- .../system-config/master-slave/clock.html | 7 +- .../system-config/master-slave/clock_bg.html | 7 +- .../system-config/master-slave/clock_de.html | 8 +- .../system-config/master-slave/clock_fr.html | 7 +- .../system-config/master-slave/clock_it.html | 9 +- .../system-config/master-slave/clock_nl.html | 7 +- .../master-slave/clock_pt_BR.html | 9 +- .../system-config/master-slave/clock_ru.html | 7 +- .../system-config/master-slave/clock_tr.html | 10 +- .../master-slave/clock_zh_TW.html | 4 +- .../master-slave/demand/idleDelay_bg.html | 3 +- .../master-slave/demand/idleDelay_de.html | 6 +- .../master-slave/demand/idleDelay_fr.html | 5 +- .../master-slave/demand/idleDelay_ja.html | 4 +- .../master-slave/demand/idleDelay_nl.html | 6 +- .../master-slave/demand/idleDelay_tr.html | 5 +- .../master-slave/demand/idleDelay_zh_TW.html | 4 +- .../master-slave/demand/inDemandDelay_bg.html | 4 +- .../master-slave/demand/inDemandDelay_de.html | 6 +- .../master-slave/demand/inDemandDelay_fr.html | 6 +- .../master-slave/demand/inDemandDelay_it.html | 6 +- .../master-slave/demand/inDemandDelay_ja.html | 4 +- .../master-slave/demand/inDemandDelay_nl.html | 5 +- .../master-slave/demand/inDemandDelay_tr.html | 5 +- .../demand/inDemandDelay_zh_TW.html | 4 +- .../demand/keepUpWhenActive_bg.html | 4 +- .../master-slave/description.html | 5 +- .../master-slave/description_bg.html | 5 +- .../master-slave/description_de.html | 13 +- .../master-slave/description_fr.html | 17 +- .../master-slave/description_it.html | 7 +- .../master-slave/description_ja.html | 9 +- .../master-slave/description_pt_BR.html | 16 +- .../master-slave/description_ru.html | 17 +- .../master-slave/description_tr.html | 19 +- .../master-slave/description_zh_TW.html | 9 +- .../master-slave/jnlp-tunnel.html | 47 +- .../master-slave/jnlp-tunnel_bg.html | 55 +- .../master-slave/jnlp-tunnel_de.html | 57 +- .../master-slave/jnlp-tunnel_fr.html | 55 +- .../master-slave/jnlp-tunnel_it.html | 52 +- .../master-slave/jnlp-tunnel_ja.html | 38 +- .../master-slave/jnlp-tunnel_zh_TW.html | 39 +- .../master-slave/numExecutors.html | 20 +- .../master-slave/numExecutors_bg.html | 23 +- .../master-slave/numExecutors_de.html | 30 +- .../master-slave/numExecutors_fr.html | 22 +- .../master-slave/numExecutors_it.html | 23 +- .../master-slave/numExecutors_ja.html | 13 +- .../master-slave/numExecutors_pt_BR.html | 21 +- .../master-slave/numExecutors_ru.html | 24 +- .../master-slave/numExecutors_tr.html | 26 +- .../master-slave/numExecutors_zh_TW.html | 11 +- .../system-config/master-slave/usage.html | 37 +- .../system-config/master-slave/usage_bg.html | 45 +- .../system-config/master-slave/usage_de.html | 33 +- .../system-config/master-slave/usage_fr.html | 32 +- .../system-config/master-slave/usage_it.html | 50 +- .../system-config/master-slave/usage_ja.html | 11 +- .../master-slave/usage_pt_BR.html | 32 +- .../system-config/master-slave/usage_ru.html | 29 +- .../system-config/master-slave/usage_tr.html | 48 +- .../master-slave/usage_zh_TW.html | 17 +- .../nodeEnvironmentVariables.html | 66 +- .../nodeEnvironmentVariables_bg.html | 66 +- .../nodeEnvironmentVariables_de.html | 12 +- .../nodeEnvironmentVariables_fr.html | 9 +- .../nodeEnvironmentVariables_it.html | 67 +- .../nodeEnvironmentVariables_ja.html | 7 +- .../nodeEnvironmentVariables_zh_TW.html | 6 +- .../patternJobNamingStrategy.html | 18 +- .../patternJobNamingStrategy_bg.html | 18 +- .../patternJobNamingStrategy_de.html | 21 +- .../patternJobNamingStrategy_fr.html | 19 +- .../patternJobNamingStrategy_it.html | 21 +- .../patternJobNamingStrategy_ja.html | 3 +- .../patternJobNamingStrategy_pt_BR.html | 18 +- .../patternJobNamingStrategy_zh_TW.html | 10 +- .../help/system-config/quietPeriod.html | 9 +- .../help/system-config/quietPeriod_bg.html | 7 +- .../help/system-config/quietPeriod_de.html | 11 +- .../help/system-config/quietPeriod_fr.html | 8 +- .../help/system-config/quietPeriod_it.html | 11 +- .../help/system-config/quietPeriod_ja.html | 9 +- .../help/system-config/quietPeriod_pt_BR.html | 9 +- .../help/system-config/quietPeriod_ru.html | 7 +- .../help/system-config/quietPeriod_tr.html | 10 +- .../help/system-config/quietPeriod_zh_TW.html | 7 +- .../help/system-config/systemMessage.html | 6 +- .../help/system-config/systemMessage_bg.html | 8 +- .../help/system-config/systemMessage_de.html | 9 +- .../help/system-config/systemMessage_fr.html | 10 +- .../help/system-config/systemMessage_it.html | 6 +- .../help/system-config/systemMessage_ja.html | 6 +- .../system-config/systemMessage_pt_BR.html | 7 +- .../help/system-config/systemMessage_ru.html | 9 +- .../help/system-config/systemMessage_tr.html | 10 +- .../system-config/systemMessage_zh_TW.html | 7 +- .../tasks/fingerprint/keepDependencies.html | 27 +- .../fingerprint/keepDependencies_bg.html | 26 +- .../fingerprint/keepDependencies_de.html | 33 +- .../fingerprint/keepDependencies_fr.html | 32 +- .../fingerprint/keepDependencies_it.html | 33 +- .../fingerprint/keepDependencies_ja.html | 27 +- .../fingerprint/keepDependencies_nl.html | 41 +- .../fingerprint/keepDependencies_pt_BR.html | 31 +- .../fingerprint/keepDependencies_ru.html | 31 +- .../fingerprint/keepDependencies_tr.html | 34 +- .../fingerprint/keepDependencies_zh_TW.html | 18 +- .../main/webapp/help/tools/help-label.html | 6 +- .../main/webapp/help/tools/help-label_bg.html | 8 +- .../main/webapp/help/tools/help-label_de.html | 4 +- .../main/webapp/help/tools/help-label_it.html | 10 +- .../main/webapp/help/tools/help-label_ja.html | 4 +- .../webapp/help/tools/help-label_pt_BR.html | 7 +- .../webapp/help/tools/help-label_zh_TW.html | 5 +- .../tools/tool-location-node-property.html | 5 +- .../tools/tool-location-node-property_bg.html | 7 +- .../tools/tool-location-node-property_de.html | 10 +- .../tools/tool-location-node-property_fr.html | 3 +- .../tools/tool-location-node-property_it.html | 9 +- .../tool-location-node-property_pt_BR.html | 6 +- .../main/webapp/help/user/description.html | 6 +- .../main/webapp/help/user/description_bg.html | 7 +- .../main/webapp/help/user/description_de.html | 8 +- .../main/webapp/help/user/description_fr.html | 9 +- .../main/webapp/help/user/description_it.html | 10 +- .../main/webapp/help/user/description_ja.html | 2 +- .../main/webapp/help/user/description_nl.html | 12 +- .../webapp/help/user/description_pt_BR.html | 5 +- .../main/webapp/help/user/description_ru.html | 6 +- .../main/webapp/help/user/description_tr.html | 11 +- .../webapp/help/user/description_zh_TW.html | 6 +- war/src/main/webapp/help/user/fullName.html | 6 +- .../main/webapp/help/user/fullName_bg.html | 2 +- .../main/webapp/help/user/fullName_de.html | 10 +- .../main/webapp/help/user/fullName_fr.html | 6 +- .../main/webapp/help/user/fullName_ja.html | 2 +- .../main/webapp/help/user/fullName_nl.html | 7 +- .../main/webapp/help/user/fullName_pt_BR.html | 7 +- .../main/webapp/help/user/fullName_ru.html | 8 +- .../main/webapp/help/user/fullName_tr.html | 9 +- .../main/webapp/help/user/fullName_zh_TW.html | 2 +- .../webapp/help/view-config/description.html | 5 +- .../help/view-config/description_bg.html | 10 +- .../help/view-config/description_de.html | 11 +- .../help/view-config/description_fr.html | 10 +- .../help/view-config/description_it.html | 9 +- .../help/view-config/description_ja.html | 4 +- .../help/view-config/description_nl.html | 12 +- .../help/view-config/description_pt_BR.html | 7 +- .../help/view-config/description_ru.html | 8 +- .../help/view-config/description_tr.html | 8 +- .../help/view-config/description_zh_TW.html | 8 +- .../help/view-config/filter-executors.html | 5 +- .../help/view-config/filter-executors_bg.html | 4 +- .../help/view-config/filter-executors_de.html | 6 +- .../help/view-config/filter-executors_it.html | 4 +- .../help/view-config/filter-executors_ja.html | 4 +- .../view-config/filter-executors_pt_BR.html | 3 +- .../view-config/filter-executors_zh_TW.html | 4 +- .../webapp/help/view-config/filter-queue.html | 4 +- .../help/view-config/filter-queue_bg.html | 4 +- .../help/view-config/filter-queue_de.html | 2 +- .../help/view-config/filter-queue_it.html | 4 +- .../help/view-config/filter-queue_ja.html | 4 +- .../help/view-config/filter-queue_pt_BR.html | 4 +- .../help/view-config/filter-queue_zh_TW.html | 4 +- .../webapp/help/view-config/includeregex.html | 18 +- .../help/view-config/includeregex_bg.html | 15 +- .../help/view-config/includeregex_de.html | 2 +- .../help/view-config/includeregex_fr.html | 6 +- .../help/view-config/includeregex_it.html | 13 +- .../help/view-config/includeregex_ja.html | 20 +- .../help/view-config/includeregex_nl.html | 8 +- .../help/view-config/includeregex_pt_BR.html | 7 +- .../help/view-config/includeregex_ru.html | 6 +- .../help/view-config/includeregex_tr.html | 7 +- .../help/view-config/includeregex_zh_TW.html | 12 +- .../webapp/help/view-config/statusFilter.html | 4 +- .../help/view-config/statusFilter_bg.html | 4 +- .../help/view-config/statusFilter_ja.html | 4 +- .../help/view-config/statusFilter_zh_TW.html | 4 +- war/src/main/webapp/scripts/combobox.js | 490 +- .../main/webapp/scripts/hudson-behavior.js | 4246 +++++++++-------- war/src/main/webapp/scripts/loading.js | 66 +- war/src/main/webapp/scripts/msie.js | 16 +- war/src/main/webapp/scripts/polyfills.js | 33 +- war/src/main/webapp/scripts/sortable.js | 720 +-- war/src/main/webapp/scripts/utilities.js | 72 +- war/src/test/js/pluginSetupWizard.spec.js | 964 ++-- .../config/freestyle-config-scrollspy.html | 481 +- .../config/freestyle-config-scrollspy_bg.html | 490 +- .../config/freestyle-config-tabbed.html | 427 +- .../config/freestyle-config-tabbed_bg.html | 454 +- war/src/test/js/widgets/config/mocks.js | 31 +- war/src/test/js/widgets/config/tabbar.spec.js | 427 +- war/webpack.config.js | 117 +- 1076 files changed, 23437 insertions(+), 18121 deletions(-) diff --git a/.github/PULL_REQUEST_TEMPLATE.md b/.github/PULL_REQUEST_TEMPLATE.md index 571c3a747a..67f2ce66b2 100644 --- a/.github/PULL_REQUEST_TEMPLATE.md +++ b/.github/PULL_REQUEST_TEMPLATE.md @@ -1,11 +1,12 @@ - + See [JENKINS-XXXXX](https://issues.jenkins.io/browse/JENKINS-XXXXX). - @@ -49,7 +50,7 @@ If you need an accelerated review process by the community (e.g., for critical b ### Maintainer checklist -Before the changes are marked as `ready-for-merge`: +Before the changes are marked as `ready-for-merge`: - [ ] There are at least 2 approvals for the pull request and no outstanding requests for change - [ ] Conversations in the pull request are over OR it is explicit that a reviewer does not block the change diff --git a/.github/dependabot.yml b/.github/dependabot.yml index 2598142fdb..db5e5cd7f9 100644 --- a/.github/dependabot.yml +++ b/.github/dependabot.yml @@ -16,7 +16,7 @@ updates: # see https://github.com/jenkinsci/jenkins/pull/5184 should be updated with groovy-all - dependency-name: "org.fusesource.jansi:jansi" # see https://github.com/jenkinsci/jenkins/pull/5144#pullrequestreview-559661934 - # will require source code changes to replace javax.mail with jakarta.mail + # will require source code changes to replace javax.mail with jakarta.mail # and some handling for plugins that depend on javax.mail being provided by Jenkins core. - dependency-name: "com.sun.mail:jakarta.mail" # this is a banned dependency, we have a hack in our pom to prevent anyone else pulling it in diff --git a/.github/release-drafter.yml b/.github/release-drafter.yml index 9013d1a824..dea378b71a 100644 --- a/.github/release-drafter.yml +++ b/.github/release-drafter.yml @@ -10,5 +10,5 @@ template: | See https://www.jenkins.io/changelog/ for the official changelogs._ $CHANGES - + All contributors: $CONTRIBUTORS diff --git a/.github/workflows/publish-release-artifact.yml b/.github/workflows/publish-release-artifact.yml index 5605510b6a..901be22b0e 100644 --- a/.github/workflows/publish-release-artifact.yml +++ b/.github/workflows/publish-release-artifact.yml @@ -15,7 +15,7 @@ jobs: - name: Set up JDK 8 uses: actions/setup-java@v3 with: - distribution: 'temurin' + distribution: "temurin" java-version: 8 - name: Set version id: set-version @@ -193,7 +193,7 @@ jobs: echo $REPO - wget -q https://get.jenkins.io/${REPO}/jenkins-${PROJECT_VERSION}-1.2.noarch.rpm -O ${OUTPUT_FILE_NAME} + wget -q https://get.jenkins.io/${REPO}/jenkins-${PROJECT_VERSION}-1.2.noarch.rpm -O ${OUTPUT_FILE_NAME} - name: Upload Release Asset id: upload-suse-rpm if: always() diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 8eb9822ccd..fec9308025 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -9,13 +9,15 @@ This page provides information about contributing code to the Jenkins core codeb 1. Fork the repository on GitHub 2. Clone the forked repository to your machine 3. Install the necessary development tools. In order to develop Jenkins, you need the following: - * Java Development Kit (JDK) 11 or 8. - In the Jenkins project we usually use [Eclipse Adoptium](https://adoptium.net/) or [OpenJDK](https://openjdk.java.net/), but you can use other JDKs as well. - * Apache Maven 3.8.1 or above. You can [download Maven here]. - In the Jenkins project we usually use the most recent Maven release. - * Any IDE which supports importing Maven projects. - * Install [NodeJS](https://nodejs.org/en/). **Note:** only needed to work on the frontend assets found in the `war` module. - * Frontend tasks are run using [yarn](https://yarnpkg.com/lang/en/). Run `npm install -g yarn` to install it. + +- Java Development Kit (JDK) 11 or 8. + In the Jenkins project we usually use [Eclipse Adoptium](https://adoptium.net/) or [OpenJDK](https://openjdk.java.net/), but you can use other JDKs as well. +- Apache Maven 3.8.1 or above. You can [download Maven here]. + In the Jenkins project we usually use the most recent Maven release. +- Any IDE which supports importing Maven projects. +- Install [NodeJS](https://nodejs.org/en/). **Note:** only needed to work on the frontend assets found in the `war` module. + - Frontend tasks are run using [yarn](https://yarnpkg.com/lang/en/). Run `npm install -g yarn` to install it. + 4. Set up your development environment as described in [Preparing for Plugin Development] If you want to contribute to Jenkins, or just learn about the project, @@ -53,11 +55,13 @@ mvn -pl war jetty:run To work on the `war` module frontend assets, two processes are needed at the same time: On one terminal, start a development server that will not process frontend assets: + ```sh mvn -pl war jetty:run -Dskip.yarn ``` On another terminal, move to the war folder and start a [webpack](https://webpack.js.org/) dev server: + ```sh cd war; yarn start ``` @@ -72,9 +76,9 @@ so there is no strict need to run full test suites before proposing a pull reque There are 3 profiles for tests: -* `light-test` - runs only unit tests, no functional tests -* `smoke-test` - runs unit tests + a number of functional tests -* `all-tests` - runs all tests, with re-run (default) +- `light-test` - runs only unit tests, no functional tests +- `smoke-test` - runs unit tests + a number of functional tests +- `all-tests` - runs all tests, with re-run (default) In addition to the included tests, you can also find extra integration and UI tests in the [Acceptance Test Harness (ATH)] repository. @@ -83,6 +87,7 @@ If you propose complex UI changes, you should create new ATH tests for them. ### JavaScript unit tests In case there's only need to run the JS tests: + ```sh cd war; yarn test ``` @@ -95,18 +100,21 @@ All proposed changes are submitted, and code reviewed, using a [GitHub pull requ To submit a pull request: 1. Commit your changes and push them to your fork on GitHub. -It is a good practice is to create branches instead of pushing to master. + It is a good practice is to create branches instead of pushing to master. 2. In the GitHub Web UI, click the _New Pull Request_ button. 3. Select `jenkinsci` as _base fork_ and `master` as `base`, then click _Create Pull Request_. - * We integrate all changes into the master branch towards the Weekly releases. - * After that, the changes may be backported to the current LTS baseline by the LTS Team. - Read more about the [backporting process]. + +- We integrate all changes into the master branch towards the Weekly releases. +- After that, the changes may be backported to the current LTS baseline by the LTS Team. + Read more about the [backporting process]. + 4. Fill in the Pull Request description according to the [proposed template]. 5. Click _Create Pull Request_. 6. Wait for CI results/reviews, process the feedback. - * If you do not get feedback after 3 days, feel free to ping `@jenkinsci/core-pr-reviewers` in the comments. - * Usually we merge pull requests after 2 approvals from reviewers, no requested changes, and having waited some more time to give others an opportunity to provide their feedback. - See [this page](/docs/MAINTAINERS.adoc) for more information about our review process. + +- If you do not get feedback after 3 days, feel free to ping `@jenkinsci/core-pr-reviewers` in the comments. +- Usually we merge pull requests after 2 approvals from reviewers, no requested changes, and having waited some more time to give others an opportunity to provide their feedback. + See [this page](/docs/MAINTAINERS.adoc) for more information about our review process. Once your Pull Request is ready to be merged, the repository maintainers will integrate it, prepare changelogs, and @@ -120,26 +128,26 @@ The complete list of labels can be found at https://github.com/jenkinsci/jenkins These labels are defined as follows: - `needs-docs` marks a pull request as lacking documentation, either for developers (e.g., Javadoc) or users (e.g., changes to the [Jenkins handbook](https://www.jenkins.io/doc/book/)). -For such pull requests to be approved and merged, the corresponding changes to the documentation should be proposed. -If those changes belong to a separate repository (e.g., `jenkins-infra/jenkins.io`), a secondary pull request should be created in draft state in the other repository and reviewed in tandem with the primary pull request that proposes the code change. + For such pull requests to be approved and merged, the corresponding changes to the documentation should be proposed. + If those changes belong to a separate repository (e.g., `jenkins-infra/jenkins.io`), a secondary pull request should be created in draft state in the other repository and reviewed in tandem with the primary pull request that proposes the code change. - `needs-fix` marks a pull request which has pending requests for change that have not yet been addressed. -Such pull requests will not be merged until the code has been fixed and the tests pass. + Such pull requests will not be merged until the code has been fixed and the tests pass. - `needs-justification` marks a pull request where the reasoning is unclear, incomplete or not entirely cogent. -To properly evaluate the solution provided in a pull request, maintainers must be able to understand the high-level problem that the pull request attempts to solve. -While the context might be obvious to the author, it is not always apparent to reviewers and maintainers. -The use of design documents, high-level tracking epics, [minimal reproducible examples (MREs)](https://en.wikipedia.org/wiki/Minimal_reproducible_example), etc. is strongly encouraged. + To properly evaluate the solution provided in a pull request, maintainers must be able to understand the high-level problem that the pull request attempts to solve. + While the context might be obvious to the author, it is not always apparent to reviewers and maintainers. + The use of design documents, high-level tracking epics, [minimal reproducible examples (MREs)](https://en.wikipedia.org/wiki/Minimal_reproducible_example), etc. is strongly encouraged. - `needs-more-review` marks a pull request as lacking a sufficient number of reviews from subject-matter expert(s) (SME), either because the changes are complex and not sufficiently explained or because there is a lack of consensus regarding the proposed solution. - `on-hold` marks a pull request that depends on another event and cannot be merged until the completion of that event. -When the dependent task has been completed, the pull request will be ready for merge. + When the dependent task has been completed, the pull request will be ready for merge. - `proposed-for-close` marks a pull request where there is either no consensus on the next steps or where the next steps have not been taken and an extended period of time has elapsed. -Such pull requests are typically closed approximately one week after the label has been applied. -They can always be reopened once consensus has been reached on the next steps or when action is taken regarding these next steps. + Such pull requests are typically closed approximately one week after the label has been applied. + They can always be reopened once consensus has been reached on the next steps or when action is taken regarding these next steps. - `ready-for-merge` marks a pull request that has met the acceptance criteria, as defined elsewhere in this document. -If there is no negative feedback, such pull requests are typically merged within approximately 24 hours. + If there is no negative feedback, such pull requests are typically merged within approximately 24 hours. - `stalled` marks a pull request that is off to a promising start but requires additional effort to reach completion - effort that appears to have been abandoned. -If the original author lacks the time and interest to continue the original effort, we suggest that someone else pick up where the original author left off to drive the effort to completion. + If the original author lacks the time and interest to continue the original effort, we suggest that someone else pick up where the original author left off to drive the effort to completion. - `work-in-progress` marks a pull request that remains under active development. -Such pull requests are not ready for final review. + Such pull requests are not ready for final review. To ensure that pull requests are processed efficiently, the `ready-for-merge`, `stalled`, and `proposed-for-close` labels are subject to time constraints. @@ -162,7 +170,7 @@ The setting can be found in Settings -> Editor -> General -> On Save -> Remove t This will help minimize the diff, which makes reviewing PRs easier. We also do not recommend `*` imports in the production code. -Please disable them in Settings > Editor > Codestyle > Java by setting _Class count to use import with '*'_ and Names count to use import with '*'_ to a high value, e.g. 100. +Please disable them in Settings > Editor > Codestyle > Java by setting _Class count to use import with '\*'_ and Names count to use import with '\*'\_ to a high value, e.g. 100. The addition of `@{jenkins.addOpens}` to `argLine` exposes a bug in IntelliJ IDEA. A patch has been proposed in [JetBrains/intellij-community#1976](https://github.com/JetBrains/intellij-community/pull/1976). @@ -199,25 +207,25 @@ just submit a pull request. # Links -* [Jenkins Contribution Landing Page](https://www.jenkins.io/participate/) -* [Jenkins Chat Channels](https://www.jenkins.io/chat/) -* [Beginners Guide To Contributing](https://www.jenkins.io/participate/) -* [List of newbie-friendly issues in the core](https://issues.jenkins.io/issues/?jql=project%20%3D%20JENKINS%20AND%20status%20in%20(Open%2C%20%22In%20Progress%22%2C%20Reopened)%20AND%20component%20%3D%20core%20AND%20labels%20in%20(newbie-friendly)) +- [Jenkins Contribution Landing Page](https://www.jenkins.io/participate/) +- [Jenkins Chat Channels](https://www.jenkins.io/chat/) +- [Beginners Guide To Contributing](https://www.jenkins.io/participate/) +- [List of newbie-friendly issues in the core]() -[Preparing for Plugin Development]: https://www.jenkins.io/doc/developer/tutorial/prepare/ +[preparing for plugin development]: https://www.jenkins.io/doc/developer/tutorial/prepare/ [newbie friendly issues]: https://issues.jenkins.io/issues/?jql=project%20%3D%20JENKINS%20AND%20status%20in%20(Open%2C%20%22In%20Progress%22%2C%20Reopened)%20AND%20component%20%3D%20core%20AND%20labels%20in%20(newbie-friendly) -[Participate]: https://www.jenkins.io/participate/ +[participate]: https://www.jenkins.io/participate/ [building and debugging process here]: https://www.jenkins.io/doc/developer/building/ [guide]: https://www.jenkins.io/doc/book/installing/war-file/#run-the-war-file -[Remote Debug Flags]: https://stackoverflow.com/questions/975271/remote-debugging-a-java-application -[Acceptance Test Harness (ATH)]: https://github.com/jenkinsci/acceptance-test-harness +[remote debug flags]: https://stackoverflow.com/questions/975271/remote-debugging-a-java-application +[acceptance test harness (ath)]: https://github.com/jenkinsci/acceptance-test-harness [backporting process]: https://www.jenkins.io/download/lts/ [proposed template]: .github/PULL_REQUEST_TEMPLATE.md -[MIT license]: ./LICENSE.txt +[mit license]: ./LICENSE.txt [contributor agreement]: https://www.jenkins.io/project/governance/#cla -[Jenkins Security Team]: https://www.jenkins.io/security/#team +[jenkins security team]: https://www.jenkins.io/security/#team [ci.jenkins.io]: https://ci.jenkins.io/ -[Jenkins Pipeline]: https://www.jenkins.io/doc/book/pipeline/ -[Jenkinsfile]: ./Jenkinsfile -[download Maven here]: https://maven.apache.org/download.cgi -[GitHub pull request]: https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests \ No newline at end of file +[jenkins pipeline]: https://www.jenkins.io/doc/book/pipeline/ +[jenkinsfile]: ./Jenkinsfile +[download maven here]: https://maven.apache.org/download.cgi +[github pull request]: https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests diff --git a/README.md b/README.md index ecf83732aa..8bdb2726a0 100644 --- a/README.md +++ b/README.md @@ -1,4 +1,4 @@ -[![][ButlerImage]][website] +[![][butlerimage]][website] # About @@ -7,8 +7,8 @@ [![Docker Pulls](https://img.shields.io/docker/pulls/jenkins/jenkins.svg)](https://hub.docker.com/r/jenkins/jenkins/) [![CII Best Practices](https://bestpractices.coreinfrastructure.org/projects/3538/badge)](https://bestpractices.coreinfrastructure.org/projects/3538) -In a nutshell, Jenkins is the leading open-source automation server. -Built with Java, it provides over 1,700 [plugins](https://plugins.jenkins.io/) to support automating virtually anything, +In a nutshell, Jenkins is the leading open-source automation server. +Built with Java, it provides over 1,700 [plugins](https://plugins.jenkins.io/) to support automating virtually anything, so that humans can spend their time doing things machines cannot. # What to Use Jenkins for and When to Use It @@ -29,17 +29,17 @@ See the [Downloads](https://www.jenkins.io/download) page for references. For all distributions Jenkins offers two release lines: -* [Weekly](https://www.jenkins.io/download/weekly/) - +- [Weekly](https://www.jenkins.io/download/weekly/) - Frequent releases which include all new features, improvements, and bug fixes. -* [Long-Term Support (LTS)](https://www.jenkins.io/download/lts/) - +- [Long-Term Support (LTS)](https://www.jenkins.io/download/lts/) - Older release line which gets periodically updated via bug fix backports. Latest releases: [![Jenkins Regular Release](https://img.shields.io/endpoint?url=https%3A%2F%2Fwww.jenkins.io%2Fchangelog%2Fbadge.json)](https://www.jenkins.io/changelog) [![Jenkins LTS Release](https://img.shields.io/endpoint?url=https%3A%2F%2Fwww.jenkins.io%2Fchangelog-stable%2Fbadge.json)](https://www.jenkins.io/changelog-stable) - # Source + Our latest and greatest source of Jenkins can be found on [GitHub]. Fork us! # Contributing to Jenkins @@ -66,11 +66,11 @@ Jenkins is used by millions of users and thousands of companies. See [adopters](https://www.jenkins.io/project/adopters/) for the list of Jenkins adopters and their success stories. # License -Jenkins is **licensed** under the **[MIT License]**. +Jenkins is **licensed** under the **[MIT License]**. -[ButlerImage]: https://www.jenkins.io/sites/default/files/jenkins_logo.png -[MIT License]: https://github.com/jenkinsci/jenkins/blob/master/LICENSE.txt -[Mirrors]: http://mirrors.jenkins-ci.org -[GitHub]: https://github.com/jenkinsci/jenkins +[butlerimage]: https://www.jenkins.io/sites/default/files/jenkins_logo.png +[mit license]: https://github.com/jenkinsci/jenkins/blob/master/LICENSE.txt +[mirrors]: http://mirrors.jenkins-ci.org +[github]: https://github.com/jenkinsci/jenkins [website]: https://www.jenkins.io/ diff --git a/changelog.html b/changelog.html index 20a2db735b..cf08ed0484 100644 --- a/changelog.html +++ b/changelog.html @@ -12,4 +12,4 @@ https://github.com/jenkins-infra/jenkins.io/blob/master/content/_data/changelogs Be sure to use PRs for changes to these files, as malformed files WILL result in build failures of the jenkins.io static site generation. ---> \ No newline at end of file +--> diff --git a/core/src/main/java/hudson/model/listeners/package.html b/core/src/main/java/hudson/model/listeners/package.html index 395a670b18..71ea3a6b85 100644 --- a/core/src/main/java/hudson/model/listeners/package.html +++ b/core/src/main/java/hudson/model/listeners/package.html @@ -22,6 +22,9 @@ OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. --> - -Listener interfaces for various events that occur inside the server. - \ No newline at end of file + + + + Listener interfaces for various events that occur inside the server. + + diff --git a/core/src/main/java/hudson/model/package.html b/core/src/main/java/hudson/model/package.html index 73e34b62da..3632b7739a 100644 --- a/core/src/main/java/hudson/model/package.html +++ b/core/src/main/java/hudson/model/package.html @@ -22,6 +22,11 @@ OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. --> - -Core object model that are bound to URLs via stapler, rooted at Hudson. - \ No newline at end of file + + + + Core object model that are bound to URLs via stapler, rooted at + Hudson + . + + diff --git a/core/src/main/java/hudson/node_monitors/package.html b/core/src/main/java/hudson/node_monitors/package.html index e178fe411c..f14c78e9a6 100644 --- a/core/src/main/java/hudson/node_monitors/package.html +++ b/core/src/main/java/hudson/node_monitors/package.html @@ -22,6 +22,9 @@ OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. --> - -Code that monitors the health of agents - \ No newline at end of file + + + + Code that monitors the health of agents + + diff --git a/core/src/main/java/hudson/scheduler/package.html b/core/src/main/java/hudson/scheduler/package.html index 6809b27ad9..b3e74b006c 100644 --- a/core/src/main/java/hudson/scheduler/package.html +++ b/core/src/main/java/hudson/scheduler/package.html @@ -22,6 +22,9 @@ OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. --> - -Classes that implement cron-like features - \ No newline at end of file + + + + Classes that implement cron-like features + + diff --git a/core/src/main/java/hudson/scm/browsers/package.html b/core/src/main/java/hudson/scm/browsers/package.html index 34cdf0e8af..0b0d0c01f7 100644 --- a/core/src/main/java/hudson/scm/browsers/package.html +++ b/core/src/main/java/hudson/scm/browsers/package.html @@ -22,6 +22,9 @@ OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. --> - -Code that computes links to external source code repository browsers. - \ No newline at end of file + + + + Code that computes links to external source code repository browsers. + + diff --git a/core/src/main/java/hudson/scm/package.html b/core/src/main/java/hudson/scm/package.html index d2a0046c66..574cfc33d9 100644 --- a/core/src/main/java/hudson/scm/package.html +++ b/core/src/main/java/hudson/scm/package.html @@ -22,6 +22,10 @@ OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. --> - -Hudson's interface with source code management systems. Start with SCM - \ No newline at end of file + + + + Hudson's interface with source code management systems. Start with + SCM + + diff --git a/core/src/main/java/hudson/search/package.html b/core/src/main/java/hudson/search/package.html index 2626d06125..55c4fae299 100644 --- a/core/src/main/java/hudson/search/package.html +++ b/core/src/main/java/hudson/search/package.html @@ -22,7 +22,10 @@ OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. --> - -QuickSilver-like -search/jump capability for better navigation around the website. - \ No newline at end of file + + + + QuickSilver + -like search/jump capability for better navigation around the website. + + diff --git a/core/src/main/java/hudson/security/package.html b/core/src/main/java/hudson/security/package.html index 833be9b59f..0b49408e34 100644 --- a/core/src/main/java/hudson/security/package.html +++ b/core/src/main/java/hudson/security/package.html @@ -22,7 +22,10 @@ OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. --> - -Security-related code. -See: Security - + + + + Security-related code. See: + Security + + diff --git a/core/src/main/java/hudson/slaves/package.html b/core/src/main/java/hudson/slaves/package.html index a5080940f2..3293958f04 100644 --- a/core/src/main/java/hudson/slaves/package.html +++ b/core/src/main/java/hudson/slaves/package.html @@ -22,6 +22,9 @@ OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. --> - -Code related to agents. - \ No newline at end of file + + + + Code related to agents. + + diff --git a/core/src/main/java/hudson/tasks/package.html b/core/src/main/java/hudson/tasks/package.html index 3ecc377e25..6e0811792b 100644 --- a/core/src/main/java/hudson/tasks/package.html +++ b/core/src/main/java/hudson/tasks/package.html @@ -22,7 +22,13 @@ OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. --> - -Built-in Builders and Publishers -that perform the actual heavy-lifting of a build. - + + + + Built-in + Builder + s and + Publisher + s that perform the actual heavy-lifting of a build. + + diff --git a/core/src/main/java/hudson/triggers/package.html b/core/src/main/java/hudson/triggers/package.html index dd0f97ed8b..4e802ae0df 100644 --- a/core/src/main/java/hudson/triggers/package.html +++ b/core/src/main/java/hudson/triggers/package.html @@ -22,6 +22,11 @@ OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. --> - -Built-in Triggers that run periodically to kick a new build. - \ No newline at end of file + + + + Built-in + Trigger + s that run periodically to kick a new build. + + diff --git a/core/src/main/java/hudson/util/package.html b/core/src/main/java/hudson/util/package.html index 0975306853..8b7b433dc6 100644 --- a/core/src/main/java/hudson/util/package.html +++ b/core/src/main/java/hudson/util/package.html @@ -22,6 +22,9 @@ OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. --> - -Other miscellaneous utility code - \ No newline at end of file + + + + Other miscellaneous utility code + + diff --git a/core/src/main/resources/hudson/PluginManager/_table.js b/core/src/main/resources/hudson/PluginManager/_table.js index 45e431338c..426819373d 100644 --- a/core/src/main/resources/hudson/PluginManager/_table.js +++ b/core/src/main/resources/hudson/PluginManager/_table.js @@ -1,426 +1,490 @@ function checkPluginsWithoutWarnings() { - var inputs = document.getElementsByTagName('input'); - for(var i = 0; i < inputs.length; i++) { - var candidate = inputs[i]; - if(candidate.type === "checkbox" && !candidate.disabled) { - candidate.checked = candidate.dataset.compatWarning === 'false'; - } + var inputs = document.getElementsByTagName("input"); + for (var i = 0; i < inputs.length; i++) { + var candidate = inputs[i]; + if (candidate.type === "checkbox" && !candidate.disabled) { + candidate.checked = candidate.dataset.compatWarning === "false"; } + } } -Behaviour.specify("#filter-box", '_table', 0, function(e) { - function applyFilter() { - var filter = e.value.toLowerCase().trim(); - var filterParts = filter.split(/ +/).filter (function(word) { return word.length > 0; }); - var items = document.getElementsBySelector("TR.plugin").concat(document.getElementsBySelector("TR.unavailable")); - var anyVisible = false; - for (var i=0; i 0; + }); + var items = document + .getElementsBySelector("TR.plugin") + .concat(document.getElementsBySelector("TR.unavailable")); + var anyVisible = false; + for (var i = 0; i < items.length; i++) { + if ( + (filterParts.length < 1 || filter.length < 2) && + items[i].hasClassName("hidden-by-default") + ) { + items[i].addClassName("jenkins-hidden"); + continue; + } + var makeVisible = true; + + var pluginId = items[i].getAttribute("data-plugin-id"); + var content = ( + items[i].querySelector(".details").innerText + + " " + + pluginId + ).toLowerCase(); + + for (var j = 0; j < filterParts.length; j++) { + var part = filterParts[j]; + if (content.indexOf(part) < 0) { + makeVisible = false; + break; } - - layoutUpdateCallback.call(); + } + + if (makeVisible) { + items[i].classList.remove("jenkins-hidden"); + anyVisible = true; + } else { + items[i].classList.add("jenkins-hidden"); + } + } + var instructions = document.getElementById( + "hidden-by-default-instructions" + ); + if (instructions) { + instructions.style.display = anyVisible ? "none" : ""; } - e.addEventListener("input", () => applyFilter()); - (function() { - var instructionsTd = document.getElementById("hidden-by-default-instructions-td"); - if (instructionsTd) { // only on Available tab - instructionsTd.innerText = instructionsTd.getAttribute("data-loaded-text"); - } - applyFilter(); - }()); + layoutUpdateCallback.call(); + } + e.addEventListener("input", () => applyFilter()); + + (function () { + var instructionsTd = document.getElementById( + "hidden-by-default-instructions-td" + ); + if (instructionsTd) { + // only on Available tab + instructionsTd.innerText = + instructionsTd.getAttribute("data-loaded-text"); + } + applyFilter(); + })(); }); /** * Code for handling the enable/disable behavior based on plugin * dependencies and dependents. */ -(function(){ - function selectAll(selector, element) { - if (element) { - return $(element).select(selector); - } else { - return Element.select(undefined, selector); - } +(function () { + function selectAll(selector, element) { + if (element) { + return $(element).select(selector); + } else { + return Element.select(undefined, selector); } - function select(selector, element) { - var elementsBySelector = selectAll(selector, element); - if (elementsBySelector.length > 0) { - return elementsBySelector[0]; - } else { - return undefined; - } + } + function select(selector, element) { + var elementsBySelector = selectAll(selector, element); + if (elementsBySelector.length > 0) { + return elementsBySelector[0]; + } else { + return undefined; } + } - /** - * Wait for document onload. - */ - Element.observe(window, "load", function() { - var pluginsTable = select('#plugins'); - var pluginTRs = selectAll('.plugin', pluginsTable); - - if (!pluginTRs) { - return; - } + /** + * Wait for document onload. + */ + Element.observe(window, "load", function () { + var pluginsTable = select("#plugins"); + var pluginTRs = selectAll(".plugin", pluginsTable); - var pluginI18n = select('.plugins.i18n'); - function i18n(messageId) { - return pluginI18n.getAttribute('data-' + messageId); - } - - // Create a map of the plugin rows, making it easy to index them. - var plugins = {}; - for (var i = 0; i < pluginTRs.length; i++) { - var pluginTR = pluginTRs[i]; - var pluginId = pluginTR.getAttribute('data-plugin-id'); - - plugins[pluginId] = pluginTR; - } - - function getPluginTR(pluginId) { - return plugins[pluginId]; - } - function getPluginName(pluginId) { - var pluginTR = getPluginTR(pluginId); - if (pluginTR) { - return pluginTR.getAttribute('data-plugin-name'); - } else { - return pluginId; - } - } - - function processSpanSet(spans) { - var ids = []; - for (var i = 0; i < spans.length; i++) { - var span = spans[i]; - var pluginId = span.getAttribute('data-plugin-id'); - var pluginName = getPluginName(pluginId); - - span.update(pluginName); - ids.push(pluginId); - } - return ids; - } - - function markAllDependentsDisabled(pluginTR) { - var jenkinsPluginMetadata = pluginTR.jenkinsPluginMetadata; - var dependentIds = jenkinsPluginMetadata.dependentIds; - - if (dependentIds) { - // If the only dependent is jenkins-core (it's a bundle plugin), then lets - // treat it like all its dependents are disabled. We're really only interested in - // dependent plugins in this case. - // Note: This does not cover "implied" dependencies ala detached plugins. See https://goo.gl/lQHrUh - if (dependentIds.length === 1 && dependentIds[0] === 'jenkins-core') { - pluginTR.addClassName('all-dependents-disabled'); - return; - } - - for (var i = 0; i < dependentIds.length; i++) { - var dependentId = dependentIds[i]; - - if (dependentId === 'jenkins-core') { - // Jenkins core is always enabled. So, make sure it's not possible to disable/uninstall - // any plugins that it "depends" on. (we sill have bundled plugins) - pluginTR.removeClassName('all-dependents-disabled'); - return; - } - - // The dependent is a plugin.... - var dependentPluginTr = getPluginTR(dependentId); - if (dependentPluginTr && dependentPluginTr.jenkinsPluginMetadata.enableInput.checked) { - // One of the plugins that depend on this plugin, is marked as enabled. - pluginTR.removeClassName('all-dependents-disabled'); - return; - } - } - } - - pluginTR.addClassName('all-dependents-disabled'); + if (!pluginTRs) { + return; + } + + var pluginI18n = select(".plugins.i18n"); + function i18n(messageId) { + return pluginI18n.getAttribute("data-" + messageId); + } + + // Create a map of the plugin rows, making it easy to index them. + var plugins = {}; + for (var i = 0; i < pluginTRs.length; i++) { + var pluginTR = pluginTRs[i]; + var pluginId = pluginTR.getAttribute("data-plugin-id"); + + plugins[pluginId] = pluginTR; + } + + function getPluginTR(pluginId) { + return plugins[pluginId]; + } + function getPluginName(pluginId) { + var pluginTR = getPluginTR(pluginId); + if (pluginTR) { + return pluginTR.getAttribute("data-plugin-name"); + } else { + return pluginId; + } + } + + function processSpanSet(spans) { + var ids = []; + for (var i = 0; i < spans.length; i++) { + var span = spans[i]; + var pluginId = span.getAttribute("data-plugin-id"); + var pluginName = getPluginName(pluginId); + + span.update(pluginName); + ids.push(pluginId); + } + return ids; + } + + function markAllDependentsDisabled(pluginTR) { + var jenkinsPluginMetadata = pluginTR.jenkinsPluginMetadata; + var dependentIds = jenkinsPluginMetadata.dependentIds; + + if (dependentIds) { + // If the only dependent is jenkins-core (it's a bundle plugin), then lets + // treat it like all its dependents are disabled. We're really only interested in + // dependent plugins in this case. + // Note: This does not cover "implied" dependencies ala detached plugins. See https://goo.gl/lQHrUh + if (dependentIds.length === 1 && dependentIds[0] === "jenkins-core") { + pluginTR.addClassName("all-dependents-disabled"); + return; } - function markHasDisabledDependencies(pluginTR) { - var jenkinsPluginMetadata = pluginTR.jenkinsPluginMetadata; - var dependencyIds = jenkinsPluginMetadata.dependencyIds; - - if (dependencyIds) { - for (var i = 0; i < dependencyIds.length; i++) { - var dependencyPluginTr = getPluginTR(dependencyIds[i]); - if (dependencyPluginTr && !dependencyPluginTr.jenkinsPluginMetadata.enableInput.checked) { - // One of the plugins that this plugin depend on, is marked as disabled. - pluginTR.addClassName('has-disabled-dependency'); - return; - } - } - } - - pluginTR.removeClassName('has-disabled-dependency'); + for (var i = 0; i < dependentIds.length; i++) { + var dependentId = dependentIds[i]; + + if (dependentId === "jenkins-core") { + // Jenkins core is always enabled. So, make sure it's not possible to disable/uninstall + // any plugins that it "depends" on. (we sill have bundled plugins) + pluginTR.removeClassName("all-dependents-disabled"); + return; + } + + // The dependent is a plugin.... + var dependentPluginTr = getPluginTR(dependentId); + if ( + dependentPluginTr && + dependentPluginTr.jenkinsPluginMetadata.enableInput.checked + ) { + // One of the plugins that depend on this plugin, is marked as enabled. + pluginTR.removeClassName("all-dependents-disabled"); + return; + } } - - function setEnableWidgetStates() { - for (var i = 0; i < pluginTRs.length; i++) { - var pluginMetadata = pluginTRs[i].jenkinsPluginMetadata; - if (pluginTRs[i].hasClassName('has-dependents-but-disabled')) { - if (pluginMetadata.enableInput.checked) { - pluginTRs[i].removeClassName('has-dependents-but-disabled'); - } - } - markAllDependentsDisabled(pluginTRs[i]); - markHasDisabledDependencies(pluginTRs[i]); - } + } + + pluginTR.addClassName("all-dependents-disabled"); + } + + function markHasDisabledDependencies(pluginTR) { + var jenkinsPluginMetadata = pluginTR.jenkinsPluginMetadata; + var dependencyIds = jenkinsPluginMetadata.dependencyIds; + + if (dependencyIds) { + for (var i = 0; i < dependencyIds.length; i++) { + var dependencyPluginTr = getPluginTR(dependencyIds[i]); + if ( + dependencyPluginTr && + !dependencyPluginTr.jenkinsPluginMetadata.enableInput.checked + ) { + // One of the plugins that this plugin depend on, is marked as disabled. + pluginTR.addClassName("has-disabled-dependency"); + return; + } } - - function addDependencyInfoRow(pluginTR, infoTR) { - infoTR.addClassName('plugin-dependency-info'); - pluginTR.insert({ - after: infoTR - }); + } + + pluginTR.removeClassName("has-disabled-dependency"); + } + + function setEnableWidgetStates() { + for (var i = 0; i < pluginTRs.length; i++) { + var pluginMetadata = pluginTRs[i].jenkinsPluginMetadata; + if (pluginTRs[i].hasClassName("has-dependents-but-disabled")) { + if (pluginMetadata.enableInput.checked) { + pluginTRs[i].removeClassName("has-dependents-but-disabled"); + } } - function removeDependencyInfoRow(pluginTR) { - var nextRows = pluginTR.nextSiblings(); - if (nextRows && nextRows.length > 0) { - var nextRow = nextRows[0]; - if (nextRow.hasClassName('plugin-dependency-info')) { - nextRow.remove(); - } - } + markAllDependentsDisabled(pluginTRs[i]); + markHasDisabledDependencies(pluginTRs[i]); + } + } + + function addDependencyInfoRow(pluginTR, infoTR) { + infoTR.addClassName("plugin-dependency-info"); + pluginTR.insert({ + after: infoTR, + }); + } + function removeDependencyInfoRow(pluginTR) { + var nextRows = pluginTR.nextSiblings(); + if (nextRows && nextRows.length > 0) { + var nextRow = nextRows[0]; + if (nextRow.hasClassName("plugin-dependency-info")) { + nextRow.remove(); } + } + } - function populateEnableDisableInfo(pluginTR, infoContainer) { - var pluginMetadata = pluginTR.jenkinsPluginMetadata; - - // Remove all existing class info - infoContainer.removeAttribute('class'); - infoContainer.addClassName('enable-state-info'); - - if (pluginTR.hasClassName('has-disabled-dependency')) { - var dependenciesDiv = pluginMetadata.dependenciesDiv; - var dependencySpans = pluginMetadata.dependencies; - - infoContainer.update('
' + i18n('cannot-enable') + '
' + i18n('disabled-dependencies') + '.
'); - - // Go through each dependency element. Show the spans where the dependency is - // disabled. Hide the others. - for (var i = 0; i < dependencySpans.length; i++) { - var dependencySpan = dependencySpans[i]; - var pluginId = dependencySpan.getAttribute('data-plugin-id'); - var depPluginTR = getPluginTR(pluginId); - var enabled = false; - if (depPluginTR) { - var depPluginMetadata = depPluginTR.jenkinsPluginMetadata; - enabled = depPluginMetadata.enableInput.checked; - } - if (enabled) { - // It's enabled ... hide the span - dependencySpan.setStyle({display: 'none'}); - } else { - // It's disabled ... show the span - dependencySpan.setStyle({display: 'inline-block'}); - } - } - - dependenciesDiv.setStyle({display: 'inherit'}); - infoContainer.appendChild(dependenciesDiv); - - return true; - } if (pluginTR.hasClassName('has-dependents')) { - if (!pluginTR.hasClassName('all-dependents-disabled')) { - var dependentIds = pluginMetadata.dependentIds; - - // If the only dependent is jenkins-core (it's a bundle plugin), then lets - // treat it like all its dependents are disabled. We're really only interested in - // dependent plugins in this case. - // Note: This does not cover "implied" dependencies ala detached plugins. See https://goo.gl/lQHrUh - if (dependentIds.length === 1 && dependentIds[0] === 'jenkins-core') { - pluginTR.addClassName('all-dependents-disabled'); - return false; - } - - infoContainer.update('
' + i18n('cannot-disable') + '
' + i18n('enabled-dependents') + '.
'); - infoContainer.appendChild(getDependentsDiv(pluginTR, true)); - return true; - } - } + function populateEnableDisableInfo(pluginTR, infoContainer) { + var pluginMetadata = pluginTR.jenkinsPluginMetadata; + + // Remove all existing class info + infoContainer.removeAttribute("class"); + infoContainer.addClassName("enable-state-info"); + + if (pluginTR.hasClassName("has-disabled-dependency")) { + var dependenciesDiv = pluginMetadata.dependenciesDiv; + var dependencySpans = pluginMetadata.dependencies; + + infoContainer.update( + '
' + + i18n("cannot-enable") + + '
' + + i18n("disabled-dependencies") + + ".
" + ); + + // Go through each dependency element. Show the spans where the dependency is + // disabled. Hide the others. + for (var i = 0; i < dependencySpans.length; i++) { + var dependencySpan = dependencySpans[i]; + var pluginId = dependencySpan.getAttribute("data-plugin-id"); + var depPluginTR = getPluginTR(pluginId); + var enabled = false; + if (depPluginTR) { + var depPluginMetadata = depPluginTR.jenkinsPluginMetadata; + enabled = depPluginMetadata.enableInput.checked; + } + if (enabled) { + // It's enabled ... hide the span + dependencySpan.setStyle({ display: "none" }); + } else { + // It's disabled ... show the span + dependencySpan.setStyle({ display: "inline-block" }); + } + } - if (pluginTR.hasClassName('possibly-has-implied-dependents')) { - infoContainer.update('
' + i18n('detached-disable') + '
' + i18n('detached-possible-dependents') + '
'); - infoContainer.appendChild(getDependentsDiv(pluginTR, true)); - return true; - } - + dependenciesDiv.setStyle({ display: "inherit" }); + infoContainer.appendChild(dependenciesDiv); + + return true; + } + if (pluginTR.hasClassName("has-dependents")) { + if (!pluginTR.hasClassName("all-dependents-disabled")) { + var dependentIds = pluginMetadata.dependentIds; + + // If the only dependent is jenkins-core (it's a bundle plugin), then lets + // treat it like all its dependents are disabled. We're really only interested in + // dependent plugins in this case. + // Note: This does not cover "implied" dependencies ala detached plugins. See https://goo.gl/lQHrUh + if (dependentIds.length === 1 && dependentIds[0] === "jenkins-core") { + pluginTR.addClassName("all-dependents-disabled"); return false; + } + + infoContainer.update( + '
' + + i18n("cannot-disable") + + '
' + + i18n("enabled-dependents") + + ".
" + ); + infoContainer.appendChild(getDependentsDiv(pluginTR, true)); + return true; } + } + + if (pluginTR.hasClassName("possibly-has-implied-dependents")) { + infoContainer.update( + '
' + + i18n("detached-disable") + + '
' + + i18n("detached-possible-dependents") + + "
" + ); + infoContainer.appendChild(getDependentsDiv(pluginTR, true)); + return true; + } + + return false; + } - function populateUninstallInfo(pluginTR, infoContainer) { - // Remove all existing class info - infoContainer.removeAttribute('class'); - infoContainer.addClassName('uninstall-state-info'); + function populateUninstallInfo(pluginTR, infoContainer) { + // Remove all existing class info + infoContainer.removeAttribute("class"); + infoContainer.addClassName("uninstall-state-info"); + + if (pluginTR.hasClassName("has-dependents")) { + infoContainer.update( + '
' + + i18n("cannot-uninstall") + + '
' + + i18n("installed-dependents") + + ".
" + ); + infoContainer.appendChild(getDependentsDiv(pluginTR, false)); + return true; + } + + if (pluginTR.hasClassName("possibly-has-implied-dependents")) { + infoContainer.update( + '
' + + i18n("detached-uninstall") + + '
' + + i18n("detached-possible-dependents") + + "
" + ); + infoContainer.appendChild(getDependentsDiv(pluginTR, false)); + return true; + } + + return false; + } - if (pluginTR.hasClassName('has-dependents')) { - infoContainer.update('
' + i18n('cannot-uninstall') + '
' + i18n('installed-dependents') + '.
'); - infoContainer.appendChild(getDependentsDiv(pluginTR, false)); - return true; - } + function getDependentsDiv(pluginTR, hideDisabled) { + var pluginMetadata = pluginTR.jenkinsPluginMetadata; + var dependentsDiv = pluginMetadata.dependentsDiv; + var dependentSpans = pluginMetadata.dependents; - if (pluginTR.hasClassName('possibly-has-implied-dependents')) { - infoContainer.update('
' + i18n('detached-uninstall') + '
' + i18n('detached-possible-dependents') + '
'); - infoContainer.appendChild(getDependentsDiv(pluginTR, false)); - return true; - } + // Go through each dependent element. If disabled should be hidden, show the spans where + // the dependent is enabled and hide the others. Otherwise show them all. + for (var i = 0; i < dependentSpans.length; i++) { + var dependentSpan = dependentSpans[i]; + var dependentId = dependentSpan.getAttribute("data-plugin-id"); - return false; + if (!hideDisabled || dependentId === "jenkins-core") { + dependentSpan.setStyle({ display: "inline-block" }); + } else { + var depPluginTR = getPluginTR(dependentId); + var depPluginMetadata = depPluginTR.jenkinsPluginMetadata; + if (depPluginMetadata.enableInput.checked) { + // It's enabled ... show the span + dependentSpan.setStyle({ display: "inline-block" }); + } else { + // It's disabled ... hide the span + dependentSpan.setStyle({ display: "none" }); + } } + } - function getDependentsDiv(pluginTR, hideDisabled) { - var pluginMetadata = pluginTR.jenkinsPluginMetadata; - var dependentsDiv = pluginMetadata.dependentsDiv; - var dependentSpans = pluginMetadata.dependents; - - // Go through each dependent element. If disabled should be hidden, show the spans where - // the dependent is enabled and hide the others. Otherwise show them all. - for (var i = 0; i < dependentSpans.length; i++) { - var dependentSpan = dependentSpans[i]; - var dependentId = dependentSpan.getAttribute('data-plugin-id'); - - if (!hideDisabled || dependentId === 'jenkins-core') { - dependentSpan.setStyle({display: 'inline-block'}); - } else { - var depPluginTR = getPluginTR(dependentId); - var depPluginMetadata = depPluginTR.jenkinsPluginMetadata; - if (depPluginMetadata.enableInput.checked) { - // It's enabled ... show the span - dependentSpan.setStyle({display: 'inline-block'}); - } else { - // It's disabled ... hide the span - dependentSpan.setStyle({display: 'none'}); - } - } - } + dependentsDiv.setStyle({ display: "inherit" }); + return dependentsDiv; + } - dependentsDiv.setStyle({display: 'inherit'}); - return dependentsDiv; + function initPluginRowHandling(pluginTR) { + var enableInput = select(".enable input", pluginTR); + var dependenciesDiv = select(".dependency-list", pluginTR); + var dependentsDiv = select(".dependent-list", pluginTR); + var enableTD = select("td.enable", pluginTR); + var uninstallTD = select("td.uninstall", pluginTR); + + pluginTR.jenkinsPluginMetadata = { + enableInput: enableInput, + dependenciesDiv: dependenciesDiv, + dependentsDiv: dependentsDiv, + }; + + if (dependenciesDiv) { + pluginTR.jenkinsPluginMetadata.dependencies = selectAll( + "span", + dependenciesDiv + ); + pluginTR.jenkinsPluginMetadata.dependencyIds = processSpanSet( + pluginTR.jenkinsPluginMetadata.dependencies + ); + } + if (dependentsDiv) { + pluginTR.jenkinsPluginMetadata.dependents = selectAll( + "span", + dependentsDiv + ); + pluginTR.jenkinsPluginMetadata.dependentIds = processSpanSet( + pluginTR.jenkinsPluginMetadata.dependents + ); + } + + // Setup event handlers... + if (enableInput) { + // Toggling of the enable/disable checkbox requires a check and possible + // change of visibility on the same checkbox on other plugins. + Element.observe(enableInput, "click", function () { + setEnableWidgetStates(); + }); + } + + // + var infoTR = document.createElement("tr"); + var infoTD = document.createElement("td"); + var infoDiv = document.createElement("div"); + infoTR.appendChild(infoTD); + infoTD.appendChild(infoDiv); + infoTD.setAttribute("colspan", "6"); // This is the cell that all info will be added to. + infoDiv.setStyle({ display: "inherit" }); + + // We don't want the info row to appear immediately. We wait for e.g. 1 second and if the mouse + // is still in there (hasn't left the cell) then we show. The following code is for clearing the + // show timeout where the mouse has left before the timeout has fired. + var showInfoTimeout = undefined; + function clearShowInfoTimeout() { + if (showInfoTimeout) { + clearTimeout(showInfoTimeout); } - - function initPluginRowHandling(pluginTR) { - var enableInput = select('.enable input', pluginTR); - var dependenciesDiv = select('.dependency-list', pluginTR); - var dependentsDiv = select('.dependent-list', pluginTR); - var enableTD = select('td.enable', pluginTR); - var uninstallTD = select('td.uninstall', pluginTR); - - pluginTR.jenkinsPluginMetadata = { - enableInput: enableInput, - dependenciesDiv: dependenciesDiv, - dependentsDiv: dependentsDiv - }; - - if (dependenciesDiv) { - pluginTR.jenkinsPluginMetadata.dependencies = selectAll('span', dependenciesDiv); - pluginTR.jenkinsPluginMetadata.dependencyIds = processSpanSet(pluginTR.jenkinsPluginMetadata.dependencies); - } - if (dependentsDiv) { - pluginTR.jenkinsPluginMetadata.dependents = selectAll('span', dependentsDiv); - pluginTR.jenkinsPluginMetadata.dependentIds = processSpanSet(pluginTR.jenkinsPluginMetadata.dependents); + showInfoTimeout = undefined; + } + + // Handle mouse in/out of the enable/disable cell (left most cell). + if (enableTD) { + Element.observe(enableTD, "mouseenter", function () { + showInfoTimeout = setTimeout(function () { + showInfoTimeout = undefined; + infoDiv.update(""); + if (populateEnableDisableInfo(pluginTR, infoDiv)) { + addDependencyInfoRow(pluginTR, infoTR); } - - // Setup event handlers... - if (enableInput) { - // Toggling of the enable/disable checkbox requires a check and possible - // change of visibility on the same checkbox on other plugins. - Element.observe(enableInput, 'click', function() { - setEnableWidgetStates(); - }); - } - - // - var infoTR = document.createElement("tr"); - var infoTD = document.createElement("td"); - var infoDiv = document.createElement("div"); - infoTR.appendChild(infoTD) - infoTD.appendChild(infoDiv) - infoTD.setAttribute('colspan', '6'); // This is the cell that all info will be added to. - infoDiv.setStyle({display: 'inherit'}); - - // We don't want the info row to appear immediately. We wait for e.g. 1 second and if the mouse - // is still in there (hasn't left the cell) then we show. The following code is for clearing the - // show timeout where the mouse has left before the timeout has fired. - var showInfoTimeout = undefined; - function clearShowInfoTimeout() { - if (showInfoTimeout) { - clearTimeout(showInfoTimeout); - } - showInfoTimeout = undefined; - } - - // Handle mouse in/out of the enable/disable cell (left most cell). - if (enableTD) { - Element.observe(enableTD, 'mouseenter', function() { - showInfoTimeout = setTimeout(function() { - showInfoTimeout = undefined; - infoDiv.update(''); - if (populateEnableDisableInfo(pluginTR, infoDiv)) { - addDependencyInfoRow(pluginTR, infoTR); - } - }, 1000); - }); - Element.observe(enableTD, 'mouseleave', function() { - clearShowInfoTimeout(); - removeDependencyInfoRow(pluginTR); - }); + }, 1000); + }); + Element.observe(enableTD, "mouseleave", function () { + clearShowInfoTimeout(); + removeDependencyInfoRow(pluginTR); + }); + } + + // Handle mouse in/out of the uninstall cell (right most cell). + if (uninstallTD) { + Element.observe(uninstallTD, "mouseenter", function () { + showInfoTimeout = setTimeout(function () { + showInfoTimeout = undefined; + infoDiv.update(""); + if (populateUninstallInfo(pluginTR, infoDiv)) { + addDependencyInfoRow(pluginTR, infoTR); } + }, 1000); + }); + Element.observe(uninstallTD, "mouseleave", function () { + clearShowInfoTimeout(); + removeDependencyInfoRow(pluginTR); + }); + } + } - // Handle mouse in/out of the uninstall cell (right most cell). - if (uninstallTD) { - Element.observe(uninstallTD, 'mouseenter', function() { - showInfoTimeout = setTimeout(function() { - showInfoTimeout = undefined; - infoDiv.update(''); - if (populateUninstallInfo(pluginTR, infoDiv)) { - addDependencyInfoRow(pluginTR, infoTR); - } - }, 1000); - }); - Element.observe(uninstallTD, 'mouseleave', function() { - clearShowInfoTimeout(); - removeDependencyInfoRow(pluginTR); - }); - } - } + for (var i = 0; i < pluginTRs.length; i++) { + initPluginRowHandling(pluginTRs[i]); + } - for (var i = 0; i < pluginTRs.length; i++) { - initPluginRowHandling(pluginTRs[i]); - } - - setEnableWidgetStates(); - }); -}()); + setEnableWidgetStates(); + }); +})(); -Element.observe(window, "load", function() { - document.getElementById('filter-box').focus(); -}); \ No newline at end of file +Element.observe(window, "load", function () { + document.getElementById("filter-box").focus(); +}); diff --git a/core/src/main/resources/hudson/ProxyConfiguration/help-name.html b/core/src/main/resources/hudson/ProxyConfiguration/help-name.html index 04d3520563..eaba21d754 100644 --- a/core/src/main/resources/hudson/ProxyConfiguration/help-name.html +++ b/core/src/main/resources/hudson/ProxyConfiguration/help-name.html @@ -1,14 +1,22 @@
- If your Jenkins server sits behind a firewall and does not have the direct access to the internet, - and if your server JVM is not configured appropriately - (See JDK networking properties for more details) - to enable internet connection, you can specify the HTTP proxy server name in this field to allow Jenkins - to install plugins on behalf of you. Note that Jenkins uses HTTPS to communicate with the update center to download plugins. + If your Jenkins server sits behind a firewall and does not have the direct + access to the internet, and if your server JVM is not configured appropriately + ( + + See JDK networking properties for more details + + ) to enable internet connection, you can specify the HTTP proxy server name in + this field to allow Jenkins to install plugins on behalf of you. Note that + Jenkins uses HTTPS to communicate with the update center to download plugins.

- Leaving this field empty - means Jenkins will try to connect to the internet directly. + Leaving this field empty means Jenkins will try to connect to the internet + directly. +

- If you are unsure about the value, check the browser proxy configuration. -

\ No newline at end of file + If you are unsure about the value, check the browser proxy configuration. +

+ diff --git a/core/src/main/resources/hudson/ProxyConfiguration/help-name_bg.html b/core/src/main/resources/hudson/ProxyConfiguration/help-name_bg.html index 47bade33d9..1151b9509f 100644 --- a/core/src/main/resources/hudson/ProxyConfiguration/help-name_bg.html +++ b/core/src/main/resources/hudson/ProxyConfiguration/help-name_bg.html @@ -1,13 +1,17 @@
- Ако вашият Jenkins е зад защитна стена и няма пряка връзка към Интернет, а JVM на сървъра не е - настроена правилно, за да се позволи връзка с Интернет, може да укажете име на сървър-посредник - за HTTP, за да позволите на Jenkins самостоятелно да инсталира приставки. (за повече детайли: - Networking Properties) - Jenkins използва HTTPS, за да се свърже със сървъра за обновяване и изтегли приставките. + Ако вашият Jenkins е зад защитна стена и няма пряка връзка към Интернет, а JVM + на сървъра не е настроена правилно, за да се позволи връзка с Интернет, може + да укажете име на сървър-посредник за HTTP, за да позволите на Jenkins + самостоятелно да инсталира приставки. (за повече детайли: + + Networking Properties + + ) Jenkins използва HTTPS, за да се свърже със сървъра за обновяване и изтегли + приставките. -

- Ако полето е празно, Jenkins ще се свързва директно с Интернет. +

Ако полето е празно, Jenkins ще се свързва директно с Интернет.

-

- Ако не сте сигурни, вижте какви са настройките на браузъра ви. +

Ако не сте сигурни, вижте какви са настройките на браузъра ви.

diff --git a/core/src/main/resources/hudson/ProxyConfiguration/help-name_de.html b/core/src/main/resources/hudson/ProxyConfiguration/help-name_de.html index daa21ce4af..b966e3cc95 100644 --- a/core/src/main/resources/hudson/ProxyConfiguration/help-name_de.html +++ b/core/src/main/resources/hudson/ProxyConfiguration/help-name_de.html @@ -1,17 +1,24 @@
- Befindet sich Ihr Jenkins-Server hinter einer Firewall, hat keinen direkten Zugang - zum Internet und ist Ihre Server-JVM nicht hinreichend konfiguriert, um eine Internetverbindung herzustellen - (mehr über die JDK-Netzwerk-Einstellungen), - dann können Sie in diesem Feld den Namen eines HTTP-Proxy-Servers angeben. - Sie erlauben dadurch Jenkins, in Ihrem Namen Plugins herunterzuladen und zu installieren. - - Beachten Sie, dass Jenkins HTTPS verwendet, um mit dem Update-Center zu kommunizieren - und Plugins herunterzuladen. + Befindet sich Ihr Jenkins-Server hinter einer Firewall, hat keinen direkten + Zugang zum Internet und ist Ihre Server-JVM nicht hinreichend konfiguriert, um + eine Internetverbindung herzustellen ( + + mehr über die JDK-Netzwerk-Einstellungen + + ), dann können Sie in diesem Feld den Namen eines HTTP-Proxy-Servers angeben. + Sie erlauben dadurch Jenkins, in Ihrem Namen Plugins herunterzuladen und zu + installieren. Beachten Sie, dass Jenkins HTTPS verwendet, um mit dem + Update-Center zu kommunizieren und Plugins herunterzuladen.

- Wenn Sie dieses Feld freilassen, versucht Jenkins, das Update-Center direkt zu kontaktieren. + Wenn Sie dieses Feld freilassen, versucht Jenkins, das Update-Center direkt + zu kontaktieren. +

- Wenn Sie sich nicht sicher sind, was Sie hier eintragen sollen, schauen Sie - in der Proxy-Konfiguration Ihres Browsers nach. + Wenn Sie sich nicht sicher sind, was Sie hier eintragen sollen, schauen Sie + in der Proxy-Konfiguration Ihres Browsers nach. +

diff --git a/core/src/main/resources/hudson/ProxyConfiguration/help-name_fr.html b/core/src/main/resources/hudson/ProxyConfiguration/help-name_fr.html index f5a50345b5..b3d676d6cc 100644 --- a/core/src/main/resources/hudson/ProxyConfiguration/help-name_fr.html +++ b/core/src/main/resources/hudson/ProxyConfiguration/help-name_fr.html @@ -1,15 +1,22 @@
- Si votre serveur Jenkins se trouve derrière un firewall, qu'il n'a pas d'accès direct à internet et - que la JVM de votre serveur n'est pas configurée de façon à permettre l'accès à internet (voir - les propriétés réseau du JDK pour plus d'informations), - vous pouvez spécifier le nom d'un serveur proxy HTTP pour permettre à Jenkins - d'installer des plugins pour vous. - Notez que Jenkins utilise HTTPS pour communiquer avec le serveur de mise à jour pour télécharger les plugins. + Si votre serveur Jenkins se trouve derrière un firewall, qu'il n'a pas d'accès + direct à internet et que la JVM de votre serveur n'est pas configurée de façon + à permettre l'accès à internet (voir + + les propriétés réseau du JDK pour plus d'informations + + ), vous pouvez spécifier le nom d'un serveur proxy HTTP pour permettre à + Jenkins d'installer des plugins pour vous. Notez que Jenkins utilise HTTPS + pour communiquer avec le serveur de mise à jour pour télécharger les plugins.

- Si ce champ est vide Jenkins tentera de se - connecter directement au site. + Si ce champ est vide Jenkins tentera de se connecter directement au site. +

- Si vous ne savez pas quelle valeur indiquer, regardez la configuration proxy de votre navigateur web. -

\ No newline at end of file + Si vous ne savez pas quelle valeur indiquer, regardez la configuration proxy + de votre navigateur web. +

+ diff --git a/core/src/main/resources/hudson/ProxyConfiguration/help-name_it.html b/core/src/main/resources/hudson/ProxyConfiguration/help-name_it.html index ee60884a61..056736163e 100644 --- a/core/src/main/resources/hudson/ProxyConfiguration/help-name_it.html +++ b/core/src/main/resources/hudson/ProxyConfiguration/help-name_it.html @@ -1,19 +1,24 @@
Se il server Jenkins è protetto da un firewall e non dispone di accesso diretto a Internet, e se la JVM del server non è configurata in modo - appropriato per consentire la connessione a Internet - ( - si vedano le proprietà di rete del JDK per ulteriori dettagli), è - possibile specificare in questo campo il nome del server proxy HTTP per - consentire a Jenkins di installare componenti aggiuntivi per proprio conto. - Si noti che Jenkins utilizza HTTPS per comunicare con il Centro aggiornamenti - per scaricare i componenti aggiuntivi. + appropriato per consentire la connessione a Internet ( + + si vedano le proprietà di rete del JDK per ulteriori dettagli + + ), è possibile specificare in questo campo il nome del server proxy HTTP per + consentire a Jenkins di installare componenti aggiuntivi per proprio conto. Si + noti che Jenkins utilizza HTTPS per comunicare con il Centro aggiornamenti per + scaricare i componenti aggiuntivi.

- Se si lascia questo campo vuoto, Jenkins proverà a collegarsi a Internet - direttamente. + Se si lascia questo campo vuoto, Jenkins proverà a collegarsi a Internet + direttamente. +

- Se non si è sicuri del valore da immettere, verificare la configurazione - proxy del browser. + Se non si è sicuri del valore da immettere, verificare la configurazione + proxy del browser. +

diff --git a/core/src/main/resources/hudson/ProxyConfiguration/help-name_ja.html b/core/src/main/resources/hudson/ProxyConfiguration/help-name_ja.html index 6662880128..21864ed73c 100644 --- a/core/src/main/resources/hudson/ProxyConfiguration/help-name_ja.html +++ b/core/src/main/resources/hudson/ProxyConfiguration/help-name_ja.html @@ -1,14 +1,25 @@
Jenkinsサーバーがファイアーウォールの内側にあってインターネットに直接アクセスできない上に、 - サーバーのJVMがインターネットと接続できるように適切(詳細はネットワークのプロパティを参照)に設定されていない場合、 + サーバーのJVMがインターネットと接続できるように適切( + + 詳細はネットワークのプロパティを参照 + + )に設定されていない場合、 この項目にプロキシーの名前を設定するとプラグインをインストールできます。

- Jenkinsは、アップデートセンターとHTTPSで接続してプラグインをダウンロードすることに注意してください。 + Jenkinsは、アップデートセンターとHTTPSで接続してプラグインをダウンロードすることに注意してください。 +

- ここに設定した値は、システムプロパティhttp.proxyHostに設定されます。空白にするとシステムプロパティを未設定にし、 - Jenkinsは直接接続します。 + ここに設定した値は、システムプロパティ + http.proxyHost + に設定されます。空白にするとシステムプロパティを未設定にし、 + Jenkinsは直接接続します。 +

- 何を設定していいか分からない場合は、ブラウザのプロキシーの設定を確認してください。 + 何を設定していいか分からない場合は、ブラウザのプロキシーの設定を確認してください。 +

diff --git a/core/src/main/resources/hudson/ProxyConfiguration/help-name_nl.html b/core/src/main/resources/hudson/ProxyConfiguration/help-name_nl.html index 22adaed5be..6b760d565e 100644 --- a/core/src/main/resources/hudson/ProxyConfiguration/help-name_nl.html +++ b/core/src/main/resources/hudson/ProxyConfiguration/help-name_nl.html @@ -1,16 +1,26 @@
- Indien Uw Jenkins server zich achter een firewall bevindt en geen directe toegang tot het internet heeft, - dan kunt U hier een HTTP-proxyservernaam opgeven via dewelke Jenkins dan voor U plugins kan installeren. - Merk op dat uw JVM hiertoe ook correct geconfigureerd dient te zijn ( - Zie "JDK networking properties" voor meer details). - Jenkins zal het opwaarderingscentrum via HTTPS contacteren voor het verkrijgen van de benodigde opwaarderingspakketten. - + Indien Uw Jenkins server zich achter een firewall bevindt en geen directe + toegang tot het internet heeft, dan kunt U hier een HTTP-proxyservernaam + opgeven via dewelke Jenkins dan voor U plugins kan installeren. Merk op dat uw + JVM hiertoe ook correct geconfigureerd dient te zijn ( + + Zie "JDK networking properties" voor meer details + + ). Jenkins zal het opwaarderingscentrum via HTTPS contacteren voor het + verkrijgen van de benodigde opwaarderingspakketten. +

- De waarde die U hier opgeeft zal als systeemparameter http.proxyHost gezet worden. Indien U dit - veld leeg laat, zal de systeemparameter niet gezet worden, waardoor Jenkins de server rechtstreeks zal proberen - te contacteren. - + De waarde die U hier opgeeft zal als systeemparameter + http.proxyHost + gezet worden. Indien U dit veld leeg laat, zal de systeemparameter niet + gezet worden, waardoor Jenkins de server rechtstreeks zal proberen te + contacteren. +

+

- Indien U niet zeker ben welke waarde U hier dient in te vullen, kunt U best de proxy configuratie van uw - browser bekijken. + Indien U niet zeker ben welke waarde U hier dient in te vullen, kunt U best + de proxy configuratie van uw browser bekijken. +

diff --git a/core/src/main/resources/hudson/ProxyConfiguration/help-name_pl.html b/core/src/main/resources/hudson/ProxyConfiguration/help-name_pl.html index 294af7f915..43fcdff072 100644 --- a/core/src/main/resources/hudson/ProxyConfiguration/help-name_pl.html +++ b/core/src/main/resources/hudson/ProxyConfiguration/help-name_pl.html @@ -1,13 +1,22 @@
- Jeśli Jenkins znajduje się za zaporą sieciową i nie ma bezpośredniego dostępu do Internetu, - a JVM nie jest skonfigurowana odpowiednio - (sprawdź ustawienia sieciowe), - możesz udostępnić Internet ustawiając serwer proxy, aby Jenkins samodzielnie pobrał i zainstalował wtyczki. - Pamiętaj, że Jenkins używa połączenia https, aby pobrać wtyczki z centrum aktualizacji. + Jeśli Jenkins znajduje się za zaporą sieciową i nie ma bezpośredniego dostępu + do Internetu, a JVM nie jest skonfigurowana odpowiednio ( + + sprawdź ustawienia sieciowe + + ), możesz udostępnić Internet ustawiając serwer proxy, aby Jenkins + samodzielnie pobrał i zainstalował wtyczki. Pamiętaj, że Jenkins używa + połączenia https, aby pobrać wtyczki z centrum aktualizacji.

- Pozostaw to pole puste, aby Jenkins korzystał z bezpośredniego połączenia z Internetem. + Pozostaw to pole puste, aby Jenkins korzystał z bezpośredniego połączenia z + Internetem. +

- Jeśli nie jesteś pewny ustawień, sprawdź ustawienia serwerów proxy w przeglądarce. -

\ No newline at end of file + Jeśli nie jesteś pewny ustawień, sprawdź ustawienia serwerów proxy w + przeglądarce. +

+ diff --git a/core/src/main/resources/hudson/ProxyConfiguration/help-name_pt_BR.html b/core/src/main/resources/hudson/ProxyConfiguration/help-name_pt_BR.html index 32f6041bca..5fab2e28bc 100644 --- a/core/src/main/resources/hudson/ProxyConfiguration/help-name_pt_BR.html +++ b/core/src/main/resources/hudson/ProxyConfiguration/help-name_pt_BR.html @@ -1,14 +1,24 @@
- Se seu servidor Jenkins estiver atrás de um firewall e não tem acesso direto a internet, - e se a JVM do seu servidor não estiver configurada apropriadamente - (Veja as propriedades de redes do JDK para mais detalhes) - para habilitar a conexão de internet, você pode especificar o nome do servidor de proxy HTTP neste campos para permitir ao Jenkins - instalar plugins para você. Note que o Jenkins usa HTTPS para se comunicar com o centro de atualização para baixar os plugins. + Se seu servidor Jenkins estiver atrás de um firewall e não tem + acesso direto a internet, e se a JVM do seu servidor não estiver + configurada apropriadamente ( + + Veja as propriedades de redes do JDK para mais detalhes + + ) para habilitar a conexão de internet, você pode especificar o nome + do servidor de proxy HTTP neste campos para permitir ao Jenkins instalar + plugins para você. Note que o Jenkins usa HTTPS para se comunicar com o + centro de atualização para baixar os plugins.

- Deixar este campo vazio - faz com que o Jenkins tente conectar à internet diretamente. + Deixar este campo vazio faz com que o Jenkins tente conectar à internet + diretamente. +

- Se você não está certo sobre o valor, cheque a configuração de proxy de seu browser. + Se você não está certo sobre o valor, cheque a + configuração de proxy de seu browser. +

diff --git a/core/src/main/resources/hudson/ProxyConfiguration/help-name_zh_TW.html b/core/src/main/resources/hudson/ProxyConfiguration/help-name_zh_TW.html index 39f70ef283..79d895e2f4 100644 --- a/core/src/main/resources/hudson/ProxyConfiguration/help-name_zh_TW.html +++ b/core/src/main/resources/hudson/ProxyConfiguration/help-name_zh_TW.html @@ -1,13 +1,19 @@
- 如果您的 Jenkins 在防火牆後面、不能直接連到 Internet，而且伺服器 JVM 也沒有特別設定 - (參考 JDK 的 《Networking Properties》了解詳情)。 - 可以在這裡指定 HTTP 代理伺服器名稱，讓 Jenkins 能幫您安裝外掛程式。 + 如果您的 Jenkins 在防火牆後面、不能直接連到 Internet，而且伺服器 JVM + 也沒有特別設定 ( + + 參考 JDK 的 《Networking Properties》了解詳情 + + )。 可以在這裡指定 HTTP 代理伺服器名稱，讓 Jenkins 能幫您安裝外掛程式。 請注意，Jenkins 使用 HTTPS 協定由更新中心下載外掛程式。

- 您在這裡送出的值會被設為 http.proxyHost 系統屬性。 - 不填任何值代表不要設定這項屬性，Jenkins 會試著直接連線到主機。 + 您在這裡送出的值會被設為 + http.proxyHost + 系統屬性。 不填任何值代表不要設定這項屬性，Jenkins 會試著直接連線到主機。 +

-

- 如果您不確定該怎麼填，可以參考瀏覽器的代理伺服器設定。 -

\ No newline at end of file +

如果您不確定該怎麼填，可以參考瀏覽器的代理伺服器設定。

+ diff --git a/core/src/main/resources/hudson/ProxyConfiguration/help-noProxyHost.html b/core/src/main/resources/hudson/ProxyConfiguration/help-noProxyHost.html index 91f8dbd8c1..805f601109 100644 --- a/core/src/main/resources/hudson/ProxyConfiguration/help-noProxyHost.html +++ b/core/src/main/resources/hudson/ProxyConfiguration/help-noProxyHost.html @@ -1,4 +1,5 @@
- Specify host name patterns that shouldn't go through the proxy, one host per line. - "*" is the wild card host name (such as "*.jenkins.io" or "www*.jenkins-ci.org") -
\ No newline at end of file + Specify host name patterns that shouldn't go through the proxy, one host per + line. "*" is the wild card host name (such as "*.jenkins.io" or + "www*.jenkins-ci.org") + diff --git a/core/src/main/resources/hudson/ProxyConfiguration/help-noProxyHost_bg.html b/core/src/main/resources/hudson/ProxyConfiguration/help-noProxyHost_bg.html index 03eeaa12cb..7a64ff7c78 100644 --- a/core/src/main/resources/hudson/ProxyConfiguration/help-noProxyHost_bg.html +++ b/core/src/main/resources/hudson/ProxyConfiguration/help-noProxyHost_bg.html @@ -1,4 +1,5 @@
- Шаблони за имената на сървърите, към които да се свързва директно, а не през сървъра-посредник. - По един шаблон на ред. „*“ напасва всички имена (напр. „*.cloudbees.com“ или „w*.jenkins.io“) + Шаблони за имената на сървърите, към които да се свързва директно, а не през + сървъра-посредник. По един шаблон на ред. „*“ напасва всички имена (напр. + „*.cloudbees.com“ или „w*.jenkins.io“)
diff --git a/core/src/main/resources/hudson/ProxyConfiguration/help-noProxyHost_de.html b/core/src/main/resources/hudson/ProxyConfiguration/help-noProxyHost_de.html index 7305964880..365f282c32 100644 --- a/core/src/main/resources/hudson/ProxyConfiguration/help-noProxyHost_de.html +++ b/core/src/main/resources/hudson/ProxyConfiguration/help-noProxyHost_de.html @@ -1,6 +1,6 @@
- Geben Sie Servernamen-Muster an, die nicht über den Proxy abgerufen werden sollen. - Geben Sie einen Eintrag pro Zeile ein. - Verwenden Sie gegebenenfalls das Jokerzeichen "*", um Gruppen von Servern anzugeben - (wie in "*.jenkins.io" or "www*.jenkins-ci.org") + Geben Sie Servernamen-Muster an, die nicht über den Proxy abgerufen werden + sollen. Geben Sie einen Eintrag pro Zeile ein. Verwenden Sie gegebenenfalls + das Jokerzeichen "*", um Gruppen von Servern anzugeben (wie in "*.jenkins.io" + or "www*.jenkins-ci.org")
diff --git a/core/src/main/resources/hudson/ProxyConfiguration/help-noProxyHost_it.html b/core/src/main/resources/hudson/ProxyConfiguration/help-noProxyHost_it.html index 90ce442251..20acf82750 100644 --- a/core/src/main/resources/hudson/ProxyConfiguration/help-noProxyHost_it.html +++ b/core/src/main/resources/hudson/ProxyConfiguration/help-noProxyHost_it.html @@ -1,5 +1,5 @@
- Specificare i pattern dei nomi host per cui le richieste non devono essere - gestite dal proxy; immettere un host per riga. "*" è il carattere jolly per - i nomi host (ad es. "*.jenkins.io" o "www*.jenkins-ci.org"). + Specificare i pattern dei nomi host per cui le richieste non devono essere + gestite dal proxy; immettere un host per riga. "*" è il carattere jolly per i + nomi host (ad es. "*.jenkins.io" o "www*.jenkins-ci.org").
diff --git a/core/src/main/resources/hudson/ProxyConfiguration/help-noProxyHost_ja.html b/core/src/main/resources/hudson/ProxyConfiguration/help-noProxyHost_ja.html index c349cc67b5..ee6b49ea36 100644 --- a/core/src/main/resources/hudson/ProxyConfiguration/help-noProxyHost_ja.html +++ b/core/src/main/resources/hudson/ProxyConfiguration/help-noProxyHost_ja.html @@ -1,4 +1,4 @@
- プロキシーを使用しないホスト名のパターンを1行に1つずつ設定します。 - ホスト名には"*"(ワイルドカード)を、"*.jenkins.io"や"www*.jenkins-ci.org"のように使用することができます。 -
\ No newline at end of file + プロキシーを使用しないホスト名のパターンを1行に1つずつ設定します。 + ホスト名には"*"(ワイルドカード)を、"*.jenkins.io"や"www*.jenkins-ci.org"のように使用することができます。 + diff --git a/core/src/main/resources/hudson/ProxyConfiguration/help-noProxyHost_zh_TW.html b/core/src/main/resources/hudson/ProxyConfiguration/help-noProxyHost_zh_TW.html index a6df9c10ed..513f77cc36 100644 --- a/core/src/main/resources/hudson/ProxyConfiguration/help-noProxyHost_zh_TW.html +++ b/core/src/main/resources/hudson/ProxyConfiguration/help-noProxyHost_zh_TW.html @@ -1,4 +1,4 @@
- 指定不要透過代理伺服器連線的主機名稱樣式，一行一個。 - 可以使用 "*" 代表任何字串 (例如 "*.jenkins.io" 或是 "www*.jenkins-ci.org")。 -
\ No newline at end of file + 指定不要透過代理伺服器連線的主機名稱樣式，一行一個。 可以使用 "*" 代表任何字串 + (例如 "*.jenkins.io" 或是 "www*.jenkins-ci.org")。 + diff --git a/core/src/main/resources/hudson/ProxyConfiguration/help-port.html b/core/src/main/resources/hudson/ProxyConfiguration/help-port.html index 5c10488e6e..d7782a9e14 100644 --- a/core/src/main/resources/hudson/ProxyConfiguration/help-port.html +++ b/core/src/main/resources/hudson/ProxyConfiguration/help-port.html @@ -1,3 +1,4 @@
- This field works in conjunction with the proxy server field to specify the HTTP proxy port. -
\ No newline at end of file + This field works in conjunction with the proxy server field to specify the + HTTP proxy port. + diff --git a/core/src/main/resources/hudson/ProxyConfiguration/help-port_bg.html b/core/src/main/resources/hudson/ProxyConfiguration/help-port_bg.html index d24f470bda..c2e4d21077 100644 --- a/core/src/main/resources/hudson/ProxyConfiguration/help-port_bg.html +++ b/core/src/main/resources/hudson/ProxyConfiguration/help-port_bg.html @@ -1,3 +1 @@ -
- Това поле определя порта за сървъра-посредник по HTTP. -
+
Това поле определя порта за сървъра-посредник по HTTP.
diff --git a/core/src/main/resources/hudson/ProxyConfiguration/help-port_de.html b/core/src/main/resources/hudson/ProxyConfiguration/help-port_de.html index b7669cdced..d004e900db 100644 --- a/core/src/main/resources/hudson/ProxyConfiguration/help-port_de.html +++ b/core/src/main/resources/hudson/ProxyConfiguration/help-port_de.html @@ -1,4 +1,4 @@
Dieses Feld arbeitet im Zusammenhang mit dem Feld "Proxy-Server" und gibt die - Portnummer des HTTP-Proxies an. -
\ No newline at end of file + Portnummer des HTTP-Proxies an. + diff --git a/core/src/main/resources/hudson/ProxyConfiguration/help-port_fr.html b/core/src/main/resources/hudson/ProxyConfiguration/help-port_fr.html index e8d1dc9158..1636e5b7af 100644 --- a/core/src/main/resources/hudson/ProxyConfiguration/help-port_fr.html +++ b/core/src/main/resources/hudson/ProxyConfiguration/help-port_fr.html @@ -1,3 +1,3 @@
Ce champ est le numéro de port du proxy HTTP, utilisé avec le nom du serveur. -
\ No newline at end of file + diff --git a/core/src/main/resources/hudson/ProxyConfiguration/help-port_it.html b/core/src/main/resources/hudson/ProxyConfiguration/help-port_it.html index a1e3c09751..69dede3ea9 100644 --- a/core/src/main/resources/hudson/ProxyConfiguration/help-port_it.html +++ b/core/src/main/resources/hudson/ProxyConfiguration/help-port_it.html @@ -1,4 +1,4 @@
- Questo campo lavora in abbinamento con il campo Server proxy per consentire - di specificare la porta HTTP del proxy. + Questo campo lavora in abbinamento con il campo Server proxy per consentire di + specificare la porta HTTP del proxy.
diff --git a/core/src/main/resources/hudson/ProxyConfiguration/help-port_ja.html b/core/src/main/resources/hudson/ProxyConfiguration/help-port_ja.html index ad73d6a4a9..8d9e12de62 100644 --- a/core/src/main/resources/hudson/ProxyConfiguration/help-port_ja.html +++ b/core/src/main/resources/hudson/ProxyConfiguration/help-port_ja.html @@ -1,3 +1,4 @@
- この項目にはプロキシーのポート番号を指定すると、"HTTP proxy server"とあわせて機能します。 -
\ No newline at end of file + この項目にはプロキシーのポート番号を指定すると、"HTTP proxy + server"とあわせて機能します。 + diff --git a/core/src/main/resources/hudson/ProxyConfiguration/help-port_nl.html b/core/src/main/resources/hudson/ProxyConfiguration/help-port_nl.html index 4dfd338e28..831931d03d 100644 --- a/core/src/main/resources/hudson/ProxyConfiguration/help-port_nl.html +++ b/core/src/main/resources/hudson/ProxyConfiguration/help-port_nl.html @@ -1,3 +1,4 @@
- Met dit veld configureert U de HTTP proxy poort die de proxy server dient te gebruiken. -
\ No newline at end of file + Met dit veld configureert U de HTTP proxy poort die de proxy server dient te + gebruiken. + diff --git a/core/src/main/resources/hudson/ProxyConfiguration/help-port_pt_BR.html b/core/src/main/resources/hudson/ProxyConfiguration/help-port_pt_BR.html index 1e2bc4bef0..250b225719 100644 --- a/core/src/main/resources/hudson/ProxyConfiguration/help-port_pt_BR.html +++ b/core/src/main/resources/hudson/ProxyConfiguration/help-port_pt_BR.html @@ -1,3 +1,4 @@
- Este campo trabalha em conjunto com o campo do servidor de proxy para especificar a porta do proxy HTTP. + Este campo trabalha em conjunto com o campo do servidor de proxy para + especificar a porta do proxy HTTP.
diff --git a/core/src/main/resources/hudson/ProxyConfiguration/help-port_tr.html b/core/src/main/resources/hudson/ProxyConfiguration/help-port_tr.html index 4a8e82eaf9..9a30a3ba39 100644 --- a/core/src/main/resources/hudson/ProxyConfiguration/help-port_tr.html +++ b/core/src/main/resources/hudson/ProxyConfiguration/help-port_tr.html @@ -1,3 +1,4 @@
- Bu alan, HTTP proxy portunu tanımlamak için, proxy sunucusu alanı ile ortaklaşa çalışır. -
\ No newline at end of file + Bu alan, HTTP proxy portunu tanımlamak için, proxy sunucusu + alanı ile ortaklaşa çalışır. + diff --git a/core/src/main/resources/hudson/ProxyConfiguration/help-port_zh_TW.html b/core/src/main/resources/hudson/ProxyConfiguration/help-port_zh_TW.html index 4a9687bccd..b195106982 100644 --- a/core/src/main/resources/hudson/ProxyConfiguration/help-port_zh_TW.html +++ b/core/src/main/resources/hudson/ProxyConfiguration/help-port_zh_TW.html @@ -1,3 +1 @@ -
- 指定 HTTP 代理伺服器連接埠，要跟「伺服器」欄位一起使用。 -
\ No newline at end of file +
指定 HTTP 代理伺服器連接埠，要跟「伺服器」欄位一起使用。
diff --git a/core/src/main/resources/hudson/ProxyConfiguration/help-userName.html b/core/src/main/resources/hudson/ProxyConfiguration/help-userName.html index 1a459f9384..80995cb339 100644 --- a/core/src/main/resources/hudson/ProxyConfiguration/help-userName.html +++ b/core/src/main/resources/hudson/ProxyConfiguration/help-userName.html @@ -1,10 +1,12 @@
- This field works in conjunction with the proxy server field - to specify the username used to authenticate with the proxy. + This field works in conjunction with the proxy server field to specify the + username used to authenticate with the proxy.

- If this proxy requires Microsofts NTLM - authentication scheme then the domain name can be encoded - within the username by prefixing the domain name followed - by a back-slash '\' before the username, e.g "ACME\John Doo". + If this proxy requires Microsofts + NTLM + authentication scheme then the domain name can be encoded within the + username by prefixing the domain name followed by a back-slash '\' before + the username, e.g "ACME\John Doo". +

diff --git a/core/src/main/resources/hudson/ProxyConfiguration/help-userName_bg.html b/core/src/main/resources/hudson/ProxyConfiguration/help-userName_bg.html index d6e402ef9d..d300f099ae 100644 --- a/core/src/main/resources/hudson/ProxyConfiguration/help-userName_bg.html +++ b/core/src/main/resources/hudson/ProxyConfiguration/help-userName_bg.html @@ -2,8 +2,9 @@ Това поле определя името за идентификация пред сървъра-посредник .

- Ако този сървър-посредник ползва схемата да идентификация на - Microsoft: NTLM, - то името за домейна се добавя пред потребителското име с - разделител „\“. Например: „ACME\John Doo“". + Ако този сървър-посредник ползва схемата да идентификация на Microsoft: + NTLM + , то името за домейна се добавя пред потребителското име с разделител „\“. + Например: „ACME\John Doo“". +

diff --git a/core/src/main/resources/hudson/ProxyConfiguration/help-userName_de.html b/core/src/main/resources/hudson/ProxyConfiguration/help-userName_de.html index 3058237215..da9b34f483 100644 --- a/core/src/main/resources/hudson/ProxyConfiguration/help-userName_de.html +++ b/core/src/main/resources/hudson/ProxyConfiguration/help-userName_de.html @@ -1,11 +1,14 @@
- Dieses Feld arbeitet im Zusammenspiel mit dem Proxy-Server-Feld - und gibt den Benutzernamen an, der zur Authentifizierung - gegenüber dem Proxy verwendet wird. + Dieses Feld arbeitet im Zusammenspiel mit dem Proxy-Server-Feld und gibt den + Benutzernamen an, der zur Authentifizierung gegenüber dem Proxy verwendet + wird.

- Wenn der Proxy Microsofts - NTLM-Authentifizierungsschema verwendet, kann die Domäne durch - Voranstellen des Domänennamens, gefolgt von einem umgekehrten Schrägstrich, - angegeben werden, also z.B. "ACME\John Doo". + Wenn der Proxy Microsofts + + NTLM-Authentifizierungsschema + + verwendet, kann die Domäne durch Voranstellen des Domänennamens, gefolgt von + einem umgekehrten Schrägstrich, angegeben werden, also z.B. "ACME\John Doo". +

diff --git a/core/src/main/resources/hudson/ProxyConfiguration/help-userName_it.html b/core/src/main/resources/hudson/ProxyConfiguration/help-userName_it.html index fb3c5f4d1d..6800e1936d 100644 --- a/core/src/main/resources/hudson/ProxyConfiguration/help-userName_it.html +++ b/core/src/main/resources/hudson/ProxyConfiguration/help-userName_it.html @@ -3,9 +3,10 @@ il nome utente utilizzato per l'autenticazione al proxy.

- Se questo proxy richiede lo schema di autenticazione Microsoft - NTLM, è possibile codificare - il nome di dominio all'interno del nome utente aggiungendo all'inizio, prima - del nome utente, il nome del dominio seguito da una barra contraria ("\"), - ad es. "ACME\Mario Rossi". + Se questo proxy richiede lo schema di autenticazione Microsoft + NTLM + , è possibile codificare il nome di dominio all'interno del nome utente + aggiungendo all'inizio, prima del nome utente, il nome del dominio seguito + da una barra contraria ("\"), ad es. "ACME\Mario Rossi". +

diff --git a/core/src/main/resources/hudson/ProxyConfiguration/help-userName_ja.html b/core/src/main/resources/hudson/ProxyConfiguration/help-userName_ja.html index 3493ba8908..9604018119 100644 --- a/core/src/main/resources/hudson/ProxyConfiguration/help-userName_ja.html +++ b/core/src/main/resources/hudson/ProxyConfiguration/help-userName_ja.html @@ -2,6 +2,9 @@ この項目はサーバー名と併せて使用し、PROXY認証で使用するユーザー名を指定します。

- プロキシーがMicrosoftのNTLM認証が必要なら、 - ドメイン名は、"ACME\John Doo"のように、ユーザー名の前にバックスラッシュ''\''で区切って入力します。 + プロキシーがMicrosoftの + NTLM + 認証が必要なら、 ドメイン名は、"ACME\John + Doo"のように、ユーザー名の前にバックスラッシュ''\''で区切って入力します。 +

diff --git a/core/src/main/resources/hudson/ProxyConfiguration/help-userName_zh_TW.html b/core/src/main/resources/hudson/ProxyConfiguration/help-userName_zh_TW.html index b85f901347..fe21c1b0c6 100644 --- a/core/src/main/resources/hudson/ProxyConfiguration/help-userName_zh_TW.html +++ b/core/src/main/resources/hudson/ProxyConfiguration/help-userName_zh_TW.html @@ -2,6 +2,9 @@ 指定代理伺服器驗證用的使用者名稱，要跟「伺服器」欄位一起使用。

- 如果代理伺服器要用到 Microsoft 的 NTLM - 驗證配置，可以把網域名稱跟反斜線 '\' 加到使用者名稱前，例如 "ACME\John Doo"。 + 如果代理伺服器要用到 Microsoft 的 + NTLM + 驗證配置，可以把網域名稱跟反斜線 '\' 加到使用者名稱前，例如 "ACME\John + Doo"。 +

diff --git a/core/src/main/resources/hudson/console/ExpandableDetailsNote/script.js b/core/src/main/resources/hudson/console/ExpandableDetailsNote/script.js index 39b041f4d9..edccad221f 100644 --- a/core/src/main/resources/hudson/console/ExpandableDetailsNote/script.js +++ b/core/src/main/resources/hudson/console/ExpandableDetailsNote/script.js @@ -1,8 +1,14 @@ -(function() { - Behaviour.specify("INPUT.reveal-expandable-detail", 'ExpandableDetailsNote', 0, function(e) { - var detail = e.nextSibling; - makeButton(e,function() { - detail.style.display = (detail.style.display=="block")?"none":"block"; - }); - }); -}()); +(function () { + Behaviour.specify( + "INPUT.reveal-expandable-detail", + "ExpandableDetailsNote", + 0, + function (e) { + var detail = e.nextSibling; + makeButton(e, function () { + detail.style.display = + detail.style.display == "block" ? "none" : "block"; + }); + } + ); +})(); diff --git a/core/src/main/resources/hudson/console/ExpandableDetailsNote/style.css b/core/src/main/resources/hudson/console/ExpandableDetailsNote/style.css index c1bbffc387..3015eb2ba7 100644 --- a/core/src/main/resources/hudson/console/ExpandableDetailsNote/style.css +++ b/core/src/main/resources/hudson/console/ExpandableDetailsNote/style.css @@ -1,6 +1,6 @@ DIV.expandable-detail { - display: none; - background-color: #d3d7cf; - margin: 0.5em; - padding: 0.5em; -} \ No newline at end of file + display: none; + background-color: #d3d7cf; + margin: 0.5em; + padding: 0.5em; +} diff --git a/core/src/main/resources/hudson/diagnosis/ReverseProxySetupMonitor/resources.css b/core/src/main/resources/hudson/diagnosis/ReverseProxySetupMonitor/resources.css index a4c7b779cb..d24b24d019 100644 --- a/core/src/main/resources/hudson/diagnosis/ReverseProxySetupMonitor/resources.css +++ b/core/src/main/resources/hudson/diagnosis/ReverseProxySetupMonitor/resources.css @@ -1,3 +1,3 @@ -.reverse-proxy__hidden { - display: none; +.reverse-proxy__hidden { + display: none; } diff --git a/core/src/main/resources/hudson/diagnosis/ReverseProxySetupMonitor/resources.js b/core/src/main/resources/hudson/diagnosis/ReverseProxySetupMonitor/resources.js index 17c29cc43b..b15e7ac8af 100644 --- a/core/src/main/resources/hudson/diagnosis/ReverseProxySetupMonitor/resources.js +++ b/core/src/main/resources/hudson/diagnosis/ReverseProxySetupMonitor/resources.js @@ -1,49 +1,53 @@ (function () { - var redirectForm = document.getElementById('redirect-error'); - if (!redirectForm) { - console.warn('This script expects to have an element with id="redirect-error" to be working.'); - return; - } + var redirectForm = document.getElementById("redirect-error"); + if (!redirectForm) { + console.warn( + 'This script expects to have an element with id="redirect-error" to be working.' + ); + return; + } - var urlToTest = redirectForm.getAttribute('data-url'); - var callUrlToTest = function(testWithContext, callback) { - var options = { - onComplete: callback - }; - if (testWithContext === true) { - options.parameters = { testWithContext: true }; - } - new Ajax.Request(urlToTest, options); - }; - - var displayWarningMessage = function(withContextMessage) { - redirectForm.classList.remove('reverse-proxy__hidden'); - if (withContextMessage === true) { - redirectForm.querySelectorAll('.js-context-message').forEach(function (node) { - return node.classList.remove('reverse-proxy__hidden'); - }); - } - }; + var urlToTest = redirectForm.getAttribute("data-url"); + var callUrlToTest = function (testWithContext, callback) { + var options = { + onComplete: callback, + }; + if (testWithContext === true) { + options.parameters = { testWithContext: true }; + } + new Ajax.Request(urlToTest, options); + }; - callUrlToTest( false, function(response) { - if (response.status !== 200) { - var context = redirectForm.getAttribute('data-context'); - // to cover the case where the JenkinsRootUrl is configured without the context - if (context) { - callUrlToTest(true, function(response2) { - if (response2.status === 200) { - // this means the root URL was configured but without the contextPath, - // so different message to display - displayWarningMessage(true); - } else { - displayWarningMessage(false); - } - }); - } else { - // redirect failed. Unfortunately, according to the spec http://www.w3.org/TR/XMLHttpRequest/ - // in case of error, we can either get 0 or a failure code - displayWarningMessage(false); - } - } - }); + var displayWarningMessage = function (withContextMessage) { + redirectForm.classList.remove("reverse-proxy__hidden"); + if (withContextMessage === true) { + redirectForm + .querySelectorAll(".js-context-message") + .forEach(function (node) { + return node.classList.remove("reverse-proxy__hidden"); + }); + } + }; + + callUrlToTest(false, function (response) { + if (response.status !== 200) { + var context = redirectForm.getAttribute("data-context"); + // to cover the case where the JenkinsRootUrl is configured without the context + if (context) { + callUrlToTest(true, function (response2) { + if (response2.status === 200) { + // this means the root URL was configured but without the contextPath, + // so different message to display + displayWarningMessage(true); + } else { + displayWarningMessage(false); + } + }); + } else { + // redirect failed. Unfortunately, according to the spec http://www.w3.org/TR/XMLHttpRequest/ + // in case of error, we can either get 0 or a failure code + displayWarningMessage(false); + } + } + }); })(); diff --git a/core/src/main/resources/hudson/model/AbstractItem/help-displayNameOrNull.html b/core/src/main/resources/hudson/model/AbstractItem/help-displayNameOrNull.html index 7fcef06e11..870c7bc2d0 100644 --- a/core/src/main/resources/hudson/model/AbstractItem/help-displayNameOrNull.html +++ b/core/src/main/resources/hudson/model/AbstractItem/help-displayNameOrNull.html @@ -1,7 +1,8 @@
-If set, the optional display name is shown for the project throughout the Jenkins -web GUI. As it is for display purposes only, the display name is not required to be -unique amongst projects.
-If the display name is not set, the Jenkins web GUI will default to showing the -project name. -
\ No newline at end of file + If set, the optional display name is shown for the project throughout the + Jenkins web GUI. As it is for display purposes only, the display name is not + required to be unique amongst projects. +
+ If the display name is not set, the Jenkins web GUI will default to showing + the project name. + diff --git a/core/src/main/resources/hudson/model/AbstractItem/help-displayNameOrNull_bg.html b/core/src/main/resources/hudson/model/AbstractItem/help-displayNameOrNull_bg.html index 2667194046..878fc812f5 100644 --- a/core/src/main/resources/hudson/model/AbstractItem/help-displayNameOrNull_bg.html +++ b/core/src/main/resources/hudson/model/AbstractItem/help-displayNameOrNull_bg.html @@ -1,7 +1,8 @@
-Ако е зададено, незадължителното показвано име се използва за проекта в -интерфейса на Jenkins. Понеже се ползва чисто визуално, няма изискване за -уникалност на това име на проект.
-Ако не е зададено показвано име, интерфейсът на Jenkins показва обичайното -име на проект. -
\ No newline at end of file + Ако е зададено, незадължителното показвано име се използва за проекта в + интерфейса на Jenkins. Понеже се ползва чисто визуално, няма изискване за + уникалност на това име на проект. +
+ Ако не е зададено показвано име, интерфейсът на Jenkins показва обичайното име + на проект. + diff --git a/core/src/main/resources/hudson/model/AbstractItem/help-displayNameOrNull_de.html b/core/src/main/resources/hudson/model/AbstractItem/help-displayNameOrNull_de.html index ffe2bb7f80..e8b0dc2379 100644 --- a/core/src/main/resources/hudson/model/AbstractItem/help-displayNameOrNull_de.html +++ b/core/src/main/resources/hudson/model/AbstractItem/help-displayNameOrNull_de.html @@ -1,8 +1,9 @@
-Wenn Sie hier einen Anzeigenamen eingeben, verwendet Jenkins diesen durchgängig -statt des Projektnamens, wo immer im Web-Interface das Projekt angezeigt wird. -Da dieser Wert nur der Anzeige dient, dürfen mehrere Projekte denselben Anzeigenamen -haben.
-Wenn Sie diesen Wert leer lassen, verwendet Jenkins an allen relevanten Stellen den -Projektnamen. -
\ No newline at end of file + Wenn Sie hier einen Anzeigenamen eingeben, verwendet Jenkins diesen + durchgängig statt des Projektnamens, wo immer im Web-Interface das Projekt + angezeigt wird. Da dieser Wert nur der Anzeige dient, dürfen mehrere Projekte + denselben Anzeigenamen haben. +
+ Wenn Sie diesen Wert leer lassen, verwendet Jenkins an allen relevanten + Stellen den Projektnamen. + diff --git a/core/src/main/resources/hudson/model/AbstractItem/help-displayNameOrNull_it.html b/core/src/main/resources/hudson/model/AbstractItem/help-displayNameOrNull_it.html index aa1cb3e7da..0f6c8d60ba 100644 --- a/core/src/main/resources/hudson/model/AbstractItem/help-displayNameOrNull_it.html +++ b/core/src/main/resources/hudson/model/AbstractItem/help-displayNameOrNull_it.html @@ -1,8 +1,9 @@
-Se impostato, il nome visualizzato (facoltativo) sarà visualizzato in -riferimento al progetto in tutta l'interfaccia utente Web di Jenkins. Dal -momento che tale nome è utilizzato solo per scopi di visualizzazione, non è -richiesto che sia univoco per ogni progetto.
-Se il nome visualizzato non è impostato, l'interfaccia utente Web di Jenkins -visualizzerà il nome del progetto per impostazione predefinita. + Se impostato, il nome visualizzato (facoltativo) sarà visualizzato in + riferimento al progetto in tutta l'interfaccia utente Web di Jenkins. Dal + momento che tale nome è utilizzato solo per scopi di visualizzazione, non è + richiesto che sia univoco per ogni progetto. +
+ Se il nome visualizzato non è impostato, l'interfaccia utente Web di Jenkins + visualizzerà il nome del progetto per impostazione predefinita.
diff --git a/core/src/main/resources/hudson/model/AbstractItem/help-displayNameOrNull_ja.html b/core/src/main/resources/hudson/model/AbstractItem/help-displayNameOrNull_ja.html index bc74fac64c..4f00a893a8 100644 --- a/core/src/main/resources/hudson/model/AbstractItem/help-displayNameOrNull_ja.html +++ b/core/src/main/resources/hudson/model/AbstractItem/help-displayNameOrNull_ja.html @@ -1,5 +1,5 @@
-Jenkinsの画面に表示用のプロジェクト名を表示します。表示のためだけのものですので、他のプロジェクトと重複しても問題ありません。 -
-表示用プロジェクト名を設定しない場合、Jenkinsの画面にはプロジェクト名を表示します。 -
\ No newline at end of file + Jenkinsの画面に表示用のプロジェクト名を表示します。表示のためだけのものですので、他のプロジェクトと重複しても問題ありません。 +
+ 表示用プロジェクト名を設定しない場合、Jenkinsの画面にはプロジェクト名を表示します。 + diff --git a/core/src/main/resources/hudson/model/AbstractItem/help-displayNameOrNull_zh_TW.html b/core/src/main/resources/hudson/model/AbstractItem/help-displayNameOrNull_zh_TW.html index 89c79f4ffa..bb4cdd9e3b 100644 --- a/core/src/main/resources/hudson/model/AbstractItem/help-displayNameOrNull_zh_TW.html +++ b/core/src/main/resources/hudson/model/AbstractItem/help-displayNameOrNull_zh_TW.html @@ -1,5 +1,6 @@
-設定後，Jenkins 網頁就會用這個名稱來顯示。因為只是單純顯示用，所以不同專案的顯示名稱可以相同。 -
-如果沒有設定，Jenkins 網頁上預設會用專案的名稱。 -
\ No newline at end of file + 設定後，Jenkins + 網頁就會用這個名稱來顯示。因為只是單純顯示用，所以不同專案的顯示名稱可以相同。 +
+ 如果沒有設定，Jenkins 網頁上預設會用專案的名稱。 + diff --git a/core/src/main/resources/hudson/model/AbstractItem/help-slaveAffinity.html b/core/src/main/resources/hudson/model/AbstractItem/help-slaveAffinity.html index e120ea844b..457962dfe0 100644 --- a/core/src/main/resources/hudson/model/AbstractItem/help-slaveAffinity.html +++ b/core/src/main/resources/hudson/model/AbstractItem/help-slaveAffinity.html @@ -1,15 +1,22 @@
- By default, builds of this project may be executed on any agents that - are available and configured to accept new builds. + By default, builds of this project may be executed on any agents that are + available and configured to accept new builds.

- When this option is checked, you have the possibility to ensure that builds of - this project only occur on a certain agent, or set of agents. + When this option is checked, you have the possibility to ensure that builds + of this project only occur on a certain agent, or set of agents. +

+

- For example, if your project should only be built on a certain operating - system, or on machines that have a certain set of tools installed, or even one - specific machine, you can restrict this project to only execute on agents that - that meet those criteria. + For example, if your project should only be built on a certain operating + system, or on machines that have a certain set of tools installed, or even + one specific machine, you can restrict this project to only execute on + agents that that meet those criteria. +

+

- The help text for the Label Expression field, shown when this option is - checked, provides more detailed information on how to specify agent criteria. + The help text for the + Label Expression + field, shown when this option is checked, provides more detailed information + on how to specify agent criteria. +

diff --git a/core/src/main/resources/hudson/model/AbstractItem/help-slaveAffinity_bg.html b/core/src/main/resources/hudson/model/AbstractItem/help-slaveAffinity_bg.html index 1faffbac16..dcb72d5d72 100644 --- a/core/src/main/resources/hudson/model/AbstractItem/help-slaveAffinity_bg.html +++ b/core/src/main/resources/hudson/model/AbstractItem/help-slaveAffinity_bg.html @@ -2,14 +2,21 @@ Стандартно, всеки наличен и настроен да приема нови изграждания агент може да изгради проекта.

- Ако изберете тази опция може да осигурите изграждането на проекта да се - извършва от определена група от компютри (в частност — само един компютър). + Ако изберете тази опция може да осигурите изграждането на проекта да се + извършва от определена група от компютри (в частност — само един компютър). +

+

- Например, ако проектът трябва да се изгражда само на определени - операционни системи или на компютри, на които са инсталирани специфични - инструменти, можете да укажете на проекта да се изгражда само на машини, - коитоy отговарят на интересуващите ви критерии. + Например, ако проектът трябва да се изгражда само на определени операционни + системи или на компютри, на които са инсталирани специфични инструменти, + можете да укажете на проекта да се изгражда само на машини, коитоy отговарят + на интересуващите ви критерии. +

+

- Помощният текст за полето Израз с етикети, което се показва, когато - сте избрали тази опция, съдържа повече информация, как се указват критерии. + Помощният текст за полето + Израз с етикети + , което се показва, когато сте избрали тази опция, съдържа повече + информация, как се указват критерии. +

diff --git a/core/src/main/resources/hudson/model/AbstractItem/help-slaveAffinity_fr.html b/core/src/main/resources/hudson/model/AbstractItem/help-slaveAffinity_fr.html index 80e130c8bd..5d7992007d 100644 --- a/core/src/main/resources/hudson/model/AbstractItem/help-slaveAffinity_fr.html +++ b/core/src/main/resources/hudson/model/AbstractItem/help-slaveAffinity_fr.html @@ -1,14 +1,12 @@ 
Parfois, un projet ne peut être construit que sur une machine-agent - particulière. Dans ce cas, cette option force Jenkins à toujours - construire ce projet sur cette machine. - - Si cette stratégie n'est pas nécessaire, décochez la case afin que - Jenkins puisse programmer des builds sur les machines les plus + particulière. Dans ce cas, cette option force Jenkins à toujours construire ce + projet sur cette machine. Si cette stratégie n'est pas nécessaire, décochez la + case afin que Jenkins puisse programmer des builds sur les machines les plus disponibles, ce qui donnera un meilleur temps de réponse.

- Cette option est également utile quand vous souhaitez vous assurer qu'un - projet peut réellement être construit sur un noeud (machine) - particulier. -

\ No newline at end of file + Cette option est également utile quand vous souhaitez vous assurer qu'un + projet peut réellement être construit sur un noeud (machine) particulier. +

+ diff --git a/core/src/main/resources/hudson/model/AbstractItem/help-slaveAffinity_it.html b/core/src/main/resources/hudson/model/AbstractItem/help-slaveAffinity_it.html index b92d1d9558..ea929c7966 100644 --- a/core/src/main/resources/hudson/model/AbstractItem/help-slaveAffinity_it.html +++ b/core/src/main/resources/hudson/model/AbstractItem/help-slaveAffinity_it.html @@ -3,17 +3,23 @@ essere eseguite su qualunque agente disponibile e configurato per accettare nuove compilazioni.

- Se quest'opzione è selezionata, si ha la possibilità di assicurarsi che le - compilazioni di questo progetto vengano eseguite solo su un determinato - agente o insieme di agenti. + Se quest'opzione è selezionata, si ha la possibilità di assicurarsi che le + compilazioni di questo progetto vengano eseguite solo su un determinato + agente o insieme di agenti. +

+

- Ad esempio, se il progetto dovrebbe essere compilato solo su un determinato - sistema operativo, oppure su macchine che hanno installato un determinato - insieme di strumenti, o addirittura su una specifica macchina, è possibile - aggiungere una restrizione al progetto in modo che la compilazione venga - eseguita solo sugli agenti che rispettano questi criteri. + Ad esempio, se il progetto dovrebbe essere compilato solo su un determinato + sistema operativo, oppure su macchine che hanno installato un determinato + insieme di strumenti, o addirittura su una specifica macchina, è possibile + aggiungere una restrizione al progetto in modo che la compilazione venga + eseguita solo sugli agenti che rispettano questi criteri. +

+

- Il testo della guida per il campo Espressione etichetta, visualizzato - quando quest'opzione è selezionata, fornisce informazioni più dettagliate - su come specificare i criteri di selezione dell'agente. + Il testo della guida per il campo + Espressione etichetta + , visualizzato quando quest'opzione è selezionata, fornisce informazioni più + dettagliate su come specificare i criteri di selezione dell'agente. +

diff --git a/core/src/main/resources/hudson/model/AbstractItem/help-slaveAffinity_ja.html b/core/src/main/resources/hudson/model/AbstractItem/help-slaveAffinity_ja.html index 4444250752..e1e0eb3788 100644 --- a/core/src/main/resources/hudson/model/AbstractItem/help-slaveAffinity_ja.html +++ b/core/src/main/resources/hudson/model/AbstractItem/help-slaveAffinity_ja.html @@ -1,16 +1,19 @@ 
特定のエージェント(もしくはマスタ)でしか、ビルドできないプロジェクトがあります。 そのような場合にこのオプションを設定すると、 - そのプロジェクトをある特定のコンピューターでのみビルドするようにできます。 -　 -

　 - そのプロジェクトをビルドできるコンピューターのグループがあるなら、プロジェクトを結びつけるノードとしてラベルを設定することができます。 - そうすることで、Jenkinsはそのラベルを持ついずれかのコンピューター上でビルドを実行します。 + そのプロジェクトをある特定のコンピューターでのみビルドするようにできます。 　 +

+ 　 + そのプロジェクトをビルドできるコンピューターのグループがあるなら、プロジェクトを結びつけるノードとしてラベルを設定することができます。 + そうすることで、Jenkinsはそのラベルを持ついずれかのコンピューター上でビルドを実行します。 +

- そうでなければ、利用可能なノードでビルドをスケジューリングできるように、チェックをはずしてください。 - 所要時間が短くなります。 + そうでなければ、利用可能なノードでビルドをスケジューリングできるように、チェックをはずしてください。 + 所要時間が短くなります。 +

- このオプションは、あるプロジェクトを特定のノードでビルドできるか確認したい場合にも便利です。 + このオプションは、あるプロジェクトを特定のノードでビルドできるか確認したい場合にも便利です。 +

diff --git a/core/src/main/resources/hudson/model/AbstractItem/help-slaveAffinity_ru.html b/core/src/main/resources/hudson/model/AbstractItem/help-slaveAffinity_ru.html index 2ff5bf2c09..a938455857 100644 --- a/core/src/main/resources/hudson/model/AbstractItem/help-slaveAffinity_ru.html +++ b/core/src/main/resources/hudson/model/AbstractItem/help-slaveAffinity_ru.html @@ -1,12 +1,11 @@ 
- Иногда проект может быть собран только на конкретном узле (или мастере). - Если это так, эта опция указывает Jenkins всегда выполнять сборку только на указанном узле - или узлах. - - Иначе, снимите флажок и Jenkins будет выполнять сборки на свободных узлах, что - снизит временные затраты на сборку. + Иногда проект может быть собран только на конкретном узле (или мастере). Если + это так, эта опция указывает Jenkins всегда выполнять сборку только на + указанном узле или узлах. Иначе, снимите флажок и Jenkins будет выполнять + сборки на свободных узлах, что снизит временные затраты на сборку.

- Эта опция также полезна если вы желаете удостовериться в том, что проект - может собираться на каком-то конкретном узле. -

\ No newline at end of file + Эта опция также полезна если вы желаете удостовериться в том, что проект + может собираться на каком-то конкретном узле. +

+ diff --git a/core/src/main/resources/hudson/model/AbstractProject/help-concurrentBuild.html b/core/src/main/resources/hudson/model/AbstractProject/help-concurrentBuild.html index 3ade7054a4..8851221d3b 100644 --- a/core/src/main/resources/hudson/model/AbstractProject/help-concurrentBuild.html +++ b/core/src/main/resources/hudson/model/AbstractProject/help-concurrentBuild.html @@ -1,39 +1,65 @@ -
When this option is checked, multiple builds of this project may be executed in parallel.

- By default, only a single build of a project is executed at a time — any - other requests to start building that project will remain in the build queue - until the first build is complete.
- This is a safe default, as projects can often require exclusive access to - certain resources, such as a database, or a piece of hardware. + By default, only a single build of a project is executed at a time — + any other requests to start building that project will remain in the build + queue until the first build is complete. +
+ This is a safe default, as projects can often require exclusive access to + certain resources, such as a database, or a piece of hardware. +

+

- But with this option enabled, if there are enough build executors available - that can handle this project, then multiple builds of this project will take - place in parallel. If there are not enough available executors at any point, - any further build requests will be held in the build queue as normal. + But with this option enabled, if there are enough build executors available + that can handle this project, then multiple builds of this project will take + place in parallel. If there are not enough available executors at any point, + any further build requests will be held in the build queue as normal. +

+

- Enabling concurrent builds is useful for projects that execute lengthy test - suites, as it allows each build to contain a smaller number of changes, while - the total turnaround time decreases as subsequent builds do not need to wait - for previous test runs to complete.
- This feature is also useful for parameterized projects, whose individual build - executions — depending on the parameters used — can be - completely independent from one another. + Enabling concurrent builds is useful for projects that execute lengthy test + suites, as it allows each build to contain a smaller number of changes, + while the total turnaround time decreases as subsequent builds do not need + to wait for previous test runs to complete. +
+ This feature is also useful for parameterized projects, whose individual + build executions — depending on the parameters used — can be + completely independent from one another. +

+

- Each concurrently executed build occurs in its own build workspace, isolated - from any other builds. By default, Jenkins appends "@<num>" to - the workspace directory name, e.g. "@2".
- The separator "@" can be changed by setting the - hudson.slaves.WorkspaceList Java system property when starting - Jenkins. For example, "hudson.slaves.WorkspaceList=-" would change - the separator to a hyphen.
- For more information on setting system properties, see the wiki page. + Each concurrently executed build occurs in its own build workspace, isolated + from any other builds. By default, Jenkins appends " + @<num> + " to the workspace directory name, e.g. " + @2 + ". +
+ The separator " + @ + " can be changed by setting the + hudson.slaves.WorkspaceList + Java system property when starting Jenkins. For example, " + hudson.slaves.WorkspaceList=- + " would change the separator to a hyphen. +
+ For more information on setting system properties, see the + + wiki page + + . +

+

- However, if you enable the Use custom workspace option, all builds will - be executed in the same workspace. Therefore caution is required, as multiple - builds may end up altering the same directory at the same time. + However, if you enable the + Use custom workspace + option, all builds will be executed in the same workspace. Therefore caution + is required, as multiple builds may end up altering the same directory at + the same time. +

diff --git a/core/src/main/resources/hudson/model/AbstractProject/help-concurrentBuild_bg.html b/core/src/main/resources/hudson/model/AbstractProject/help-concurrentBuild_bg.html index 71f60235ee..4ae5b764ca 100644 --- a/core/src/main/resources/hudson/model/AbstractProject/help-concurrentBuild_bg.html +++ b/core/src/main/resources/hudson/model/AbstractProject/help-concurrentBuild_bg.html @@ -1,43 +1,68 @@ -
Когато тази опция е избрана, паралелно може да се изпълняват множество изграждания на този проект.

- Стандартно, в един момент се изпълнява максимум едно изграждане на отделен - проект — последващите заявки за изграждането на проекта се поставят в опашка - да изчакат завършването на текущото изграждане, преди да се продължи със - следващото.
- Това е по-безопасният вариант, защото често проектите изискват достъпът до - определени ресурси да е поединично — например база от данни или някакво - хардуерно устройство. + Стандартно, в един момент се изпълнява максимум едно изграждане на отделен + проект — последващите заявки за изграждането на проекта се поставят в опашка + да изчакат завършването на текущото изграждане, преди да се продължи със + следващото. +
+ Това е по-безопасният вариант, защото често проектите изискват достъпът до + определени ресурси да е поединично — например база от данни или някакво + хардуерно устройство. +

+

- Ако изберете тази опция и в даден момент има достатъчно изграждащи машини, то - паралелно ще могат да се изпълняват множество изграждания на проекта. Ако в - определен момент няма достатъчно свободни машини, то заявките за изграждане ще - изчакват в опашка както обикновено. + Ако изберете тази опция и в даден момент има достатъчно изграждащи машини, + то паралелно ще могат да се изпълняват множество изграждания на проекта. Ако + в определен момент няма достатъчно свободни машини, то заявките за + изграждане ще изчакват в опашка както обикновено. +

+

- Включването на паралелните изграждане е полезно при проекти с дълги тестове, - защото това позволява отделното изграждане да съдържа сравнително малък на - брой промени, без това да увеличава прекомерно много времето за работа, защото - всяко ново изграждане няма нужда да изчаква завършването на всички предишни - изграждания.
- Тази възможност е полезна и за параметризираните проекти, чиито изграждания - може да са напълно независими едно от друго — при определени стойности на - параметрите. + Включването на паралелните изграждане е полезно при проекти с дълги тестове, + защото това позволява отделното изграждане да съдържа сравнително малък на + брой промени, без това да увеличава прекомерно много времето за работа, + защото всяко ново изграждане няма нужда да изчаква завършването на всички + предишни изграждания. +
+ Тази възможност е полезна и за параметризираните проекти, чиито изграждания + може да са напълно независими едно от друго — при определени стойности на + параметрите. +

+

- Всяко паралелно изпълнявано изграждане се извършва в отделно от всички други - работни пространства. Стандартно добавя „@<номер>“ към името на - работната директория, например „@2“.
- Разделителят „@“ може да се смени с промяната на системното свойство - на Java — „hudson.slaves.WorkspaceList“ при стартирането на Jenkins. - Например чрез „hudson.slaves.WorkspaceList=-“ ще смените разделителя - с тирето от ASCII.
- За повече информация погледнете документацията в уикито. + Всяко паралелно изпълнявано изграждане се извършва в отделно от всички други + работни пространства. Стандартно добавя „ + @<номер> + “ към името на работната директория, например „ + @2 + “. +
+ Разделителят „ + @ + “ може да се смени с промяната на системното свойство на Java — „ + hudson.slaves.WorkspaceList + “ при стартирането на Jenkins. Например чрез „ + hudson.slaves.WorkspaceList=- + “ ще смените разделителя с тирето от ASCII. +
+ За повече информация погледнете + + документацията в уикито + + . +

+

- Ако настройката Специално работно пространство е включена, всички - изграждания на проекта ще се правят в едно и също работно пространство, - поради което трябва да внимавате, защото множество изпълнения може едновременно - да променят работната директория. + Ако настройката + Специално работно пространство + е включена, всички изграждания на проекта ще се правят в едно и също работно + пространство, поради което трябва да внимавате, защото множество изпълнения + може едновременно да променят работната директория. +

diff --git a/core/src/main/resources/hudson/model/AbstractProject/help-concurrentBuild_de.html b/core/src/main/resources/hudson/model/AbstractProject/help-concurrentBuild_de.html index e294c0125d..4414810d7d 100644 --- a/core/src/main/resources/hudson/model/AbstractProject/help-concurrentBuild_de.html +++ b/core/src/main/resources/hudson/model/AbstractProject/help-concurrentBuild_de.html @@ -1,25 +1,37 @@
- Wenn angewählt, wird Jenkins Builds parallel planen und ausführen (vorausgesetzt, es existieren - ausreichend viele Build-Prozessoren und Build-Aufträge). Dies ist nützlich bei Build- und Testjobs, die - lange dauern: Wird öfter gebaut, so beinhaltet ein Build weniger Änderungen. Gleichzeitig verringert sich - die Gesamtzeit, da ein Build nun nicht mehr so lange auf das Ende des vorausgehenden Builds warten muss. - Parallele Ausführung ist oft auch in Kombination mit parametrisierten Builds nützlich, die - unabhängig voneinander gebaut werden können. + Wenn angewählt, wird Jenkins Builds parallel planen und ausführen + (vorausgesetzt, es existieren ausreichend viele Build-Prozessoren und + Build-Aufträge). Dies ist nützlich bei Build- und Testjobs, die lange dauern: + Wird öfter gebaut, so beinhaltet ein Build weniger Änderungen. Gleichzeitig + verringert sich die Gesamtzeit, da ein Build nun nicht mehr so lange auf das + Ende des vorausgehenden Builds warten muss. Parallele Ausführung ist oft auch + in Kombination mit parametrisierten Builds nützlich, die unabhängig + voneinander gebaut werden können. -

- Für bestimmte Arten von Jobs kann eine parallele Ausführung mehrerer Builds problematisch sein, - z.B. wenn der Build exklusiven Zugriff auf eine bestimmte Ressource, etwa eine Datenbank, voraussetzt - oder für Jobs, bei denen Jenkins als cron-Ersatz eingesetzt wird. +

+ Für bestimmte Arten von Jobs kann eine parallele Ausführung mehrerer Builds + problematisch sein, z.B. wenn der Build exklusiven Zugriff auf eine + bestimmte Ressource, etwa eine Datenbank, voraussetzt oder für Jobs, bei + denen Jenkins als cron-Ersatz eingesetzt wird. +

-

- Wenn Sie einen angepassten Arbeitsbereich verwenden und diese Option aktivieren, werden alle Ihre - Builds gleichzeitig im selben Arbeitsbereich ausgeführt. Ohne weitere Vorkehrungen von Ihrer Seite - werden Ihre Builds dann voraussichtlich miteinander kollidieren. Ist die Option deaktiviert, benutzt Jenkins - für Builds jeweils einen eigenen, isolierten Arbeitsbereich - sogar wenn sie auf demselben Knoten ausgeführt werden. +

+ Wenn Sie einen angepassten Arbeitsbereich verwenden und diese Option + aktivieren, werden alle Ihre Builds gleichzeitig im selben Arbeitsbereich + ausgeführt. Ohne weitere Vorkehrungen von Ihrer Seite werden Ihre Builds + dann voraussichtlich miteinander kollidieren. Ist die Option deaktiviert, + benutzt Jenkins für Builds jeweils einen eigenen, isolierten Arbeitsbereich + - sogar wenn sie auf demselben Knoten ausgeführt werden. +

-

- Falls Jenkins unterschiedliche Arbeitsbereiche einsetzt, hängt Jenkins "@num" an den - Verzeichnisnamen des Arbeitsbereiches, z.B. "@2". Der Separator "@" kann konfiguriert werden indem das System Property - "hudson.slaves.WorkspaceList" auf die gewünschte Separatorzeichenkette auf der Kommandozeile von Jenkins gesetzt wird. - Z.B. durch "-Dhudson.slaves.WorkspaceList=-" wird der Bindestrich als Separator verwendet. +

+ Falls Jenkins unterschiedliche Arbeitsbereiche einsetzt, hängt Jenkins "@ + num + " an den Verzeichnisnamen des Arbeitsbereiches, z.B. "@2". Der Separator "@" + kann konfiguriert werden indem das System Property + "hudson.slaves.WorkspaceList" auf die gewünschte Separatorzeichenkette auf + der Kommandozeile von Jenkins gesetzt wird. Z.B. durch + "-Dhudson.slaves.WorkspaceList=-" wird der Bindestrich als Separator + verwendet. +

diff --git a/core/src/main/resources/hudson/model/AbstractProject/help-concurrentBuild_fr.html b/core/src/main/resources/hudson/model/AbstractProject/help-concurrentBuild_fr.html index 7ed8ff558f..d74dbbbbcc 100644 --- a/core/src/main/resources/hudson/model/AbstractProject/help-concurrentBuild_fr.html +++ b/core/src/main/resources/hudson/model/AbstractProject/help-concurrentBuild_fr.html @@ -1,41 +1,77 @@ -
- Lorsque cette option est cochée, plusieurs constructions de ce projet peuvent - être exécutées en parallèle. + Lorsque cette option est cochée, plusieurs constructions de ce projet + peuvent être exécutées en parallèle.

- Par défaut, une seule construction du projet est exécutée à la fois — toutes - les autres demandes pour exécuter la construction de ce projet resteront dans la file d'attente - jusqu'à ce que la première construction soit terminée.
- Ce choix par défaut est une précaution, car les projets exigent souvent un accès exclusif à - certaines ressources, telles qu'une base de données ou un hardware spécifique. + Par défaut, une seule construction du projet est + exécutée à la fois — toutes les autres demandes + pour exécuter la construction de ce projet resteront dans la file + d'attente jusqu'à ce que la première construction soit + terminée. +
+ Ce choix par défaut est une précaution, car les projets + exigent souvent un accès exclusif à certaines ressources, + telles qu'une base de données ou un hardware spécifique. +

+

- Si cette option est activée, et s'il y a suffisamment d'exécuteurs disponibles - sachant gérer ce projet, alors les multiples constructions de ce projet tourneront - en parallèle. S'il n'y a pas assez d'exécuteurs disponibles à un moment donné, - toute autre demande de construction sera maintenue dans la file d'attente de construction - comme normalement. + Si cette option est activée, et s'il y a suffisamment + d'exécuteurs disponibles sachant gérer ce projet, alors les + multiples constructions de ce projet tourneront en parallèle. S'il + n'y a pas assez d'exécuteurs disponibles à un moment + donné, toute autre demande de construction sera maintenue dans la + file d'attente de construction comme normalement. +

+

- Activer les constructions simultanées est utile pour les projets qui exécutent de longs tests - car elle permet à chaque construction de contenir un plus petit nombre de modifications, tandis que - le temps d'exécution total diminue car les constructions suivantes n'ont pas besoin d'attendre - que les tests précédents soient terminés.
- Cette fonctionnalité est également utile pour les projets paramétrés, - dont les différentes constructions — en fonction des paramètres utilisés — - peuvent être totalement indépendantes les unes des autres. + Activer les constructions simultanées est utile pour les projets qui + exécutent de longs tests car elle permet à chaque construction + de contenir un plus petit nombre de modifications, tandis que le temps + d'exécution total diminue car les constructions suivantes n'ont pas + besoin d'attendre que les tests précédents soient + terminés. +
+ Cette fonctionnalité est également utile pour les projets + paramétrés, dont les différentes constructions — + en fonction des paramètres utilisés — peuvent être + totalement indépendantes les unes des autres. +

+

- Chaque construction exécutée en parallèle se produit dans son propre espace de travail, - isolé des autres constructions. - Par défaut, Jenkins ajoute "@<num>" au nom du répertoire de l'espace - de travail, par exemple "@2".
- Le séparateur "@" est modifiable en renseignant la valeur de la propriété système Java - hudson.slaves.WorkspaceList au démarrage de jenkins. - Par exemple, "hudson.slaves.WorkspaceList=-" modifierait - le séparateur à un trait d'union.
- Pour plus d'informations sur le paramétrage des propriétés système, voir la page du wiki. + Chaque construction exécutée en parallèle se produit + dans son propre espace de travail, isolé des autres constructions. + Par défaut, Jenkins ajoute " + @<num> + " au nom du répertoire de l'espace de travail, par exemple " + @2 + ". +
+ Le séparateur " + @ + " est modifiable en renseignant la valeur de la propriété + système Java + hudson.slaves.WorkspaceList + au démarrage de jenkins. Par exemple, " + hudson.slaves.WorkspaceList=- + " modifierait le séparateur à un trait d'union. +
+ Pour plus d'informations sur le paramétrage des + propriétés système, voir la + + page du wiki + + . +

+

- En revanche, si vous activez l'option Utiliser un espace de travail personnalisé, toutes les constructions - seront exécutées dans le même espace de travail. La prudence est donc de mise, car plusieurs - constructions peuvent finir par modifier le même répertoire en même temps. + En revanche, si vous activez l'option + Utiliser un espace de travail personnalisé + , toutes les constructions seront exécutées dans le même + espace de travail. La prudence est donc de mise, car plusieurs constructions + peuvent finir par modifier le même répertoire en même + temps. +

diff --git a/core/src/main/resources/hudson/model/AbstractProject/help-concurrentBuild_it.html b/core/src/main/resources/hudson/model/AbstractProject/help-concurrentBuild_it.html index 4b1cc72cca..b8525b416e 100644 --- a/core/src/main/resources/hudson/model/AbstractProject/help-concurrentBuild_it.html +++ b/core/src/main/resources/hudson/model/AbstractProject/help-concurrentBuild_it.html @@ -1,47 +1,73 @@ -
- Quando quest'opzione è selezionata è possibile eseguire compilazioni - multiple di questo progetto in parallelo. + Quando quest'opzione è selezionata è possibile eseguire compilazioni multiple + di questo progetto in parallelo.

- Per impostazione predefinita viene eseguita solo una singola compilazione di - un progetto per volta — qualunque altra richiesta di avvio della - compilazione di tale progetto rimarrà in coda finché la prima compilazione - non sarà stata completata.
- Questa è un'impostazione predefinita sicura, in quanto i progetti spesso - possono chiedere accesso esclusivo a determinate risorse, come un database - o una periferica hardware. + Per impostazione predefinita viene eseguita solo una singola compilazione di + un progetto per volta — qualunque altra richiesta di avvio della + compilazione di tale progetto rimarrà in coda finché la prima compilazione + non sarà stata completata. +
+ Questa è un'impostazione predefinita sicura, in quanto i progetti spesso + possono chiedere accesso esclusivo a determinate risorse, come un database o + una periferica hardware. +

+

- Con quest'opzione abilitata, tuttavia, se sono disponibili abbastanza - esecutori compilazione in grado di gestire questo progetto, allora verranno - eseguite più compilazioni di questo progetto in parallelo. Se in un dato - momento non è disponibile un numero sufficiente di esecutori, tutte le - ulteriori richieste di compilazione verranno mantenute nella coda di - compilazione come al solito. + Con quest'opzione abilitata, tuttavia, se sono disponibili abbastanza + esecutori compilazione in grado di gestire questo progetto, allora verranno + eseguite più compilazioni di questo progetto in parallelo. Se in un dato + momento non è disponibile un numero sufficiente di esecutori, tutte le + ulteriori richieste di compilazione verranno mantenute nella coda di + compilazione come al solito. +

+

- Abilitare le compilazioni concorrenti è utile per i progetti che eseguono - suite di test lunghe, in quanto consente a ogni compilazione di contenere - un numero minore di modifiche, riducendo al contempo il tempo totale di - esecuzione in quanto le compilazioni seguenti non avranno la necessità di - attendere che le precedenti esecuzioni dei test giungano a termine.
- Questa funzionalità è utile anche per i progetti parametrizzati, le cui - esecuzioni di compilazione individuali — a seconda dei parametri - utilizzati — possono essere completamente indipendenti l'una - dall'altra. + Abilitare le compilazioni concorrenti è utile per i progetti che eseguono + suite di test lunghe, in quanto consente a ogni compilazione di contenere un + numero minore di modifiche, riducendo al contempo il tempo totale di + esecuzione in quanto le compilazioni seguenti non avranno la necessità di + attendere che le precedenti esecuzioni dei test giungano a termine. +
+ Questa funzionalità è utile anche per i progetti parametrizzati, le cui + esecuzioni di compilazione individuali — a seconda dei parametri + utilizzati — possono essere completamente indipendenti l'una + dall'altra. +

+

- Ogni compilazione eseguita concorrentemente viene eseguita nel proprio - spazio di lavoro, isolata da tutte le altre compilazioni. Per impostazione - predefinita, Jenkins aggiunge "@<numero>" alla fine del nome - della directory dello spazio di lavoro, ad es. "@2".
- Il separatore "@" può essere modificato impostando la proprietà di - sistema Java hudson.slaves.WorkspaceList all'avvio di Jenkins. Ad - esempio, "hudson.slaves.WorkspaceList=-" modificherebbe il - separatore in un trattino.
- Per ulteriori informazioni sull'impostazione delle proprietà di sistema, si - veda la pagina wiki. + Ogni compilazione eseguita concorrentemente viene eseguita nel proprio + spazio di lavoro, isolata da tutte le altre compilazioni. Per impostazione + predefinita, Jenkins aggiunge " + @<numero> + " alla fine del nome della directory dello spazio di lavoro, ad es. " + @2 + ". +
+ Il separatore " + @ + " può essere modificato impostando la proprietà di sistema Java + hudson.slaves.WorkspaceList + all'avvio di Jenkins. Ad esempio, " + hudson.slaves.WorkspaceList=- + " modificherebbe il separatore in un trattino. +
+ Per ulteriori informazioni sull'impostazione delle proprietà di sistema, si + veda la + + pagina wiki + + . +

+

- Ciò nonostante, se si abilita l'opzione Utilizza spazio di lavoro - personalizzato, tutte le compilazioni saranno eseguite nello stesso - spazio di lavoro. Pertanto è richiesta attenzione in quanto più compilazioni - potrebbero modificare la stessa directory nello stesso momento. + Ciò nonostante, se si abilita l'opzione + Utilizza spazio di lavoro personalizzato + , tutte le compilazioni saranno eseguite nello stesso spazio di lavoro. + Pertanto è richiesta attenzione in quanto più compilazioni potrebbero + modificare la stessa directory nello stesso momento. +

diff --git a/core/src/main/resources/hudson/model/AbstractProject/help-concurrentBuild_ja.html b/core/src/main/resources/hudson/model/AbstractProject/help-concurrentBuild_ja.html index ff51449ac9..fb81c69d6f 100644 --- a/core/src/main/resources/hudson/model/AbstractProject/help-concurrentBuild_ja.html +++ b/core/src/main/resources/hudson/model/AbstractProject/help-concurrentBuild_ja.html @@ -1,14 +1,16 @@
- このオプションをチェックすると、複数のビルドを同時にスケジュールし実行します(十分なエグゼキューターとビルドの要求がある場合)。 - 各ビルドの変更は少ないにもかかわらずビルドやテストに時間がかかる場合に有効で、ビルドの要求が先行するビルドの完了を待つ時間をより短くすることで、 - 全体のターンアラウンドタイムを減らします。 - 個々のエグゼキューターが互いに独立しているパラメータ化されたビルドでも有効です。 + このオプションをチェックすると、複数のビルドを同時にスケジュールし実行します(十分なエグゼキューターとビルドの要求がある場合)。 + 各ビルドの変更は少ないにもかかわらずビルドやテストに時間がかかる場合に有効で、ビルドの要求が先行するビルドの完了を待つ時間をより短くすることで、 + 全体のターンアラウンドタイムを減らします。 + 個々のエグゼキューターが互いに独立しているパラメータ化されたビルドでも有効です。 -

+

上記以外のジョブで、複数ビルドを同時に実行すると問題が生じるかもしれません。例えば、データベースのようにある特定のリソースを占有するものや、 Jenkinsをクーロンの代わりに使う場合などは考えられます。 +

-

+

カスタムワークスペースを使用しているとすべてのビルドは同じワークスペースを使用するので、注意しないとビルドが衝突します。 同一ノードでビルドを実行するときには、Jenkinsは異なるワークスペースを使用して各ビルドが独立したものになるようにします。 +

diff --git a/core/src/main/resources/hudson/model/AbstractProject/help-concurrentBuild_zh_TW.html b/core/src/main/resources/hudson/model/AbstractProject/help-concurrentBuild_zh_TW.html index 46c44bc95f..ea93fafa19 100644 --- a/core/src/main/resources/hudson/model/AbstractProject/help-concurrentBuild_zh_TW.html +++ b/core/src/main/resources/hudson/model/AbstractProject/help-concurrentBuild_zh_TW.html @@ -1,20 +1,29 @@
- 啟用這項功能後，Jenkins 可以同時安排執行多個建置 (假設執行程式的數量跟要建置的作業都夠多)。 - 這個功能很適合每次建置及測試都要很久的作業，就算只有小小的變更，都不用等前一次做完就能開始， - 可以減少等候及執行的時間。 - 在參數化建置中也非常有用，因為每個建置都是互相獨立的。 + 啟用這項功能後，Jenkins 可以同時安排執行多個建置 + (假設執行程式的數量跟要建置的作業都夠多)。 + 這個功能很適合每次建置及測試都要很久的作業，就算只有小小的變更，都不用等前一次做完就能開始， + 可以減少等候及執行的時間。 + 在參數化建置中也非常有用，因為每個建置都是互相獨立的。 -

- 用在其他作業上，可能會有些狀況。 - 這類作業包括會獨佔資料庫等資源，或是把 Jenkins 當做 cron 替代方案的作業。 +

+ 用在其他作業上，可能會有些狀況。 這類作業包括會獨佔資料庫等資源，或是把 + Jenkins 當做 cron 替代方案的作業。 +

-

+

如果您同時使用自訂工作區，所有的建置作業都會在同一個工作區中執行，除非您自己做一些特別處理， 不然建置間可能會有衝突。 - 在沒有自訂工作區的情況下，就算在某個節點中同時建置，Jenkins 也會使用不同的工作區避免衝突。 + 在沒有自訂工作區的情況下，就算在某個節點中同時建置，Jenkins + 也會使用不同的工作區避免衝突。 +

-

- 當 Jenkins 建立各別獨立的工作區時，會將 "@編號" 加到工作區目錄名稱後面，例如 "@2"。 - 可以在 Jenkins 指令列中指定 hudson.slaves.WorkspaceList 系統屬性設定分隔符號 - (預設是 "@")。例如 "-Dhudson.slaves.WorkspaceList=-" 就是指定以破折號當成分隔符號。 +

+ 當 Jenkins 建立各別獨立的工作區時，會將 "@ + 編號 + " 加到工作區目錄名稱後面，例如 "@2"。 可以在 Jenkins 指令列中指定 + hudson.slaves.WorkspaceList + 系統屬性設定分隔符號 (預設是 "@")。例如 + "-Dhudson.slaves.WorkspaceList=-" + 就是指定以破折號當成分隔符號。 +

diff --git a/core/src/main/resources/hudson/model/AbstractProject/help-label.html b/core/src/main/resources/hudson/model/AbstractProject/help-label.html index 27e7ddf557..9d9a4648a2 100644 --- a/core/src/main/resources/hudson/model/AbstractProject/help-label.html +++ b/core/src/main/resources/hudson/model/AbstractProject/help-label.html @@ -1,28 +1,50 @@
Defines a logical expression which determines which agents may execute builds - of this project. This expression, when tested against the name and labels of - each available agent, will be either true or false. If the - expression evaluates to true, then that agent will be allowed to - execute builds of this project. + of this project. This expression, when tested against the name and labels of + each available agent, will be either + true + or + false + . If the expression evaluates to + true + , then that agent will be allowed to execute builds of this project.

- If this project should always be built on a specific agent, or on the built-in - node, then you can just enter the agent's name, or built-in, - respectively. + If this project should always be built on a specific agent, or on the + built-in node, then you can just enter the agent's name, or + built-in + , respectively. +

+

- However, you should generally avoid using the Name of an agent here, - preferring to target the Labels of an agent. As documented on the - configuration page for each agent, and the Configure System page for - the master, labels can be used to represent which operating system the agent - is running on, its CPU architecture, or any number of other characteristics. -
- Using labels removes the need to re-configure the label expression entered - here each time that you add, remove, or rename agents. + However, you should generally avoid using the + Name + of an agent here, preferring to target the + Labels + of an agent. As documented on the configuration page for each agent, and the + Configure System + page for the master, labels can be used to represent which operating system + the agent is running on, its CPU architecture, or any number of other + characteristics. +
+ Using labels removes the need to re-configure the label expression entered + here each time that you add, remove, or rename agents. +

+

- A label expression can be as simple as entering a single label or - agent name, for example android-builder, or - linux-machine-42.
- You can also make use of various operators to create more complex - expressions. + A label expression can be as simple as entering a single + label + or + agent name + , for example + android-builder + , or + linux-machine-42 + . +
+ You can also make use of various + operators + to create more complex expressions. +

Supported operators

The following operators are supported, in descending order of precedence: @@ -34,52 +56,86 @@
!expression
- NOT — negation; the result of expression must not be true + NOT — negation; the result of + expression + must + not + be true
a && b
- AND — both of the expressions a and b must be - true + AND — + both + of the expressions + a + and + b + must be true
a || b
- OR — either of the expressions a or b may be - true + OR — + either + of the expressions + a + or + b + may be true
a -> b
- "implies" operator — equivalent to !a || b.
- For example, windows -> x64 could be thought of as "if a Windows - agent is used, then that agent must be 64-bit", while still - allowing this project to be executed on any agents that do not have - the windows label, regardless of whether they have also have an - x64 label + "implies" operator — equivalent to + !a || b + . +
+ For example, + windows -> x64 + could be thought of as "if a Windows agent is used, then that agent + must + be 64-bit", while still allowing this project to be executed on any agents + that + do not + have the + windows + label, regardless of whether they have also have an + x64 + label
a <-> b
- "if and only if" operator — equivalent to a && b || - !a && !b
- For example, windows <-> dc2 could be thought of as "if a - Windows agent is used, then that agent must be in datacenter 2, but - if a non-Windows agent is used, then it must not be in datacenter - 2" + "if and only if" operator — equivalent to + a && b || !a && !b +
+ For example, + windows <-> dc2 + could be thought of as "if a Windows agent is used, then that agent + must + be in datacenter 2, but if a non-Windows agent is used, then it + must not + be in datacenter 2"

Notes

  • - All operators are left-associative, i.e. a -> b -> c is - equivalent to (a -> b) -> c. + All operators are left-associative, i.e. + a -> b -> c + is equivalent to + (a -> b) -> c + .
  • Labels or agent names can be surrounded with quotation marks if they - contain characters that would conflict with the operator syntax.
    - For example, "osx (10.11)" || "Windows Server". + contain characters that would conflict with the operator syntax. +
    + For example, + "osx (10.11)" || "Windows Server" + .
  • Expressions can be written without whitespace, but including it is @@ -91,38 +147,46 @@ not supported.
  • - An empty expression will always evaluate to true, matching all - agents. + An empty expression will always evaluate to + true + , matching all agents.

Examples

built-in
-
Builds of this project may be executed only on the built-in node
+
Builds of this project may be executed only on the built-in node
+
linux-machine-42
Builds of this project may be executed only on the agent with the name - linux-machine-42 (or on any machine that happens to have a label - called linux-machine-42) + linux-machine-42 + (or on any machine that happens to have a label called + linux-machine-42 + )
windows && jdk9
Builds of this project may be executed only on any Windows agent that has - version 9 of the Java Development Kit installed (assuming that agents - with JDK 9 installed have been given a jdk9 label) + version 9 of the Java Development Kit installed (assuming that agents with + JDK 9 installed have been given a + jdk9 + label)
postgres && !vm && (linux || freebsd)
Builds of this project may be executed only any on Linux or FreeBSD agent, - so long as they are not a virtual machine, and they have PostgreSQL - installed (assuming that each agent has the appropriate labels — in - particular, each agent running in a virtual machine must have the - vm label in order for this example to work as expected) + so long as they are + not + a virtual machine, and they have PostgreSQL installed (assuming that each + agent has the appropriate labels — in particular, each agent running in a + virtual machine must have the + vm + label in order for this example to work as expected)
-
diff --git a/core/src/main/resources/hudson/model/AbstractProject/help-label_bg.html b/core/src/main/resources/hudson/model/AbstractProject/help-label_bg.html index 6e36cf16bb..a01baa7989 100644 --- a/core/src/main/resources/hudson/model/AbstractProject/help-label_bg.html +++ b/core/src/main/resources/hudson/model/AbstractProject/help-label_bg.html @@ -1,84 +1,140 @@
Логически израз, който определя кои агенти могат да изграждат този проект. Изразът ще се изчисли с всеки етикет и име на всеки наличен агент и резултатът - ще е или истина, или лъжа. Само когато изразът се изчисли като - истина, агентът ще може да изгражда този проект. + ще е или + истина + , или + лъжа + . Само когато изразът се изчисли като + истина + , агентът ще може да изгражда този проект.

- Ако проектът трябва задължително да се изгражда на определен подчинен компютър - или на основния, въведете съответно името на компютъра или - built-in. + Ако проектът трябва задължително да се изгражда на определен подчинен + компютър или на основния, въведете съответно името на компютъра или + built-in + . +

+

- Като цяло трябва да избягвате употребата на името на подчинения - компютър като вместо това използвате етикетите на компютрите. Както е - документирано на страницата за настройки на всеки агент и страницата за - Системни настройки на основния компютър, етикетите могат да се - използват за определяне на кои операционни системи върви Jenkins, каква е - архитектурата на процесора както и на всякакви други характеристики. -
- Като използвате етикети елиминирате нуждата да преправяте етикетните изрази - всеки път като добавяте, махате или преименувате машини. + Като цяло трябва да избягвате употребата на + името + на подчинения компютър като вместо това използвате + етикетите + на компютрите. Както е документирано на страницата за настройки на всеки + агент и страницата за + Системни настройки + на основния компютър, етикетите могат да се използват за определяне на кои + операционни системи върви Jenkins, каква е архитектурата на процесора както + и на всякакви други характеристики. +
+ Като използвате етикети елиминирате нуждата да преправяте етикетните изрази + всеки път като добавяте, махате или преименувате машини. +

+

- Етикетният израз може да е съвсем прост, напр. единичен етикет или - име на машина като android-builder или - linux-machine-42.
- Може да ползвате и някоиоператори, за да създавате по-сложни изрази. + Етикетният израз може да е съвсем прост, напр. единичен + етикет + или + име на машина + като + android-builder + или + linux-machine-42 + . +
+ Може да ползвате и някои + оператори + , за да създавате по-сложни изрази. +

Поддържани оператори

Поддържат се следните оператори в намаляващ приоритет:
(израз)
-
- скоби — за изрично указване на приоритета на операция -
+
скоби — за изрично указване на приоритета на операция
!израз
- НЕ — отрицание, стойността на израза трябва да не е - истина. + НЕ — отрицание, стойността на + израза + трябва да + не + е истина.
a && b
- И — и двата израза a и b трябва да са - истина. + И — + и двата + израза + a + и + b + трябва да са истина.
a || b
- ИЛИ — някой от изразите a или b трябва да е - истина. + ИЛИ — + някой от + изразите + a + или + b + трябва да е истина.
a -> b
- ИМПЛИКАЦИЯ — АКО - ТО, същото като !a || b.
- Напр. windows -> x64 означава: „ако се ползва компютър под - Windows, той трябва да е 64-битов“, което също позволява проектът - да бъде изграждан на машини без етикета windows, без - значение дали имат или не етикетаx64. + ИМПЛИКАЦИЯ — АКО - ТО, същото като + !a || b + . +
+ Напр. + windows -> x64 + означава: „ако се ползва компютър под Windows, той + трябва + да е 64-битов“, което също позволява проектът да бъде изграждан на машини + без + етикета + windows + , без значение дали имат или не етикета + x64 + .
a <-> b
- ЕКВИВАЛЕНТНОСТ — АКО И САМО АКО, същото като a && b || - !a && !b
- Напр. windows <-> dc2 означава: „ако се ползва компютър под - Windows, той трябва да е в центъра за данни № 2, ако обаче се - ползва компютър, който не е под Windows, той не трябва да е в - центъра за данни № 2“. + ЕКВИВАЛЕНТНОСТ — АКО И САМО АКО, същото като + a && b || !a && !b +
+ Напр. + windows <-> dc2 + означава: „ако се ползва компютър под Windows, той + трябва + да е в центъра за данни № 2, ако обаче се ползва компютър, който не е под + Windows, той + не трябва + да е в центъра за данни № 2“.

Бележки

  • - Асоциативността на всички оператори е лява, т. е. a -> b -> c - означава: (a -> b) -> c. + Асоциативността на всички оператори е лява, т. е. + a -> b -> c + означава: + (a -> b) -> c + .
  • Етикетите или имената на компютрите може да са заградени в кавички, ако - съдържат знаци, които противоречат на синтаксиса на операторите.
    - Напр. "osx (10.11)" || "Windows Server". + съдържат знаци, които противоречат на синтаксиса на операторите. +
    + Напр. + "osx (10.11)" || "Windows Server" + .
  • Не е задължително да слагате интервали в изразите, но е добре да го @@ -90,39 +146,50 @@ изрази не се поддържа.
  • - Празен израз се изчислява като истина и напасва всички машини. + Празен израз се изчислява като + истина + и напасва всички машини.

Примери

built-in
-
Изгражданията на този проект може да са само на основния компютър на - Jenkins.
+ Изгражданията на този проект може да са само на основния компютър на + Jenkins. +
+ +
linux-machine-42
Проектът може да бъде изграден само на агент с име - linux-machine-42 (или на всяка машина, която има етикет на име - linux-machine-42). + linux-machine-42 + (или на всяка машина, която има етикет на име + linux-machine-42 + ).
windows && jdk9
Изгражданията може да се извършат на всеки подчинен компютър, който е с Windows и има версия 9 на комплекта за разработчици на Java (като - приемаме, че всеки компютър с инсталиран JDK 9 има етикета jdk9). + приемаме, че всеки компютър с инсталиран JDK 9 има етикета + jdk9 + ).
postgres && !vm && (linux || freebsd)
Изгражданията на този проект може да са на всеки агент под Linux или - FreeBSD, стига да не са във виртуална машина, и да е инсталирана - базата PostgreSQL (като приемаме, че на всяка машина са поставени - съответните етикети, напр. всяка виртуална машина е с етикет vm, - иначе примерът няма да сработи). + FreeBSD, стига да + не + са във виртуална машина, и да е инсталирана базата PostgreSQL (като + приемаме, че на всяка машина са поставени съответните етикети, напр. всяка + виртуална машина е с етикет + vm + , иначе примерът няма да сработи).
-
diff --git a/core/src/main/resources/hudson/model/AbstractProject/help-label_it.html b/core/src/main/resources/hudson/model/AbstractProject/help-label_it.html index d5a98e96dd..ba2cb3d44a 100644 --- a/core/src/main/resources/hudson/model/AbstractProject/help-label_it.html +++ b/core/src/main/resources/hudson/model/AbstractProject/help-label_it.html @@ -1,77 +1,128 @@
- Definisce un'espressione logica che determina quali agenti possano eseguire - le compilazioni di questo progetto. Quest'espression, se testata con il - nome e le etichette di ogni agente disponibile, sarà valutata come - true o false. Se l'espressione viene valutata come true, - allora a tale agente sarà consentito eseguire le compilazioni di questo + Definisce un'espressione logica che determina quali agenti possano eseguire le + compilazioni di questo progetto. Quest'espression, se testata con il nome e le + etichette di ogni agente disponibile, sarà valutata come + true + o + false + . Se l'espressione viene valutata come + true + , allora a tale agente sarà consentito eseguire le compilazioni di questo progetto.

- Se questo progetto dovrebbe essere sempre compilato su un agente specifico, - o sul nodo master Jenkins, allora si dovrebbe immettere semplicemente, - rispettivamente, il nome dell'agente o master. + Se questo progetto dovrebbe essere sempre compilato su un agente specifico, + o sul nodo master Jenkins, allora si dovrebbe immettere semplicemente, + rispettivamente, il nome dell'agente o + master + . +

+

- Ciò nonostante, si dovrebbe generalmente evitare di usare il nome di - un agente in questo campo, preferendo le etichette di un agente. - Come documentato sulla pagina di configurazione di ogni agente e sulla - pagina Configura sistema del nodo master, è possibile utilizzare - etichette per rappresentare il sistema operativo su cui è in esecuzione - l'agente, la sua architettura CPU o un qualunque numero di altre - caratteristiche. -
- L'utilizzo delle etichette fa venir meno la necessità di riconfigurare - l'espressione etichetta immessa in questo campo ogni volta che si aggiungono, - rimuovono o ridenominano agenti. + Ciò nonostante, si dovrebbe generalmente evitare di usare il + nome + di un agente in questo campo, preferendo le + etichette + di un agente. Come documentato sulla pagina di configurazione di ogni agente + e sulla pagina + Configura sistema + del nodo master, è possibile utilizzare etichette per rappresentare il + sistema operativo su cui è in esecuzione l'agente, la sua architettura CPU o + un qualunque numero di altre caratteristiche. +
+ L'utilizzo delle etichette fa venir meno la necessità di riconfigurare + l'espressione etichetta immessa in questo campo ogni volta che si + aggiungono, rimuovono o ridenominano agenti. +

+

- Un'espressione etichetta può essere semplicemente una singola - etichetta o nome agente, ad esempio - android-builder o linux-machine-42.
- È possibile inoltre utilizzare svariati operatori per creare - espressioni più complesse. + Un'espressione etichetta può essere semplicemente una singola + etichetta + o + nome agente + , ad esempio + android-builder + o + linux-machine-42 + . +
+ È possibile inoltre utilizzare svariati + operatori + per creare espressioni più complesse. +

Operatori supportati

Sono supportati i seguenti operatori in ordine di precedenza decrescente:
(espressione)
- parentesi — utilizzate per definire esplicitamente l'associatività - di un'espressione + parentesi — utilizzate per definire esplicitamente l'associatività di + un'espressione
!espressione
- NOT — negazione; il risultato di espressione non + NOT — negazione; il risultato di + espressione + non dev'essere vero
a && b
- AND — entrambe le espressioni a e b devono - essere vere + AND — + entrambe + le espressioni + a + e + b + devono essere vere
a || b
- OR — una delle espressioni a o b può essere vera + OR — + una + delle espressioni + a + o + b + può essere vera
a -> b
- operatore "implica" — equivalente ad !a || b.
- Ad esempio, windows -> x64 può essere interpretato come "se - viene utilizzato un agente Windows, allora tale agente deve + operatore "implica" — equivalente ad + !a || b + . +
+ Ad esempio, + windows -> x64 + può essere interpretato come "se viene utilizzato un agente Windows, + allora tale agente + deve essere a 64 bit", consentendo comunque l'esecuzione su qualunque agente - che non abbia l'etichetta windows, a prescindere dal - fatto che abbia l'etichetta x64 + che + non + abbia l'etichetta + windows + , a prescindere dal fatto che abbia l'etichetta + x64
a <-> b
- operatore "se e solo se" — equivalente a a && b || - !a && !b
- Ad esempio, windows <-> dc2 può essere interpretato come - "se viene utilizzato un agente Windows, allora tale agente deve + operatore "se e solo se" — equivalente a + a && b || !a && !b +
+ Ad esempio, + windows <-> dc2 + può essere interpretato come "se viene utilizzato un agente Windows, + allora tale agente + deve essere nel datacenter 2, ma se viene utilizzato un agente non Windows, - allora non deve essere nel datacenter 2" + allora + non deve + essere nel datacenter 2"
@@ -79,26 +130,33 @@
  • Tutti gli operatori sono associativi a sinistra, ossia - a -> b -> c è equivalente ad (a -> b) -> c. + a -> b -> c + è equivalente ad + (a -> b) -> c + .
  • - Le etichette o i nomi degli agenti possono essere racchiusi da - virgolette doppie se contengono caratteri che andrebbero in conflitto con - la sintassi degli operatori.
    - Ad esempio, "osx (10.11)" || "Windows Server". + Le etichette o i nomi degli agenti possono essere racchiusi da virgolette + doppie se contengono caratteri che andrebbero in conflitto con la sintassi + degli operatori. +
    + Ad esempio, + "osx (10.11)" || "Windows Server" + .
  • - Le espressioni possono essere scritte senza spazi bianchi, ma includerli - è raccomandato per questioni di leggibilità; Jenkins ignorerà gli spazi + Le espressioni possono essere scritte senza spazi bianchi, ma includerli è + raccomandato per questioni di leggibilità; Jenkins ignorerà gli spazi bianchi durante la valutazione delle espressioni.
  • - La ricerca di corrispondenze fra etichette o nomi agenti con - espressioni con caratteri jolly o espressioni regolari non è supportata. + La ricerca di corrispondenze fra etichette o nomi agenti con espressioni + con caratteri jolly o espressioni regolari non è supportata.
  • - Un'espressione vuota verrà sempre valutata come true e - corrisponderà a tutti gli agenti. + Un'espressione vuota verrà sempre valutata come + true + e corrisponderà a tutti gli agenti.
@@ -106,34 +164,40 @@
built-in
- Le compilazioni di questo progetto possono eseguite solo sul nodo - master di Jenkins + Le compilazioni di questo progetto possono eseguite solo sul nodo master + di Jenkins
linux-machine-42
Le compilazioni di questo progetto possono essere eseguite solo - sull'agente denominato linux-machine-42 (o su qualunque sistema - che abbia un'etichetta denominata linux-machine-42) + sull'agente denominato + linux-machine-42 + (o su qualunque sistema che abbia un'etichetta denominata + linux-machine-42 + )
windows && jdk9
Le compilazioni di questo progetto possono essere eseguite solo su un qualunque agente Windows che abbia installata la versione 9 del Java - Development Kit (assumendo che agli agenti su cui sia installato JDK 9 - sia stata assegnata l'etichetta jdk9) + Development Kit (assumendo che agli agenti su cui sia installato JDK 9 sia + stata assegnata l'etichetta + jdk9 + )
postgres && !vm && (linux || freebsd)
Le compilazioni di questo progetto possono essere eseguite solo su - qualunque agente Linux o FreeBSD fintantoché non siano una - macchina virtuale e abbiano PostgreSQL installato (assumendo che ogni - agente abbia le etichette appropriate — in particolare, ogni agente in - esecuzione in una macchina virtuale deve avere l'etichetta vm + qualunque agente Linux o FreeBSD fintantoché + non + siano una macchina virtuale e abbiano PostgreSQL installato (assumendo che + ogni agente abbia le etichette appropriate — in particolare, ogni agente + in esecuzione in una macchina virtuale deve avere l'etichetta + vm affinché quest'esempio funzioni come atteso)
-
diff --git a/core/src/main/resources/hudson/model/BooleanParameterDefinition/help-boolean-default.html b/core/src/main/resources/hudson/model/BooleanParameterDefinition/help-boolean-default.html index d586b51c9b..77b14e7ffc 100644 --- a/core/src/main/resources/hudson/model/BooleanParameterDefinition/help-boolean-default.html +++ b/core/src/main/resources/hudson/model/BooleanParameterDefinition/help-boolean-default.html @@ -1,3 +1 @@ -
- Specifies the default value of the field. -
\ No newline at end of file +
Specifies the default value of the field.
diff --git a/core/src/main/resources/hudson/model/BooleanParameterDefinition/help-boolean-default_bg.html b/core/src/main/resources/hudson/model/BooleanParameterDefinition/help-boolean-default_bg.html index bc7e127059..c1c6c4da64 100644 --- a/core/src/main/resources/hudson/model/BooleanParameterDefinition/help-boolean-default_bg.html +++ b/core/src/main/resources/hudson/model/BooleanParameterDefinition/help-boolean-default_bg.html @@ -1,3 +1 @@ -
- Указва стандартната стойност на полето. -
+
Указва стандартната стойност на полето.
diff --git a/core/src/main/resources/hudson/model/BooleanParameterDefinition/help-boolean-default_de.html b/core/src/main/resources/hudson/model/BooleanParameterDefinition/help-boolean-default_de.html index 1685f6a396..ec0b44a716 100644 --- a/core/src/main/resources/hudson/model/BooleanParameterDefinition/help-boolean-default_de.html +++ b/core/src/main/resources/hudson/model/BooleanParameterDefinition/help-boolean-default_de.html @@ -1,3 +1 @@ -
- Gibt den Vorgabewert für dieses Feld an. -
\ No newline at end of file +
Gibt den Vorgabewert für dieses Feld an.
diff --git a/core/src/main/resources/hudson/model/BooleanParameterDefinition/help-boolean-default_fr.html b/core/src/main/resources/hudson/model/BooleanParameterDefinition/help-boolean-default_fr.html index 1ab00dde0b..4709d58b56 100644 --- a/core/src/main/resources/hudson/model/BooleanParameterDefinition/help-boolean-default_fr.html +++ b/core/src/main/resources/hudson/model/BooleanParameterDefinition/help-boolean-default_fr.html @@ -1,3 +1 @@ -
- Spécifie la valeur par défaut de ce champ. -
\ No newline at end of file +
Spécifie la valeur par défaut de ce champ.
diff --git a/core/src/main/resources/hudson/model/BooleanParameterDefinition/help-boolean-default_it.html b/core/src/main/resources/hudson/model/BooleanParameterDefinition/help-boolean-default_it.html index 6ca32861b7..07ab8d7fbc 100644 --- a/core/src/main/resources/hudson/model/BooleanParameterDefinition/help-boolean-default_it.html +++ b/core/src/main/resources/hudson/model/BooleanParameterDefinition/help-boolean-default_it.html @@ -1,3 +1 @@ -
- Specifica il valore predefinito del campo. -
+
Specifica il valore predefinito del campo.
diff --git a/core/src/main/resources/hudson/model/BooleanParameterDefinition/help-boolean-default_ja.html b/core/src/main/resources/hudson/model/BooleanParameterDefinition/help-boolean-default_ja.html index fa0011046a..25938a269f 100644 --- a/core/src/main/resources/hudson/model/BooleanParameterDefinition/help-boolean-default_ja.html +++ b/core/src/main/resources/hudson/model/BooleanParameterDefinition/help-boolean-default_ja.html @@ -1,3 +1 @@ -
- この項目のデフォルト値を設定します。 -
\ No newline at end of file +
この項目のデフォルト値を設定します。
diff --git a/core/src/main/resources/hudson/model/BooleanParameterDefinition/help-boolean-default_ru.html b/core/src/main/resources/hudson/model/BooleanParameterDefinition/help-boolean-default_ru.html index faf9692143..5458fe5b9e 100644 --- a/core/src/main/resources/hudson/model/BooleanParameterDefinition/help-boolean-default_ru.html +++ b/core/src/main/resources/hudson/model/BooleanParameterDefinition/help-boolean-default_ru.html @@ -1,3 +1 @@ -
- Задает значение поля по умолчанию. -
\ No newline at end of file +
Задает значение поля по умолчанию.
diff --git a/core/src/main/resources/hudson/model/BooleanParameterDefinition/help-boolean-default_zh_TW.html b/core/src/main/resources/hudson/model/BooleanParameterDefinition/help-boolean-default_zh_TW.html index 71dde30413..acfb0c8454 100644 --- a/core/src/main/resources/hudson/model/BooleanParameterDefinition/help-boolean-default_zh_TW.html +++ b/core/src/main/resources/hudson/model/BooleanParameterDefinition/help-boolean-default_zh_TW.html @@ -1,3 +1 @@ -
- 指定欄位的預設值。 -
\ No newline at end of file +
指定欄位的預設值。
diff --git a/core/src/main/resources/hudson/model/BuildTimelineWidget/build-timeline-widget.js b/core/src/main/resources/hudson/model/BuildTimelineWidget/build-timeline-widget.js index 30d465f43f..eb556bad16 100644 --- a/core/src/main/resources/hudson/model/BuildTimelineWidget/build-timeline-widget.js +++ b/core/src/main/resources/hudson/model/BuildTimelineWidget/build-timeline-widget.js @@ -1,125 +1,127 @@ -var targetDiv = document.querySelector('#build-timeline-div'); -var tz = targetDiv.getAttribute('data-hour-local-timezone'); +var targetDiv = document.querySelector("#build-timeline-div"); +var tz = targetDiv.getAttribute("data-hour-local-timezone"); var tl = null; var interval = 24 * 60 * 60 * 1000; function getData(eventSource1, current, min, max) { - if (current < min) { - return; - } - if (!eventSource1.loaded[current]) { - eventSource1.loaded[current] = true; - new Ajax.Request("timeline/data/", { - method: "POST", - parameters: { min: current * interval, max: (current + 1) * interval }, - onSuccess: function (t) { - if (t.status != 0) { - try { - eventSource1.loadJSON(JSON.parse(t.responseText), '.'); - getData(eventSource1, current - 1, min, max); - } catch (e) { - alert(e); - } - } - } - }); - } + if (current < min) { + return; + } + if (!eventSource1.loaded[current]) { + eventSource1.loaded[current] = true; + new Ajax.Request("timeline/data/", { + method: "POST", + parameters: { min: current * interval, max: (current + 1) * interval }, + onSuccess: function (t) { + if (t.status != 0) { + try { + eventSource1.loadJSON(JSON.parse(t.responseText), "."); + getData(eventSource1, current - 1, min, max); + } catch (e) { + alert(e); + } + } + }, + }); + } } function doLoad() { - var tl_el = document.getElementById("tl"); - var eventSource1 = new Timeline.DefaultEventSource(); - eventSource1.loaded = {}; - eventSource1.ensureVisible = function (band) { - // make sure all data are loaded for the portion visible in the band - // $('status').innerHTML = "min="+band.getMinDate()+" max="+band.getMaxDate(); - var min = Math.floor(band.getMinVisibleDate().getTime() / interval); - var max = Math.ceil(band.getMaxVisibleDate().getTime() / interval); - getData(eventSource1, max, min, max); - }; - - - var theme1 = Timeline.ClassicTheme.create(); - //theme1.autoWidth = true; // Set the Timeline's "width" automatically. - // Set autoWidth on the Timeline's first band's theme, - // will affect all bands. - - var bandInfos = [ - // the bar that shows outline - Timeline.createBandInfo({ - width: "20%", - intervalUnit: Timeline.DateTime.DAY, - intervalPixels: 200, - eventSource: eventSource1, - timeZone: tz, - theme: theme1, - layout: 'overview' // original, overview, detailed - }), - // the main area - Timeline.createBandInfo({ - width: "80%", - eventSource: eventSource1, - timeZone: tz, - theme: theme1, - intervalUnit: Timeline.DateTime.HOUR, - intervalPixels: 200 - }) - ]; - bandInfos[0].highlight = true; - bandInfos[0].syncWith = 1; - - // create the Timeline - tl = Timeline.create(tl_el, bandInfos, Timeline.HORIZONTAL); - - tl.getBand(0).addOnScrollListener(function (band) { - eventSource1.ensureVisible(band); - }); - - tl.layout(); // display the Timeline - - // if resized, redo layout - var resizeTimerID = null; - function doResize() { - if (resizeTimerID == null) { - resizeTimerID = window.setTimeout(function () { - resizeTimerID = null; - tl.layout(); - }, 500); - } - } - - if (window.addEventListener) { - window.addEventListener("resize", doResize, false); - } else if (window.attachEvent) { - window.attachEvent("onresize", doResize); - } else if (window.onResize) { - window.onresize = doResize; + var tl_el = document.getElementById("tl"); + var eventSource1 = new Timeline.DefaultEventSource(); + eventSource1.loaded = {}; + eventSource1.ensureVisible = function (band) { + // make sure all data are loaded for the portion visible in the band + // $('status').innerHTML = "min="+band.getMinDate()+" max="+band.getMaxDate(); + var min = Math.floor(band.getMinVisibleDate().getTime() / interval); + var max = Math.ceil(band.getMaxVisibleDate().getTime() / interval); + getData(eventSource1, max, min, max); + }; + + var theme1 = Timeline.ClassicTheme.create(); + //theme1.autoWidth = true; // Set the Timeline's "width" automatically. + // Set autoWidth on the Timeline's first band's theme, + // will affect all bands. + + var bandInfos = [ + // the bar that shows outline + Timeline.createBandInfo({ + width: "20%", + intervalUnit: Timeline.DateTime.DAY, + intervalPixels: 200, + eventSource: eventSource1, + timeZone: tz, + theme: theme1, + layout: "overview", // original, overview, detailed + }), + // the main area + Timeline.createBandInfo({ + width: "80%", + eventSource: eventSource1, + timeZone: tz, + theme: theme1, + intervalUnit: Timeline.DateTime.HOUR, + intervalPixels: 200, + }), + ]; + bandInfos[0].highlight = true; + bandInfos[0].syncWith = 1; + + // create the Timeline + tl = Timeline.create(tl_el, bandInfos, Timeline.HORIZONTAL); + + tl.getBand(0).addOnScrollListener(function (band) { + eventSource1.ensureVisible(band); + }); + + tl.layout(); // display the Timeline + + // if resized, redo layout + var resizeTimerID = null; + function doResize() { + if (resizeTimerID == null) { + resizeTimerID = window.setTimeout(function () { + resizeTimerID = null; + tl.layout(); + }, 500); } - -}; + } + + if (window.addEventListener) { + window.addEventListener("resize", doResize, false); + } else if (window.attachEvent) { + window.attachEvent("onresize", doResize); + } else if (window.onResize) { + window.onresize = doResize; + } +} if (window.addEventListener) { - window.addEventListener("load", doLoad, false); + window.addEventListener("load", doLoad, false); } else if (window.attachEvent) { - window.attachEvent("onload", doLoad); + window.attachEvent("onload", doLoad); } else if (window.onLoad) { - window.onload = doLoad; + window.onload = doLoad; } //add resize handle (function () { - var Dom = YAHOO.util.Dom, - Event = YAHOO.util.Event; - - var resize = new YAHOO.util.Resize('resizeContainer', { - handles: 'b', - minHeight: 300 // this should be the same as the height of the container div, - // to fix a issue when it's resized to be smaller than the original height - }); - - //update timeline after resizing - resize.on('endResize', function () { - tl.layout(); - }, null, true); - + var Dom = YAHOO.util.Dom, + Event = YAHOO.util.Event; + + var resize = new YAHOO.util.Resize("resizeContainer", { + handles: "b", + minHeight: 300, // this should be the same as the height of the container div, + // to fix a issue when it's resized to be smaller than the original height + }); + + //update timeline after resizing + resize.on( + "endResize", + function () { + tl.layout(); + }, + null, + true + ); })(); diff --git a/core/src/main/resources/hudson/model/Job/buildTimeTrend_resources.css b/core/src/main/resources/hudson/model/Job/buildTimeTrend_resources.css index 4cadb1d1b3..13efe1c1e3 100644 --- a/core/src/main/resources/hudson/model/Job/buildTimeTrend_resources.css +++ b/core/src/main/resources/hudson/model/Job/buildTimeTrend_resources.css @@ -1,3 +1,3 @@ img.build-time-graph { - float: right; + float: right; } diff --git a/core/src/main/resources/hudson/model/Job/buildTimeTrend_resources.js b/core/src/main/resources/hudson/model/Job/buildTimeTrend_resources.js index a5feb6e9bc..e3522b4609 100644 --- a/core/src/main/resources/hudson/model/Job/buildTimeTrend_resources.js +++ b/core/src/main/resources/hudson/model/Job/buildTimeTrend_resources.js @@ -2,93 +2,123 @@ * Public method to be called by progressiveRendering's callback */ function buildTimeTrend_displayBuilds(data) { - var p = document.getElementById('trend'); - var isDistributedBuildsEnabled = 'true' === p.getAttribute("data-is-distributed-build-enabled"); - var rootURL = document.head.getAttribute('data-rooturl'); - - for (var x = 0; data.length > x; x++) { - var e = data[x]; - var tr = new Element('tr'); - tr.insert(new Element('td', {data: e.iconColorOrdinal}). - insert(new Element('a', {class: 'build-status-link', href: e.number + '/console'}). - insert(generateSVGIcon(e.iconName)))); - tr.insert(new Element('td', {data: e.number}). - insert(new Element('a', {href: e.number + '/', 'class': 'model-link inside'}). - update(e.displayName.escapeHTML()))); - tr.insert(new Element('td', {data: e.duration}). - update(e.durationString.escapeHTML())); - if (isDistributedBuildsEnabled) { - var buildInfo = null; - var buildInfoStr = (e.builtOnStr || '').escapeHTML(); - if(e.builtOn) { - buildInfo = new Element('a', {href: rootURL + '/computer/' + e.builtOn, 'class': 'model-link inside'}).update(buildInfoStr); - } else { - buildInfo = buildInfoStr; - } - tr.insert(new Element('td').update(buildInfo)); - } - p.insert(tr); - Behaviour.applySubtree(tr); - } - ts_refresh(p); + var p = document.getElementById("trend"); + var isDistributedBuildsEnabled = + "true" === p.getAttribute("data-is-distributed-build-enabled"); + var rootURL = document.head.getAttribute("data-rooturl"); + + for (var x = 0; data.length > x; x++) { + var e = data[x]; + var tr = new Element("tr"); + tr.insert( + new Element("td", { data: e.iconColorOrdinal }).insert( + new Element("a", { + class: "build-status-link", + href: e.number + "/console", + }).insert(generateSVGIcon(e.iconName)) + ) + ); + tr.insert( + new Element("td", { data: e.number }).insert( + new Element("a", { + href: e.number + "/", + class: "model-link inside", + }).update(e.displayName.escapeHTML()) + ) + ); + tr.insert( + new Element("td", { data: e.duration }).update( + e.durationString.escapeHTML() + ) + ); + if (isDistributedBuildsEnabled) { + var buildInfo = null; + var buildInfoStr = (e.builtOnStr || "").escapeHTML(); + if (e.builtOn) { + buildInfo = new Element("a", { + href: rootURL + "/computer/" + e.builtOn, + class: "model-link inside", + }).update(buildInfoStr); + } else { + buildInfo = buildInfoStr; + } + tr.insert(new Element("td").update(buildInfo)); + } + p.insert(tr); + Behaviour.applySubtree(tr); + } + ts_refresh(p); } /** * Generate SVG Icon */ function generateSVGIcon(iconName, iconSizeClass) { + const imagesURL = document.head.getAttribute("data-imagesurl"); - const imagesURL = document.head.getAttribute('data-imagesurl'); - - const isInProgress = iconName.endsWith("anime"); - let buildStatus = 'never-built'; - switch (iconName) { - case 'red': - case 'red-anime': - buildStatus = 'last-failed'; - break; - case 'yellow': - case 'yellow-anime': - buildStatus = 'last-unstable'; - break; - case 'blue': - case 'blue-anime': - buildStatus = 'last-successful'; - break; - case 'grey': - case 'grey-anime': - case 'disabled': - case 'disabled-anime': - buildStatus = 'last-disabled'; - break; - case 'aborted': - case 'aborted-anime': - buildStatus = 'last-aborted'; - break; - case 'nobuilt': - case 'nobuilt-anime': - buildStatus = 'never-built'; - break - } + const isInProgress = iconName.endsWith("anime"); + let buildStatus = "never-built"; + switch (iconName) { + case "red": + case "red-anime": + buildStatus = "last-failed"; + break; + case "yellow": + case "yellow-anime": + buildStatus = "last-unstable"; + break; + case "blue": + case "blue-anime": + buildStatus = "last-successful"; + break; + case "grey": + case "grey-anime": + case "disabled": + case "disabled-anime": + buildStatus = "last-disabled"; + break; + case "aborted": + case "aborted-anime": + buildStatus = "last-aborted"; + break; + case "nobuilt": + case "nobuilt-anime": + buildStatus = "never-built"; + break; + } - const svg1 = document.createElementNS('http://www.w3.org/2000/svg', 'svg'); - svg1.setAttribute('class', 'svg-icon'); - svg1.setAttribute('viewBox', "0 0 24 24"); - const use1 = document.createElementNS('http://www.w3.org/2000/svg', 'use'); - use1.setAttribute('href', imagesURL + '/build-status/build-status-sprite.svg#build-status-' + (isInProgress ? 'in-progress' : 'static')) - svg1.appendChild(use1); + const svg1 = document.createElementNS("http://www.w3.org/2000/svg", "svg"); + svg1.setAttribute("class", "svg-icon"); + svg1.setAttribute("viewBox", "0 0 24 24"); + const use1 = document.createElementNS("http://www.w3.org/2000/svg", "use"); + use1.setAttribute( + "href", + imagesURL + + "/build-status/build-status-sprite.svg#build-status-" + + (isInProgress ? "in-progress" : "static") + ); + svg1.appendChild(use1); - const svg2 = document.createElementNS('http://www.w3.org/2000/svg', 'svg'); - svg2.setAttribute('class', 'svg-icon icon-' + iconName + ' ' + (iconSizeClass || 'icon-sm')); - svg2.setAttribute('viewBox', "0 0 24 24"); - const use2 = document.createElementNS('http://www.w3.org/2000/svg', 'use'); - use2.setAttribute('href', imagesURL + '/build-status/build-status-sprite.svg#' + buildStatus) - svg2.appendChild(use2); + const svg2 = document.createElementNS("http://www.w3.org/2000/svg", "svg"); + svg2.setAttribute( + "class", + "svg-icon icon-" + iconName + " " + (iconSizeClass || "icon-sm") + ); + svg2.setAttribute("viewBox", "0 0 24 24"); + const use2 = document.createElementNS("http://www.w3.org/2000/svg", "use"); + use2.setAttribute( + "href", + imagesURL + "/build-status/build-status-sprite.svg#" + buildStatus + ); + svg2.appendChild(use2); - const span = new Element('span', {class: 'build-status-icon__wrapper icon-' + iconName}). - insert(new Element('span', {class: 'build-status-icon__outer'}). - insert(svg1)). - insert(svg2); + const span = new Element("span", { + class: "build-status-icon__wrapper icon-" + iconName, + }) + .insert( + new Element("span", { class: "build-status-icon__outer" }).insert(svg1) + ) + .insert(svg2); - return span; -} \ No newline at end of file + return span; +} diff --git a/core/src/main/resources/hudson/model/ListView/configure-entries-resources.js b/core/src/main/resources/hudson/model/ListView/configure-entries-resources.js index 7f4621d7a7..f036e949de 100644 --- a/core/src/main/resources/hudson/model/ListView/configure-entries-resources.js +++ b/core/src/main/resources/hudson/model/ListView/configure-entries-resources.js @@ -1,8 +1,8 @@ -Behaviour.specify("#recurse", 'ListView', 0, function (e) { - var nestedElements = $$('SPAN.nested') - e.onclick = function () { - nestedElements.each(function (el) { - e.checked ? el.show() : el.hide(); - }); - } +Behaviour.specify("#recurse", "ListView", 0, function (e) { + var nestedElements = $$("SPAN.nested"); + e.onclick = function () { + nestedElements.each(function (el) { + e.checked ? el.show() : el.hide(); + }); + }; }); diff --git a/core/src/main/resources/hudson/model/LoadStatistics/resources.js b/core/src/main/resources/hudson/model/LoadStatistics/resources.js index b4bdc926a0..60318f37a1 100644 --- a/core/src/main/resources/hudson/model/LoadStatistics/resources.js +++ b/core/src/main/resources/hudson/model/LoadStatistics/resources.js @@ -21,31 +21,39 @@ * OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN * THE SOFTWARE. */ -(function(){ - document.addEventListener("DOMContentLoaded", function() { - const graphLocation = document.querySelector('.js-load-graph'); - if (graphLocation) { - const type = graphLocation.getAttribute("data-graph-type"); - const parentSelector = graphLocation.getAttribute("data-graph-parent-selector"); - const baseUrl = graphLocation.getAttribute("data-graph-base-url"); - const graphAlt = graphLocation.getAttribute("data-graph-alt"); - - const parent = document.querySelector(parentSelector); - if (parent) { - const availableWidth = parent.offsetWidth; - const padding = 30; - // for some browsers, the perfect width is not enough - const quirkyBrowserAdjustment = 15; - const graphWidth = availableWidth - padding - quirkyBrowserAdjustment; +(function () { + document.addEventListener("DOMContentLoaded", function () { + const graphLocation = document.querySelector(".js-load-graph"); + if (graphLocation) { + const type = graphLocation.getAttribute("data-graph-type"); + const parentSelector = graphLocation.getAttribute( + "data-graph-parent-selector" + ); + const baseUrl = graphLocation.getAttribute("data-graph-base-url"); + const graphAlt = graphLocation.getAttribute("data-graph-alt"); - // type in {sec10, min, hour} - const graphUrl = baseUrl + "/graph?type=" + type + "&width=" + graphWidth + "&height=500"; - const graphImgTag = document.createElement("img"); - graphImgTag.src = graphUrl; - graphImgTag.srcset = graphUrl + "&scale=2 2x"; - graphImgTag.alt = graphAlt; - graphLocation.appendChild(graphImgTag); - } - } - }); + const parent = document.querySelector(parentSelector); + if (parent) { + const availableWidth = parent.offsetWidth; + const padding = 30; + // for some browsers, the perfect width is not enough + const quirkyBrowserAdjustment = 15; + const graphWidth = availableWidth - padding - quirkyBrowserAdjustment; + + // type in {sec10, min, hour} + const graphUrl = + baseUrl + + "/graph?type=" + + type + + "&width=" + + graphWidth + + "&height=500"; + const graphImgTag = document.createElement("img"); + graphImgTag.src = graphUrl; + graphImgTag.srcset = graphUrl + "&scale=2 2x"; + graphImgTag.alt = graphAlt; + graphLocation.appendChild(graphImgTag); + } + } + }); })(); diff --git a/core/src/main/resources/hudson/model/ParametersDefinitionProperty/help.html b/core/src/main/resources/hudson/model/ParametersDefinitionProperty/help.html index 0ad5c21cb2..8f40501bf3 100644 --- a/core/src/main/resources/hudson/model/ParametersDefinitionProperty/help.html +++ b/core/src/main/resources/hudson/model/ParametersDefinitionProperty/help.html @@ -1,36 +1,67 @@
Parameters allow you to prompt users for one or more inputs that will be - passed into a build. For example, you might have a project that runs tests on - demand by allowing users to upload a zip file with binaries to be tested. - This could be done by adding a File Parameter here. -
+ passed into a build. For example, you might have a project that runs tests on + demand by allowing users to upload a zip file with binaries to be tested. This + could be done by adding a + File Parameter + here. +
Or you might have a project that releases some software, and you want users to enter release notes that will be uploaded along with the software. This could - be done by adding a Multi-line String Parameter here. + be done by adding a + Multi-line String Parameter + here.

- Each parameter has a Name and some sort of Value, depending on - the parameter type. These name-value pairs will be exported as environment - variables when the build starts, allowing subsequent parts of the build - configuration (such as build steps) to access those values, e.g. by using the - ${PARAMETER_NAME} syntax (or %PARAMETER_NAME% on Windows). -
- This also implies that each parameter defined here should have a unique - Name. + Each parameter has a + Name + and some sort of + Value + , depending on the parameter type. These name-value pairs will be exported + as environment variables when the build starts, allowing subsequent parts of + the build configuration (such as build steps) to access those values, e.g. + by using the + ${PARAMETER_NAME} + syntax (or + %PARAMETER_NAME% + on Windows). +
+ This also implies that each parameter defined here should have a unique + Name + . +

+

- When a project is parameterized, the usual Build Now link will be - replaced with a Build with Parameters link, where users will be - prompted to specify values for each of the defined parameters. If they choose - not to enter anything, the build will start with the default value for each - parameter. + When a project is parameterized, the usual + Build Now + link will be replaced with a + Build with Parameters + link, where users will be prompted to specify values for each of the defined + parameters. If they choose not to enter anything, the build will start with + the default value for each parameter. +

+

- If a build is started automatically, for example if started by an SCM trigger, - the default values for each parameter will be used. + If a build is started automatically, for example if started by an SCM + trigger, the default values for each parameter will be used. +

+

- When a parameterized build is in the queue, attempting to start another build - of the same project will only succeed if the parameter values are different, - or if the Execute concurrent builds if necessary option is enabled. + When a parameterized build is in the queue, attempting to start another + build of the same project will only succeed if the parameter values are + different, or if the + Execute concurrent builds if necessary + option is enabled. +

+

- See the Parameterized Builds documentation for more information about - this feature. + See the + + Parameterized Builds documentation + + for more information about this feature. +

diff --git a/core/src/main/resources/hudson/model/ParametersDefinitionProperty/help_bg.html b/core/src/main/resources/hudson/model/ParametersDefinitionProperty/help_bg.html index e1c6c18263..529b6ec5fb 100644 --- a/core/src/main/resources/hudson/model/ParametersDefinitionProperty/help_bg.html +++ b/core/src/main/resources/hudson/model/ParametersDefinitionProperty/help_bg.html @@ -1,36 +1,67 @@
Параметрите позволяват на потребителите да въведат данни, които да се - използват по време на изграждането. Например, проект за тестове за - производителност при заявка, който позволява на потребителите да - качват изпълними файлове, които да се тестват. Това може да се случи - с добавянето на Параметър: файл. -
- Друга възможност е проект, който изготвя крайния вариант на програма - и искате да позволите на потребителите до прикачат към нея бележки по - версията. Може да постигнете това като добавите Параметър: многоредов - низ. + използват по време на изграждането. Например, проект за тестове за + производителност при заявка, който позволява на потребителите да качват + изпълними файлове, които да се тестват. Това може да се случи с добавянето на + Параметър: файл + . +
+ Друга възможност е проект, който изготвя крайния вариант на програма и искате + да позволите на потребителите до прикачат към нея бележки по версията. Може да + постигнете това като добавите + Параметър: многоредов низ + .

- Всеки параметър има име и стойност, която зависи от вида на - параметъра. Тези двойки име-стойност се изнасят като променливи на средата - при стартиране на изграждането, което позволява на последващите стъпки от - него да достъпват стойностите чрез синтаксиса ${ИМЕ_НА_ПАРАМЕТЪР} - (под Windows e %ИМЕ_НА_ПАРАМЕТЪР%). -
- Това е и причината името на всеки параметър да е уникално. + Всеки параметър има + име + и + стойност + , която зависи от вида на параметъра. Тези двойки име-стойност се изнасят + като променливи на средата при стартиране на изграждането, което позволява + на последващите стъпки от него да достъпват стойностите чрез синтаксиса + ${ИМЕ_НА_ПАРАМЕТЪР} + (под Windows e + %ИМЕ_НА_ПАРАМЕТЪР% + ). +
+ Това е и причината + името + на всеки параметър да е уникално. +

+

- При параметризирането на проект, стандартната връзка Изграждане - се замества с връзка Изграждане с параметри. Чрез нея потребителите - могат да указват стойности за всеки от дефинираните параметри. Ако не въведат - нищо, се използва отделна стандартна стойност за всеки от параметрите. + При параметризирането на проект, стандартната връзка + Изграждане + се замества с връзка + Изграждане с параметри + . Чрез нея потребителите могат да указват стойности за всеки от дефинираните + параметри. Ако не въведат нищо, се използва отделна стандартна стойност за + всеки от параметрите. +

+

- Ако изграждането е стартирано автоматично, например от промяна в системата за - контрол на версиите, за всеки от параметрите ще се ползва стандартната му - стойност. + Ако изграждането е стартирано автоматично, например от промяна в системата + за контрол на версиите, за всеки от параметрите ще се ползва стандартната му + стойност. +

+

- Когато има поне едно параметризирано изграждане в опашката, опит за стартирането - на друго ще е успешно, ако поне един от параметрите е различен, освен ако не е - зададена опцията Едновременно изграждане при необходимост. + Когато има поне едно параметризирано изграждане в опашката, опит за + стартирането на друго ще е успешно, ако поне един от параметрите е различен, + освен ако не е зададена опцията + Едновременно изграждане при необходимост + . +

+

- За повече информация вижте страницата за параметризираните изграждания в уикито. + За повече информация вижте + + страницата за параметризираните изграждания + + в уикито. +

diff --git a/core/src/main/resources/hudson/model/ParametersDefinitionProperty/help_de.html b/core/src/main/resources/hudson/model/ParametersDefinitionProperty/help_de.html index 42b0cd89c0..0f11357485 100644 --- a/core/src/main/resources/hudson/model/ParametersDefinitionProperty/help_de.html +++ b/core/src/main/resources/hudson/model/ParametersDefinitionProperty/help_de.html @@ -1,15 +1,22 @@
- Wenn Sie Jenkins einsetzen, um bestimmte Abläufe zu automatisieren, kann es - praktisch sein, einen Build zu "parametrisieren": Dies bedeutet, dass der Build - zu Beginn vom Benutzer Eingaben verlangt, die dem Buildprozess dann zur Verfügung stehen. - So könnten Sie beispielsweise einen Test-Job anlegen, bei dem Ihre Benutzer eine ZIP-Datei - der Software hochladen können, die getestet werden soll. + Wenn Sie Jenkins einsetzen, um bestimmte Abläufe zu automatisieren, kann es + praktisch sein, einen Build zu "parametrisieren": Dies bedeutet, dass der + Build zu Beginn vom Benutzer Eingaben verlangt, die dem Buildprozess dann zur + Verfügung stehen. So könnten Sie beispielsweise einen Test-Job anlegen, bei + dem Ihre Benutzer eine ZIP-Datei der Software hochladen können, die getestet + werden soll. -

- Dieser Abschnitt legt fest, welche Parameter Ihr Build verlangt. Parameter werden - nach Namen unterschieden. Sie können daher auch mehrere Parameter verwenden, solange - diese unterschiedliche Namen tragen. -

- Auf der Jenkins website +

+ Dieser Abschnitt legt fest, welche Parameter Ihr Build verlangt. Parameter + werden nach Namen unterschieden. Sie können daher auch mehrere Parameter + verwenden, solange diese unterschiedliche Namen tragen. +

+ +

+ Auf der + + Jenkins website + finden Sie weitere Informationen über parametrisierte Builds. +

diff --git a/core/src/main/resources/hudson/model/ParametersDefinitionProperty/help_fr.html b/core/src/main/resources/hudson/model/ParametersDefinitionProperty/help_fr.html index 56c3ed5ca7..fc3ac41d91 100644 --- a/core/src/main/resources/hudson/model/ParametersDefinitionProperty/help_fr.html +++ b/core/src/main/resources/hudson/model/ParametersDefinitionProperty/help_fr.html @@ -1,14 +1,20 @@ 
- Il est parfois pratique de rendre paramétrables certaines automatisations, en demandant des informations - à l'utilisateur. - Par exemple, vous pourriez proposer un job de test à la demande, où l'utilisateur peut soumettre un - fichier zip des binaires à tester. + Il est parfois pratique de rendre paramétrables certaines automatisations, en + demandant des informations à l'utilisateur. Par exemple, vous pourriez + proposer un job de test à la demande, où l'utilisateur peut soumettre un + fichier zip des binaires à tester. -

- Cette section configure les paramètres que prend votre build. Les paramètres sont identifiés par leur - nom. Vous pouvez donc avoir de multiples paramètres, s'ils ont bien des noms distincts. +

+ Cette section configure les paramètres que prend votre build. Les paramètres + sont identifiés par leur nom. Vous pouvez donc avoir de multiples + paramètres, s'ils ont bien des noms distincts. +

-

- Consultez cette page +

+ Consultez + + cette page + pour plus de discussions autour de cette fonctionnalité. +

diff --git a/core/src/main/resources/hudson/model/ParametersDefinitionProperty/help_it.html b/core/src/main/resources/hudson/model/ParametersDefinitionProperty/help_it.html index cccfa4f907..f738e6f285 100644 --- a/core/src/main/resources/hudson/model/ParametersDefinitionProperty/help_it.html +++ b/core/src/main/resources/hudson/model/ParametersDefinitionProperty/help_it.html @@ -3,40 +3,68 @@ forniti a una compilazione. Ad esempio, si potrebbe avere un progetto che esegue test su richiesta consentendo agli utenti di caricare un file ZIP contenente i binari da testare. Si potrebbe ottenere tale risultato - aggiungendo qui un Parametro file. -
+ aggiungendo qui un + Parametro file + . +
Oppure si potrebbe avere un progetto che rilascia del software e si desidera che gli utenti immettano delle note di rilascio che saranno caricate insieme al software. Si potrebbe ottenere tale risultato aggiungendo qui un - Parametro stringa multiriga. + Parametro stringa multiriga + .

- Ogni parametro ha un Nome e qualche tipo di Valore che - dipende dal tipo del parametro. Queste coppie nome-valore saranno esportate - come variabili d'ambiente all'avvio della compilazione, consentendo ai - passaggi successivi della configurazione della compilazione (come le - istruzioni di compilazione) di accedere a tali valori, ad esempio utilizzando - la sintassi ${NOME_PARAMETRO} (o %NOME_PARAMETRO% su - Windows). -
- Ciò implica anche che ogni parametro definito qui debba avere un - Nome univoco. + Ogni parametro ha un + Nome + e qualche tipo di + Valore + che dipende dal tipo del parametro. Queste coppie nome-valore saranno + esportate come variabili d'ambiente all'avvio della compilazione, + consentendo ai passaggi successivi della configurazione della compilazione + (come le istruzioni di compilazione) di accedere a tali valori, ad esempio + utilizzando la sintassi + ${NOME_PARAMETRO} + (o + %NOME_PARAMETRO% + su Windows). +
+ Ciò implica anche che ogni parametro definito qui debba avere un + Nome + univoco. +

+

- Quando un progetto è parametrizzato, il collegamento Compila ora - usuale sarà sostituito da un collegamento Compila con parametri dove - agli utenti verrà chiesto di specificare i valori per ognuno dei parametri - definiti. Se questi scelgono di non immettere nulla, la compilazione verrà - avviata con il valore predefinito per ogni parametro. + Quando un progetto è parametrizzato, il collegamento + Compila ora + usuale sarà sostituito da un collegamento + Compila con parametri + dove agli utenti verrà chiesto di specificare i valori per ognuno dei + parametri definiti. Se questi scelgono di non immettere nulla, la + compilazione verrà avviata con il valore predefinito per ogni parametro. +

+

- Se una compilazione è avviata automaticamente, ad esempio se è avviata da - un trigger del sistema di gestione del codice sorgente, saranno utilizzati i - valori predefiniti per ogni parametro. + Se una compilazione è avviata automaticamente, ad esempio se è avviata da un + trigger del sistema di gestione del codice sorgente, saranno utilizzati i + valori predefiniti per ogni parametro. +

+

- Quando una compilazione parametrizzata è in coda, i tentativi di avvio di - un'altra compilazione dello stesso progetto avranno successo solo se i valori - dei parametri sono diversi, o se l'opzione Esegui compilazioni concorrenti - se necessario è abilitata. + Quando una compilazione parametrizzata è in coda, i tentativi di avvio di + un'altra compilazione dello stesso progetto avranno successo solo se i + valori dei parametri sono diversi, o se l'opzione + Esegui compilazioni concorrenti se necessario + è abilitata. +

+

- Si veda la documentazione sulle compilazioni parametrizzate per - ulteriori informazioni su questa funzionalità. + Si veda la + + documentazione sulle compilazioni parametrizzate + + per ulteriori informazioni su questa funzionalità. +

diff --git a/core/src/main/resources/hudson/model/ParametersDefinitionProperty/help_ja.html b/core/src/main/resources/hudson/model/ParametersDefinitionProperty/help_ja.html index ba083784fd..fad8bf9982 100644 --- a/core/src/main/resources/hudson/model/ParametersDefinitionProperty/help_ja.html +++ b/core/src/main/resources/hudson/model/ParametersDefinitionProperty/help_ja.html @@ -1,11 +1,18 @@
- Jenkinsを様々な自動化に使用していると、ビルドの"パラメータ化" - ビルドプロセスで使用する値をユーザーが入力する - - が便利なこともあります。例えば、ユーザーがテスト対象のバイナリー形式のZIPファイルを登録する、 - といったテストジョブを設定することもあるでしょう。 + Jenkinsを様々な自動化に使用していると、ビルドの"パラメータ化" - + ビルドプロセスで使用する値をユーザーが入力する - + が便利なこともあります。例えば、ユーザーがテスト対象のバイナリー形式のZIPファイルを登録する、 + といったテストジョブを設定することもあるでしょう。 -

+

ここでは、ビルドが必要とするパラメータを設定します。パラメータは名前で識別するので、異なる名前を使用すれば複数のパラメータを使用できます。 +

-

- この機能の詳細については、Wikiの項目を参照してください。 +

+ この機能の詳細については、 + + Wikiの項目 + + を参照してください。 +

diff --git a/core/src/main/resources/hudson/model/ParametersDefinitionProperty/help_tr.html b/core/src/main/resources/hudson/model/ParametersDefinitionProperty/help_tr.html index 4451919d0f..be7598673e 100644 --- a/core/src/main/resources/hudson/model/ParametersDefinitionProperty/help_tr.html +++ b/core/src/main/resources/hudson/model/ParametersDefinitionProperty/help_tr.html @@ -1,14 +1,21 @@
- When you are using Jenkins for various automations, it's sometimes convenient - to be able to "parameterize" a build, by requiring a set of user inputs to - be made available to the build process. For example, you might be setting up - an on-demand test job, where the user can submit a zip file of the binaries to be tested. + When you are using Jenkins for various automations, it's sometimes convenient + to be able to "parameterize" a build, by requiring a set of user inputs to be + made available to the build process. For example, you might be setting up an + on-demand test job, where the user can submit a zip file of the binaries to be + tested. -

- This section configures what parameters your build takes. Parameters are distinguished - by their names, and so you can have multiple parameters provided that they have different names. +

+ This section configures what parameters your build takes. Parameters are + distinguished by their names, and so you can have multiple parameters + provided that they have different names. +

-

- See the Jenkins site +

+ See + + the Jenkins site + for more discussions about this feature. +

diff --git a/core/src/main/resources/hudson/model/ParametersDefinitionProperty/help_zh_TW.html b/core/src/main/resources/hudson/model/ParametersDefinitionProperty/help_zh_TW.html index c265951d63..f02bfbaf4d 100644 --- a/core/src/main/resources/hudson/model/ParametersDefinitionProperty/help_zh_TW.html +++ b/core/src/main/resources/hudson/model/ParametersDefinitionProperty/help_zh_TW.html @@ -1,12 +1,18 @@
- 當您用 Jenkins 自動化各種流程時，如果能將建置「自動化」會方便許多，要求使用者輸入參數，並帶到建置過程裡。 - 例如，您可以設一個依需求測試的作業，要使用者將待測試的檔案壓縮起來上傳。 + 當您用 Jenkins + 自動化各種流程時，如果能將建置「自動化」會方便許多，要求使用者輸入參數，並帶到建置過程裡。 + 例如，您可以設一個依需求測試的作業，要使用者將待測試的檔案壓縮起來上傳。 -

+

這一區可以讓您設定建置時要帶的參數。 參數之間是以名稱來區隔，所以如果您要用到多個參數，請指定不同的名稱。 +

-

- 請參考這篇 Wiki - 條目有關本功能的更多討論。 +

+ 請參考 + + 這篇 Wiki 條目 + + 有關本功能的更多討論。 +

diff --git a/core/src/main/resources/hudson/model/PasswordParameterDefinition/help.html b/core/src/main/resources/hudson/model/PasswordParameterDefinition/help.html index e78469f695..e14f484a96 100644 --- a/core/src/main/resources/hudson/model/PasswordParameterDefinition/help.html +++ b/core/src/main/resources/hudson/model/PasswordParameterDefinition/help.html @@ -1,5 +1,6 @@
- Pass a password to your build. - The password entered here is made available to the build in plain text as an environment variable like a string parameter would be. - The value will be stored encrypted on the Jenkins controller, similar to passwords in Jenkins configuration. -
\ No newline at end of file + Pass a password to your build. The password entered here is made available to + the build in plain text as an environment variable like a string parameter + would be. The value will be stored encrypted on the Jenkins controller, + similar to passwords in Jenkins configuration. + diff --git a/core/src/main/resources/hudson/model/PasswordParameterDefinition/help_it.html b/core/src/main/resources/hudson/model/PasswordParameterDefinition/help_it.html index 51638b0358..50f651cca7 100644 --- a/core/src/main/resources/hudson/model/PasswordParameterDefinition/help_it.html +++ b/core/src/main/resources/hudson/model/PasswordParameterDefinition/help_it.html @@ -1,7 +1,7 @@
- Fornire una password per la compilazione. - La password immessa qui sarà resa disponibile per la compilazione come - variabile d'ambiente in chiaro, come accadrebbe per un parametro stringa. - Il valore sarà salvato in forma crittografata sul master Jenkins, - analogamente alle password nella configurazione di Jenkins. + Fornire una password per la compilazione. La password immessa qui sarà resa + disponibile per la compilazione come variabile d'ambiente in chiaro, come + accadrebbe per un parametro stringa. Il valore sarà salvato in forma + crittografata sul master Jenkins, analogamente alle password nella + configurazione di Jenkins.
diff --git a/core/src/main/resources/hudson/model/Slave/help-remoteFS.html b/core/src/main/resources/hudson/model/Slave/help-remoteFS.html index ca9aa4bfce..5e4381c4a9 100644 --- a/core/src/main/resources/hudson/model/Slave/help-remoteFS.html +++ b/core/src/main/resources/hudson/model/Slave/help-remoteFS.html @@ -1,34 +1,49 @@

- An agent needs to have a directory dedicated to Jenkins. Specify - the path to this directory on the agent. It is best to use - an absolute path, such as /var/jenkins or c:\jenkins. - This should be a path local to the agent machine. There is no need for - this path to be visible from the controller. + An agent needs to have a directory dedicated to Jenkins. Specify the path to + this directory on the agent. It is best to use an absolute path, such as + /var/jenkins + or + c:\jenkins + . This should be a path local to the agent machine. There is no need for + this path to be visible from the controller. +

+

- Agents do not maintain important data; all job configurations, build logs and - artifacts are stored on the controller, so it would be possible to use a temporary - directory as the agent root directory. -
- However, by giving an agent a directory that is not deleted after a machine - reboot, for example, the agent can cache data such as tool installations, or - build workspaces. This prevents unnecessary downloading of tools, or checking - out source code again when builds start to run on this agent again after a - reboot. + Agents do not maintain important data; all job configurations, build logs + and artifacts are stored on the controller, so it would be possible to use a + temporary directory as the agent root directory. +
+ However, by giving an agent a directory that is not deleted after a machine + reboot, for example, the agent can cache data such as tool installations, or + build workspaces. This prevents unnecessary downloading of tools, or + checking out source code again when builds start to run on this agent again + after a reboot. +

+

- If you use a relative path, such as ./jenkins-agent, the path will be - relative to the working directory provided by the Launch method. + If you use a relative path, such as + ./jenkins-agent + , the path will be relative to the working directory provided by the + Launch method + . +

+
    -
  • For launchers where Jenkins controls starting the agent process, such - as SSH, the current working directory will typically be consistent, - e.g. the user's home directory.
    • -
  • For launchers where Jenkins has no control over starting the agent process, - such as inbound agents launched from the command line, - the current working directory may change between - launches of the agent and use of a relative path may prove problematic. -
    - The principal issue encountered when using relative paths with inbound launchers - is the proliferation of stale workspaces and tool installation - on the agent machine. This can cause disk space issues.
    • +
  • + For launchers where Jenkins controls starting the agent process, such as + SSH, the current working directory will typically be consistent, e.g. the + user's home directory. +
    • +
  • + For launchers where Jenkins has no control over starting the agent + process, such as inbound agents launched from the command line, the + current working directory may change between launches of the agent and use + of a relative path may prove problematic. +
    + The principal issue encountered when using relative paths with inbound + launchers is the proliferation of stale workspaces and tool installation + on the agent machine. This can cause disk space issues. +
diff --git a/core/src/main/resources/hudson/model/Slave/help-remoteFS_bg.html b/core/src/main/resources/hudson/model/Slave/help-remoteFS_bg.html index 9135d16180..88a4c5a540 100644 --- a/core/src/main/resources/hudson/model/Slave/help-remoteFS_bg.html +++ b/core/src/main/resources/hudson/model/Slave/help-remoteFS_bg.html @@ -1,34 +1,50 @@

- Компютърът за изграждания трябва да има директория, която да се ползва - само от Jenkins. Укажете пътя до директорията. Най-добре ползвайте - абсолютен път като /var/jenkins или c:\jenkins. - Това е локален път — както се вижда на машината за изграждания. Няма - нужда пътят да се вижда от командната машина. + Компютърът за изграждания трябва да има директория, която да се ползва само + от Jenkins. Укажете пътя до директорията. Най-добре ползвайте абсолютен път + като + /var/jenkins + или + c:\jenkins + . Това е локален път — както се вижда на машината за изграждания. Няма нужда + пътят да се вижда от командната машина. +

+

- Изграждащите машини не съдържат важни данни — всички настройки по задачите, - журналите от изгражданията както и артефактите се държат на компания компютър, - затова е напълно допустимо да се ползва временна директория като основна на - подчинените машини. -
- Има полза директорията да не е временна, защото след рестартиране на машината - тя остава и може да държи кеширани инсталациите на инструменти, или местата - за изграждания. Това минимизира повтарящите се изтегляния на инструменти - или ресурси от системите за контрол на версии при стартирането на ново - изграждане след рестартиране. + Изграждащите машини не съдържат важни данни — всички настройки по задачите, + журналите от изгражданията както и артефактите се държат на компания + компютър, затова е напълно допустимо да се ползва временна директория като + основна на подчинените машини. +
+ Има полза директорията да не е временна, защото след рестартиране на + машината тя остава и може да държи кеширани инсталациите на инструменти, или + местата за изграждания. Това минимизира повтарящите се изтегляния на + инструменти или ресурси от системите за контрол на версии при стартирането + на ново изграждане след рестартиране. +

+

- Ако използвате относителен път като ./jenkins-agent, пътят се определя - спрямо работната директория указана в Начина за стартиране. + Ако използвате относителен път като + ./jenkins-agent + , пътят се определя спрямо работната директория указана в + Начина за стартиране + . +

+
    -
  • При стартиранията, при които Jenkins управлява пускането на агента, - като например SSH, текущата директория най-често е една и съща, примерно - домашната директория на потребителя.
    • -
  • При стартиранията, при които Jenkins не ги управлява, като JNLP през - командния ред или връзка за уеб браузъра, текущата директория може да се - променя при всяко стартиране. В този случай ползването на относителен път - може да доведе до проблеми. -
    - Най-често това са остарели работни места, инсталации на инструменти, което - води до свършване на свободното дисково пространство.
    • +
  • + При стартиранията, при които Jenkins управлява пускането на агента, като + например SSH, текущата директория най-често е една и съща, примерно + домашната директория на потребителя. +
    • +
  • + При стартиранията, при които Jenkins не ги управлява, като JNLP през + командния ред или връзка за уеб браузъра, текущата директория може да се + променя при всяко стартиране. В този случай ползването на относителен път + може да доведе до проблеми. +
    + Най-често това са остарели работни места, инсталации на инструменти, което + води до свършване на свободното дисково пространство. +
diff --git a/core/src/main/resources/hudson/model/Slave/help-remoteFS_fr.html b/core/src/main/resources/hudson/model/Slave/help-remoteFS_fr.html index 10588de692..445870ba27 100644 --- a/core/src/main/resources/hudson/model/Slave/help-remoteFS_fr.html +++ b/core/src/main/resources/hudson/model/Slave/help-remoteFS_fr.html @@ -1,16 +1,17 @@ 

- Un agent a besoin d'un répertoire dédié à Jenkins. Spécifiez ici le - chemin absolu (local à l'agent) vers le répertoire de travail sur l'agent, par exemple - '/var/jenkins' ou 'c:\jenkins'. Le chemin doit être local à la machine - agent. En règle générale, il n'est pas nécessaire que ce chemin soit - visible depuis le contrôleur. + Un agent a besoin d'un répertoire dédié à Jenkins. Spécifiez ici le chemin + absolu (local à l'agent) vers le répertoire de travail sur l'agent, par + exemple '/var/jenkins' ou 'c:\jenkins'. Le chemin doit être local à la + machine agent. En règle générale, il n'est pas nécessaire que ce chemin soit + visible depuis le contrôleur. +

- Les agents ne conservent pas de données importantes (autres que les - répertoires de travail des derniers builds des projets); vous pouvez donc - positionner le répertoire du travail de l'agent dans un répertoire - temporaire. - Le seul défaut de ce choix est que vous perdrez le dernier workspace à - jour si la machine agent est éteinte. + Les agents ne conservent pas de données importantes (autres que les + répertoires de travail des derniers builds des projets); vous pouvez donc + positionner le répertoire du travail de l'agent dans un répertoire + temporaire. Le seul défaut de ce choix est que vous perdrez le dernier + workspace à jour si la machine agent est éteinte. +

diff --git a/core/src/main/resources/hudson/model/Slave/help-remoteFS_it.html b/core/src/main/resources/hudson/model/Slave/help-remoteFS_it.html index 05a4a4ebcc..15d72168c2 100644 --- a/core/src/main/resources/hudson/model/Slave/help-remoteFS_it.html +++ b/core/src/main/resources/hudson/model/Slave/help-remoteFS_it.html @@ -1,39 +1,54 @@

- Un agente deve avere una directory dedicata a Jenkins. Specificare il - percorso a questa directory sull'agente. È meglio utilizzare un percorso - assoluto, come /var/jenkins o c:\jenkins. - Questo percorso deve essere locale al computer agente. Non è necessario - che questo percorso sia visibile dal master. + Un agente deve avere una directory dedicata a Jenkins. Specificare il + percorso a questa directory sull'agente. È meglio utilizzare un percorso + assoluto, come + /var/jenkins + o + c:\jenkins + . Questo percorso deve essere locale al computer agente. Non è necessario + che questo percorso sia visibile dal master. +

+

- Gli agenti non mantengono dati importanti; tutte le configurazioni dei - processi, i log delle compilazioni e gli artefatti sono salvati sul master, - per cui sarebbe possibile utilizzare una directory temporanea come directory - radice dell'agente. -
- Tuttavia, fornendo a un agente una directory che non viene eliminata al - riavvio del computer, ad esempio, l'agente può eseguire il caching di dati - come installazioni di strumenti o spazi di lavoro delle compilazioni. Ciò - impedisce il download non necessario di strumenti o evita la necessità di - eseguire nuovamente il checkout del codice sorgente quando delle compilazioni - riprendono ad essere eseguite dopo un riavvio. + Gli agenti non mantengono dati importanti; tutte le configurazioni dei + processi, i log delle compilazioni e gli artefatti sono salvati sul master, + per cui sarebbe possibile utilizzare una directory temporanea come directory + radice dell'agente. +
+ Tuttavia, fornendo a un agente una directory che non viene eliminata al + riavvio del computer, ad esempio, l'agente può eseguire il caching di dati + come installazioni di strumenti o spazi di lavoro delle compilazioni. Ciò + impedisce il download non necessario di strumenti o evita la necessità di + eseguire nuovamente il checkout del codice sorgente quando delle + compilazioni riprendono ad essere eseguite dopo un riavvio. +

+

- Se si utilizza un percorso relativo, come ./jenkins-agent, il - percorso sarà relativo alla directory di lavoro fornita dal Metodo di - avvio. + Se si utilizza un percorso relativo, come + ./jenkins-agent + , il percorso sarà relativo alla directory di lavoro fornita dal + Metodo di avvio + . +

+
    -
  • Per le utilità di avvio per cui Jenkins controlla l'avvio del processo - agente, come SSH, tipicamente la directory di lavoro corrente sarà - consistente, ad es. la directory home dell'utente.
    • -
  • Per le utilità di avvio per cui Jenkins non ha controllo sull'avvio del - processo agente, come agenti che comunicano in ingresso avviati dalla riga - di comando, la directory di lavoro corrente potrebbe variare da un avvio - all'altro dell'agente e l'utilizzo di un percorso relativo potrebbe - rivelarsi problematico. -
    - Il problema principale riscontrato con l'utilizzo dei percorsi relativi con - gli agenti che comunicano in ingresso è la proliferazione di spazi di lavoro - e di installazioni di strumenti non aggiornati sul computer dell'agente. - Ciò può causare problemi di spazio disponibile su disco.
    • +
  • + Per le utilità di avvio per cui Jenkins controlla l'avvio del processo + agente, come SSH, tipicamente la directory di lavoro corrente sarà + consistente, ad es. la directory home dell'utente. +
    • +
  • + Per le utilità di avvio per cui Jenkins non ha controllo sull'avvio del + processo agente, come agenti che comunicano in ingresso avviati dalla riga + di comando, la directory di lavoro corrente potrebbe variare da un avvio + all'altro dell'agente e l'utilizzo di un percorso relativo potrebbe + rivelarsi problematico. +
    + Il problema principale riscontrato con l'utilizzo dei percorsi relativi + con gli agenti che comunicano in ingresso è la proliferazione di spazi di + lavoro e di installazioni di strumenti non aggiornati sul computer + dell'agente. Ciò può causare problemi di spazio disponibile su disco. +
diff --git a/core/src/main/resources/hudson/model/Slave/help-remoteFS_ja.html b/core/src/main/resources/hudson/model/Slave/help-remoteFS_ja.html index 792e54a2ef..595d86afb7 100644 --- a/core/src/main/resources/hudson/model/Slave/help-remoteFS_ja.html +++ b/core/src/main/resources/hudson/model/Slave/help-remoteFS_ja.html @@ -1,11 +1,13 @@

- エージェントにはJenkins用のディレクトリが必要です。 - '/var/jenkins'や'c:\jenkins'のような、エージェントのワークディレクトリの絶対パスを指定します。 - このパスは、エージェントでのローカルなパスです。マスターから見える必要はありません。 + エージェントにはJenkins用のディレクトリが必要です。 + '/var/jenkins'や'c:\jenkins'のような、エージェントのワークディレクトリの絶対パスを指定します。 + このパスは、エージェントでのローカルなパスです。マスターから見える必要はありません。 +

- エージェントは重要なデータ(直前にビルドしたプロジェクトのワークスペースを除いて)を保持しないので、 - エージェントのワークスペースをテンポラリディレクトリに設定できます。 - 唯一の弱点は、エージェントが落ちると最新のワークスペースを失うことです。 + エージェントは重要なデータ(直前にビルドしたプロジェクトのワークスペースを除いて)を保持しないので、 + エージェントのワークスペースをテンポラリディレクトリに設定できます。 + 唯一の弱点は、エージェントが落ちると最新のワークスペースを失うことです。 +

diff --git a/core/src/main/resources/hudson/model/Slave/help-remoteFS_ru.html b/core/src/main/resources/hudson/model/Slave/help-remoteFS_ru.html index 18f5b1f7f6..c97323beac 100644 --- a/core/src/main/resources/hudson/model/Slave/help-remoteFS_ru.html +++ b/core/src/main/resources/hudson/model/Slave/help-remoteFS_ru.html @@ -1,14 +1,14 @@
- +

- Подчиненный узел должен иметь директорию выделенную для Jenkins. - Укажите полный путь к этой директории, например - '/export/home/jenkins'. + Подчиненный узел должен иметь директорию выделенную для Jenkins. Укажите + полный путь к этой директории, например '/export/home/jenkins'. +

- Подчиненные узлы не содержат важных данный (чего-то кроме директорий - сборки последних собранных проектов), так что вы можете назначить - в качестве такой директории любую временную. Единственное негативное - последствие - вы можете потерять последнюю версию сборочной директории, - если узел выключится. + Подчиненные узлы не содержат важных данный (чего-то кроме директорий сборки + последних собранных проектов), так что вы можете назначить в качестве такой + директории любую временную. Единственное негативное последствие - вы можете + потерять последнюю версию сборочной директории, если узел выключится. +

diff --git a/core/src/main/resources/hudson/model/StringParameterDefinition/help-trim.html b/core/src/main/resources/hudson/model/StringParameterDefinition/help-trim.html index 3fe1272d80..d06e5bd0b4 100644 --- a/core/src/main/resources/hudson/model/StringParameterDefinition/help-trim.html +++ b/core/src/main/resources/hudson/model/StringParameterDefinition/help-trim.html @@ -1,3 +1 @@ -
- Strip whitespace from the beginning and end of the string. -
+
Strip whitespace from the beginning and end of the string.
diff --git a/core/src/main/resources/hudson/model/StringParameterDefinition/help-trim_it.html b/core/src/main/resources/hudson/model/StringParameterDefinition/help-trim_it.html index bd89b7f97e..6997a6ab5f 100644 --- a/core/src/main/resources/hudson/model/StringParameterDefinition/help-trim_it.html +++ b/core/src/main/resources/hudson/model/StringParameterDefinition/help-trim_it.html @@ -1,3 +1 @@ -
- Elimina gli spazi bianchi all'inizio e alla fine della stringa. -
+
Elimina gli spazi bianchi all'inizio e alla fine della stringa.
diff --git a/core/src/main/resources/hudson/model/TimeZoneProperty/help-timeZoneName.html b/core/src/main/resources/hudson/model/TimeZoneProperty/help-timeZoneName.html index b6b91671a4..4bb418b353 100644 --- a/core/src/main/resources/hudson/model/TimeZoneProperty/help-timeZoneName.html +++ b/core/src/main/resources/hudson/model/TimeZoneProperty/help-timeZoneName.html @@ -1,3 +1,3 @@
- Specify user defined time zone for displaying time rather than system default. + Specify user defined time zone for displaying time rather than system default.
diff --git a/core/src/main/resources/hudson/model/TimeZoneProperty/help-timeZoneName_ja.html b/core/src/main/resources/hudson/model/TimeZoneProperty/help-timeZoneName_ja.html index 64f2156603..92d9ed7db0 100644 --- a/core/src/main/resources/hudson/model/TimeZoneProperty/help-timeZoneName_ja.html +++ b/core/src/main/resources/hudson/model/TimeZoneProperty/help-timeZoneName_ja.html @@ -1,3 +1,3 @@
- システムデフォルトの代わりに、ユーザーが指定したタイムゾーンで時刻を表示します。 + システムデフォルトの代わりに、ユーザーが指定したタイムゾーンで時刻を表示します。
diff --git a/core/src/main/resources/hudson/model/UpdateCenter/update-center.js b/core/src/main/resources/hudson/model/UpdateCenter/update-center.js index acb0e8ee55..d90b1c7fb2 100644 --- a/core/src/main/resources/hudson/model/UpdateCenter/update-center.js +++ b/core/src/main/resources/hudson/model/UpdateCenter/update-center.js @@ -1,38 +1,38 @@ function submitScheduleForm(el) { - var form = document.getElementById("scheduleRestart"); - form.action = el.checked ? "safeRestart" : "cancelRestart"; - crumb.appendToForm(form); - form.submit(); + var form = document.getElementById("scheduleRestart"); + form.action = el.checked ? "safeRestart" : "cancelRestart"; + crumb.appendToForm(form); + form.submit(); } function refresh() { - window.setTimeout(function() { - new Ajax.Request("./body", { - onSuccess: function(rsp) { - var div = document.createElement('div'); - div.innerHTML = rsp.responseText; + window.setTimeout(function () { + new Ajax.Request("./body", { + onSuccess: function (rsp) { + var div = document.createElement("div"); + div.innerHTML = rsp.responseText; - var rows = div.children[0].rows; - for(var i=0; i x; x++) { - var e = data[x]; - var id = 'person-' + e.id; - var r = document.getElementById(id); - if (r == null) { - r = document.createElement('tr'); - r.id = id; - p.appendChild(r); - } else { - while (r.firstChild) { - r.removeChild(r.firstChild); - } - } - - var d = document.createElement('td'); - var wrapper = document.createElement('div'); - wrapper.className = 'jenkins-table__cell__button-wrapper'; - d.className = 'jenkins-table__cell--tight jenkins-table__icon'; - var icon = document.getElementById('person-circle') - wrapper.innerHTML = icon.children[0].outerHTML; - d.appendChild(wrapper); - r.appendChild(d); + var p = document.getElementById("people"); + p.show(); + var rootURL = document.head.getAttribute("data-rooturl"); + for (var x = 0; data.length > x; x++) { + var e = data[x]; + var id = "person-" + e.id; + var r = document.getElementById(id); + if (r == null) { + r = document.createElement("tr"); + r.id = id; + p.appendChild(r); + } else { + while (r.firstChild) { + r.removeChild(r.firstChild); + } + } - d = document.createElement('td'); - var a = document.createElement('a'); - a.href = rootURL + "/" + e.url; - a.className = "jenkins-table__link" - a.appendChild(document.createTextNode(e.id)); - d.appendChild(a); - r.appendChild(d); + var d = document.createElement("td"); + var wrapper = document.createElement("div"); + wrapper.className = "jenkins-table__cell__button-wrapper"; + d.className = "jenkins-table__cell--tight jenkins-table__icon"; + var icon = document.getElementById("person-circle"); + wrapper.innerHTML = icon.children[0].outerHTML; + d.appendChild(wrapper); + r.appendChild(d); - d = document.createElement('td'); - d.appendChild(document.createTextNode(e.fullName)); - r.appendChild(d); + d = document.createElement("td"); + var a = document.createElement("a"); + a.href = rootURL + "/" + e.url; + a.className = "jenkins-table__link"; + a.appendChild(document.createTextNode(e.id)); + d.appendChild(a); + r.appendChild(d); - d = document.createElement('td'); - d.setAttribute('data', e.timeSortKey); - d.appendChild(document.createTextNode(e.lastChangeTimeString)); - r.appendChild(d); + d = document.createElement("td"); + d.appendChild(document.createTextNode(e.fullName)); + r.appendChild(d); - d = document.createElement('td'); - if (e.projectUrl != null) { - a = document.createElement('a'); - a.href = rootURL + "/" + e.projectUrl; - a.className = 'jenkins-table__link model-link inside'; - a.appendChild(document.createTextNode(e.projectFullDisplayName)); - d.appendChild(a); - } - r.appendChild(d); + d = document.createElement("td"); + d.setAttribute("data", e.timeSortKey); + d.appendChild(document.createTextNode(e.lastChangeTimeString)); + r.appendChild(d); - ts_refresh(p); + d = document.createElement("td"); + if (e.projectUrl != null) { + a = document.createElement("a"); + a.href = rootURL + "/" + e.projectUrl; + a.className = "jenkins-table__link model-link inside"; + a.appendChild(document.createTextNode(e.projectFullDisplayName)); + d.appendChild(a); } + r.appendChild(d); + + ts_refresh(p); + } } diff --git a/core/src/main/resources/hudson/node_monitors/AbstractDiskSpaceMonitor/help-freeSpaceThreshold.html b/core/src/main/resources/hudson/node_monitors/AbstractDiskSpaceMonitor/help-freeSpaceThreshold.html index 3bc40d8cc7..818a9e10ad 100644 --- a/core/src/main/resources/hudson/node_monitors/AbstractDiskSpaceMonitor/help-freeSpaceThreshold.html +++ b/core/src/main/resources/hudson/node_monitors/AbstractDiskSpaceMonitor/help-freeSpaceThreshold.html @@ -1,5 +1,6 @@
- This option configures the amount of minimum amount of free disk space - desired for an agent's proper operation, such as "1.5GB", "100KB", etc. - If an agent is found to have less free disk space than this amount, it will be marked offline. -
\ No newline at end of file + This option configures the amount of minimum amount of free disk space desired + for an agent's proper operation, such as "1.5GB", "100KB", etc. If an agent is + found to have less free disk space than this amount, it will be marked + offline. + diff --git a/core/src/main/resources/hudson/node_monitors/AbstractDiskSpaceMonitor/help-freeSpaceThreshold_bg.html b/core/src/main/resources/hudson/node_monitors/AbstractDiskSpaceMonitor/help-freeSpaceThreshold_bg.html index 990f142db1..72d21fe446 100644 --- a/core/src/main/resources/hudson/node_monitors/AbstractDiskSpaceMonitor/help-freeSpaceThreshold_bg.html +++ b/core/src/main/resources/hudson/node_monitors/AbstractDiskSpaceMonitor/help-freeSpaceThreshold_bg.html @@ -1,7 +1,6 @@
- Тази опция указва минималното необходимо свободно пространство на диска, за - да се осигури правилна работа на Jenkins на машината. Примерни стойности са: - „1.5GB“, „100KB“ и т.н. - Ако свободното място на машината падне под тази стойност, тя ще бъде - маркирана извън линия. + Тази опция указва минималното необходимо свободно пространство на диска, за да + се осигури правилна работа на Jenkins на машината. Примерни стойности са: + „1.5GB“, „100KB“ и т.н. Ако свободното място на машината падне под тази + стойност, тя ще бъде маркирана извън линия.
diff --git a/core/src/main/resources/hudson/node_monitors/AbstractDiskSpaceMonitor/help-freeSpaceThreshold_it.html b/core/src/main/resources/hudson/node_monitors/AbstractDiskSpaceMonitor/help-freeSpaceThreshold_it.html index 746e24cf10..88a79c434b 100644 --- a/core/src/main/resources/hudson/node_monitors/AbstractDiskSpaceMonitor/help-freeSpaceThreshold_it.html +++ b/core/src/main/resources/hudson/node_monitors/AbstractDiskSpaceMonitor/help-freeSpaceThreshold_it.html @@ -1,7 +1,7 @@
- Quest'opzione configura il valore minimo di spazio libero su disco - desiderato affinché un agente funzioni correttamente (ad esempio: - "1.5GB", "100KB", ecc.). Se viene rilevato che un agente ha una quantità - di spazio libero su disco inferiore a questo valore, questo verrà - contrassegnato come non in linea. + Quest'opzione configura il valore minimo di spazio libero su disco desiderato + affinché un agente funzioni correttamente (ad esempio: "1.5GB", "100KB", + ecc.). Se viene rilevato che un agente ha una quantità di spazio libero su + disco inferiore a questo valore, questo verrà contrassegnato come non in + linea.
diff --git a/core/src/main/resources/hudson/node_monitors/AbstractDiskSpaceMonitor/help-freeSpaceThreshold_ja.html b/core/src/main/resources/hudson/node_monitors/AbstractDiskSpaceMonitor/help-freeSpaceThreshold_ja.html index 5848ee95cb..7513f5b2d1 100644 --- a/core/src/main/resources/hudson/node_monitors/AbstractDiskSpaceMonitor/help-freeSpaceThreshold_ja.html +++ b/core/src/main/resources/hudson/node_monitors/AbstractDiskSpaceMonitor/help-freeSpaceThreshold_ja.html @@ -1,4 +1,5 @@
- このオプションは、エージェントが正常動作するために最低限必要な空きディスク容量を設定します(例 "1.5GB"、"100KB"など)。 - エージェントの空き容量がこの値より少ない場合、オフラインになります。 -
\ No newline at end of file + このオプションは、エージェントが正常動作するために最低限必要な空きディスク容量を設定します(例 + "1.5GB"、"100KB"など)。 + エージェントの空き容量がこの値より少ない場合、オフラインになります。 + diff --git a/core/src/main/resources/hudson/node_monitors/ArchitectureMonitor/help.html b/core/src/main/resources/hudson/node_monitors/ArchitectureMonitor/help.html index c25399638b..23efe3bdef 100644 --- a/core/src/main/resources/hudson/node_monitors/ArchitectureMonitor/help.html +++ b/core/src/main/resources/hudson/node_monitors/ArchitectureMonitor/help.html @@ -1,3 +1,4 @@
- This monitor just shows the architecture of the agent for your information. It never marks the agent offline. -
\ No newline at end of file + This monitor just shows the architecture of the agent for your information. It + never marks the agent offline. + diff --git a/core/src/main/resources/hudson/node_monitors/ArchitectureMonitor/help_bg.html b/core/src/main/resources/hudson/node_monitors/ArchitectureMonitor/help_bg.html index a48bff0cc4..8d147a70b4 100644 --- a/core/src/main/resources/hudson/node_monitors/ArchitectureMonitor/help_bg.html +++ b/core/src/main/resources/hudson/node_monitors/ArchitectureMonitor/help_bg.html @@ -1,4 +1,4 @@
- Този датчик просто извежда архитектурата на агента. Той никога не указва - агентът да е извън линия. -
\ No newline at end of file + Този датчик просто извежда архитектурата на агента. Той никога не указва + агентът да е извън линия. + diff --git a/core/src/main/resources/hudson/node_monitors/ArchitectureMonitor/help_it.html b/core/src/main/resources/hudson/node_monitors/ArchitectureMonitor/help_it.html index 84aa0eb92d..61756b5165 100644 --- a/core/src/main/resources/hudson/node_monitors/ArchitectureMonitor/help_it.html +++ b/core/src/main/resources/hudson/node_monitors/ArchitectureMonitor/help_it.html @@ -1,4 +1,4 @@
- Questo monitor visualizza semplicemente l'architettura dell'agente a - scopo informativo. Non contrassegna mai l'agente come non in linea. + Questo monitor visualizza semplicemente l'architettura dell'agente a scopo + informativo. Non contrassegna mai l'agente come non in linea.
diff --git a/core/src/main/resources/hudson/node_monitors/ArchitectureMonitor/help_ja.html b/core/src/main/resources/hudson/node_monitors/ArchitectureMonitor/help_ja.html index f4ca37e4df..a50fa1e7e3 100644 --- a/core/src/main/resources/hudson/node_monitors/ArchitectureMonitor/help_ja.html +++ b/core/src/main/resources/hudson/node_monitors/ArchitectureMonitor/help_ja.html @@ -1,3 +1,3 @@
- 情報として、エージェントのアーキテクチャを表示するだけで、そのエージェントをオフラインにすることはありません。 -
\ No newline at end of file + 情報として、エージェントのアーキテクチャを表示するだけで、そのエージェントをオフラインにすることはありません。 + diff --git a/core/src/main/resources/hudson/node_monitors/ClockMonitor/help.html b/core/src/main/resources/hudson/node_monitors/ClockMonitor/help.html index 4311cc9b4f..f9a1a868b1 100644 --- a/core/src/main/resources/hudson/node_monitors/ClockMonitor/help.html +++ b/core/src/main/resources/hudson/node_monitors/ClockMonitor/help.html @@ -1,9 +1,9 @@
- This monitors the clock difference between the controller and nodes. - While Jenkins itself is generally capable of tolerating clock differences between systems, - version control activities and distributed file access (such as NFS, Windows file shares) - tend to have strange problems when systems involved have different clocks. + This monitors the clock difference between the controller and nodes. While + Jenkins itself is generally capable of tolerating clock differences between + systems, version control activities and distributed file access (such as NFS, + Windows file shares) tend to have strange problems when systems involved have + different clocks. -

- To keep clocks in sync, refer to NTP. +

To keep clocks in sync, refer to NTP.

diff --git a/core/src/main/resources/hudson/node_monitors/ClockMonitor/help_bg.html b/core/src/main/resources/hudson/node_monitors/ClockMonitor/help_bg.html index 8e9f95e880..f817e62983 100644 --- a/core/src/main/resources/hudson/node_monitors/ClockMonitor/help_bg.html +++ b/core/src/main/resources/hudson/node_monitors/ClockMonitor/help_bg.html @@ -1,9 +1,8 @@
- Този датчик указва разликата в часовниците между водача и следващите машини. - Въпреки че Jenkins не е чувствителен към разликите в часовниците, системите - за контрол на версиите, както и отдалечените файлови системи (като NFS и - споделянето на файлове в Windows) често имат проблеми в такива ситуации. + Този датчик указва разликата в часовниците между водача и следващите машини. + Въпреки че Jenkins не е чувствителен към разликите в часовниците, системите за + контрол на версиите, както и отдалечените файлови системи (като NFS и + споделянето на файлове в Windows) често имат проблеми в такива ситуации. -

- За да синхронизирате часовниците, ползвайте примерно NTP. +

За да синхронизирате часовниците, ползвайте примерно NTP.

diff --git a/core/src/main/resources/hudson/node_monitors/ClockMonitor/help_it.html b/core/src/main/resources/hudson/node_monitors/ClockMonitor/help_it.html index a957c0c591..da64a8cfc1 100644 --- a/core/src/main/resources/hudson/node_monitors/ClockMonitor/help_it.html +++ b/core/src/main/resources/hudson/node_monitors/ClockMonitor/help_it.html @@ -1,11 +1,10 @@
- Questo modulo mantiene sotto controllo la differenza di orario tra il - master e i nodi. Mentre Jenkins stesso è in generale in grado di tollerare - differenze di orario fra i sistemi, le attività legate al controllo di - versione e all'accesso ai file distribuito (come NFS o condivisioni file - Windows) tendono a presentare problemi strani quando i sistemi coinvolti - hanno ora e data differenti. + Questo modulo mantiene sotto controllo la differenza di orario tra il master e + i nodi. Mentre Jenkins stesso è in generale in grado di tollerare differenze + di orario fra i sistemi, le attività legate al controllo di versione e + all'accesso ai file distribuito (come NFS o condivisioni file Windows) tendono + a presentare problemi strani quando i sistemi coinvolti hanno ora e data + differenti. -

- Per mantenere gli orologi sincronizzati, si faccia riferimento a NTP. +

Per mantenere gli orologi sincronizzati, si faccia riferimento a NTP.

diff --git a/core/src/main/resources/hudson/node_monitors/ClockMonitor/help_ja.html b/core/src/main/resources/hudson/node_monitors/ClockMonitor/help_ja.html index 98e9111ab7..f982aa20d4 100644 --- a/core/src/main/resources/hudson/node_monitors/ClockMonitor/help_ja.html +++ b/core/src/main/resources/hudson/node_monitors/ClockMonitor/help_ja.html @@ -1,9 +1,8 @@
- マスタとノード間のクロック誤差を監視します。 - Jenkins自身は通常システム間のクロック誤差を許容しますが、 - バージョンコントロールや分散ファイルシステムでのアクセス(NFSやWindowsでのファイル共有など）では、 - 関係するシステムにクロック誤差があると変な問題が発生する傾向があります。 + マスタとノード間のクロック誤差を監視します。 + Jenkins自身は通常システム間のクロック誤差を許容しますが、 + バージョンコントロールや分散ファイルシステムでのアクセス(NFSやWindowsでのファイル共有など）では、 + 関係するシステムにクロック誤差があると変な問題が発生する傾向があります。 -

- クロックの同期をとるには、NTPの利用を検討してください。 +

クロックの同期をとるには、NTPの利用を検討してください。

diff --git a/core/src/main/resources/hudson/node_monitors/ClockMonitor/help_zh_TW.html b/core/src/main/resources/hudson/node_monitors/ClockMonitor/help_zh_TW.html index 3341e7521f..ff8c9f95ca 100644 --- a/core/src/main/resources/hudson/node_monitors/ClockMonitor/help_zh_TW.html +++ b/core/src/main/resources/hudson/node_monitors/ClockMonitor/help_zh_TW.html @@ -1,8 +1,7 @@
- 監控 Master 與節點的時間差。 - 雖然 Jenkins 本身可以容忍系統間的時間差，但是版本管理活動及分散式檔案存取 - (例如 NFS 及 Windows 檔案共用) 在系統之間有時間差時可能會出現一些狀況。 + 監控 Master 與節點的時間差。 雖然 Jenkins + 本身可以容忍系統間的時間差，但是版本管理活動及分散式檔案存取 (例如 NFS 及 + Windows 檔案共用) 在系統之間有時間差時可能會出現一些狀況。 -

- 保持同步時間的方法，請找 "NTP"。 +

保持同步時間的方法，請找 "NTP"。

diff --git a/core/src/main/resources/hudson/node_monitors/DiskSpaceMonitor/help.html b/core/src/main/resources/hudson/node_monitors/DiskSpaceMonitor/help.html index 1b6db0303d..ace250e874 100644 --- a/core/src/main/resources/hudson/node_monitors/DiskSpaceMonitor/help.html +++ b/core/src/main/resources/hudson/node_monitors/DiskSpaceMonitor/help.html @@ -1,7 +1,11 @@
- This monitors the available disk space of $JENKINS_HOME on each agent, and if it gets below - a threshold, the agent will be marked offline. + This monitors the available disk space of + $JENKINS_HOME + on each agent, and if it gets below a threshold, the agent will be marked + offline. -

- This directory is where all your builds are performed, so if it fills up, all the builds will fail. +

+ This directory is where all your builds are performed, so if it fills up, + all the builds will fail. +

diff --git a/core/src/main/resources/hudson/node_monitors/DiskSpaceMonitor/help_bg.html b/core/src/main/resources/hudson/node_monitors/DiskSpaceMonitor/help_bg.html index ba17348d3d..8575ba41a8 100644 --- a/core/src/main/resources/hudson/node_monitors/DiskSpaceMonitor/help_bg.html +++ b/core/src/main/resources/hudson/node_monitors/DiskSpaceMonitor/help_bg.html @@ -1,9 +1,12 @@
- Този датчик указва свободното дисково пространство на файловата система, в - която е разположена директорията $JENKINS_HOME. Ако то падне под - определена стойност, машината ще бъде указана като извън линия. + Този датчик указва свободното дисково пространство на файловата система, в + която е разположена директорията + $JENKINS_HOME + . Ако то падне под определена стойност, машината ще бъде указана като извън + линия. -

- В тази директория се извършват всички изграждания. Когато се напълни, +

+ В тази директория се извършват всички изграждания. Когато се напълни, изгражданията са неуспешни. +

diff --git a/core/src/main/resources/hudson/node_monitors/DiskSpaceMonitor/help_it.html b/core/src/main/resources/hudson/node_monitors/DiskSpaceMonitor/help_it.html index 11931c4fa5..0b30bc7df3 100644 --- a/core/src/main/resources/hudson/node_monitors/DiskSpaceMonitor/help_it.html +++ b/core/src/main/resources/hudson/node_monitors/DiskSpaceMonitor/help_it.html @@ -1,9 +1,12 @@
- Questo modulo mantiene sotto controllo lo spazio su disco disponibile su - ogni agente per $JENKINS_HOME e, se diminuisce al di sotto di - una certa soglia, l'agente sarà contrassegnato come non in linea. + Questo modulo mantiene sotto controllo lo spazio su disco disponibile su ogni + agente per + $JENKINS_HOME + e, se diminuisce al di sotto di una certa soglia, l'agente sarà contrassegnato + come non in linea. -

+

Questa directory è il percorso in cui sono eseguite tutte le compilazioni, per cui, se dovesse riempirsi, tutte le compilazioni fallirebbero. +

diff --git a/core/src/main/resources/hudson/node_monitors/DiskSpaceMonitor/help_ja.html b/core/src/main/resources/hudson/node_monitors/DiskSpaceMonitor/help_ja.html index 5cdbf0b5b6..5baa36a0f0 100644 --- a/core/src/main/resources/hudson/node_monitors/DiskSpaceMonitor/help_ja.html +++ b/core/src/main/resources/hudson/node_monitors/DiskSpaceMonitor/help_ja.html @@ -1,6 +1,9 @@
- 各エージェントの$JENKINS_HOMEの利用可能なディスク容量を監視します。もし閾値を下回ったらそのエージェントはオフラインになります。 + 各エージェントの + $JENKINS_HOME + の利用可能なディスク容量を監視します。もし閾値を下回ったらそのエージェントはオフラインになります。 -

+

このディレクトリでビルドが実行されるので、いっぱいになったらビルドはすべて失敗します。 +

diff --git a/core/src/main/resources/hudson/node_monitors/ResponseTimeMonitor/help.html b/core/src/main/resources/hudson/node_monitors/ResponseTimeMonitor/help.html index 977072ab4b..ed324b07d5 100644 --- a/core/src/main/resources/hudson/node_monitors/ResponseTimeMonitor/help.html +++ b/core/src/main/resources/hudson/node_monitors/ResponseTimeMonitor/help.html @@ -1,9 +1,12 @@
- This monitors the round trip network response time from the controller to the agent, and if it - goes above a threshold repeatedly, it marks the agent offline. + This monitors the round trip network response time from the controller to the + agent, and if it goes above a threshold repeatedly, it marks the agent + offline. -

- This is useful for detecting unresponsive agents, or other network problems that clog the - communication channel. More specifically, the controller sends a no-op command to the agent, - and checks the time it takes to get back the result of this no-op command. -

\ No newline at end of file +

+ This is useful for detecting unresponsive agents, or other network problems + that clog the communication channel. More specifically, the controller sends + a no-op command to the agent, and checks the time it takes to get back the + result of this no-op command. +

+ diff --git a/core/src/main/resources/hudson/node_monitors/ResponseTimeMonitor/help_bg.html b/core/src/main/resources/hudson/node_monitors/ResponseTimeMonitor/help_bg.html index 7d4deeb108..098a5eba79 100644 --- a/core/src/main/resources/hudson/node_monitors/ResponseTimeMonitor/help_bg.html +++ b/core/src/main/resources/hudson/node_monitors/ResponseTimeMonitor/help_bg.html @@ -1,10 +1,11 @@
- Този датчик наблюдава времето за отговор на заявка по мрежата от - водещата машина към следваща. Ако мине определен праг, агентът се извежда - като извън линия. + Този датчик наблюдава времето за отговор на заявка по мрежата от водещата + машина към следваща. Ако мине определен праг, агентът се извежда като извън + линия. -

+

Това е полезно, за да се откриват агенти, които не отговарят на заявки или мрежови проблеми, като задръстване на информационния канал. Лидерът праща празна заявка към машините и замерва времето за отговор. -

\ No newline at end of file +

+ diff --git a/core/src/main/resources/hudson/node_monitors/ResponseTimeMonitor/help_it.html b/core/src/main/resources/hudson/node_monitors/ResponseTimeMonitor/help_it.html index 89b9f2854d..e4a7f06024 100644 --- a/core/src/main/resources/hudson/node_monitors/ResponseTimeMonitor/help_it.html +++ b/core/src/main/resources/hudson/node_monitors/ResponseTimeMonitor/help_it.html @@ -1,11 +1,12 @@
- Questo modulo mantiene sotto controllo il tempo di risposta di rete di - andata e ritorno dal master all'agente e, se aumenta ripetutamente al di - sopra di una certa soglia, contrassegna l'agente come non in linea. + Questo modulo mantiene sotto controllo il tempo di risposta di rete di andata + e ritorno dal master all'agente e, se aumenta ripetutamente al di sopra di una + certa soglia, contrassegna l'agente come non in linea. -

- Ciò è utile per rilevare agenti che non rispondono o altri problemi di - rete che bloccano il canale di comunicazione. Più nello specifico, il - master invia un comando no-op all'agente e controlla il tempo richiesto - per ricevere i risultati di tale comando no-op. +

+ Ciò è utile per rilevare agenti che non rispondono o altri problemi di rete + che bloccano il canale di comunicazione. Più nello specifico, il master + invia un comando no-op all'agente e controlla il tempo richiesto per + ricevere i risultati di tale comando no-op. +

diff --git a/core/src/main/resources/hudson/node_monitors/ResponseTimeMonitor/help_ja.html b/core/src/main/resources/hudson/node_monitors/ResponseTimeMonitor/help_ja.html index d1e3d127cb..a5e0730973 100644 --- a/core/src/main/resources/hudson/node_monitors/ResponseTimeMonitor/help_ja.html +++ b/core/src/main/resources/hudson/node_monitors/ResponseTimeMonitor/help_ja.html @@ -1,7 +1,8 @@
- マスターからエージェントへの往復の応答時間を監視し、閾値を繰り返し超えるようであればそのエージェントをオフラインにします。 + マスターからエージェントへの往復の応答時間を監視し、閾値を繰り返し超えるようであればそのエージェントをオフラインにします。 -

+

応答しないエージェントや、通信を妨げる他のネットワーク関連の問題を発見するのに有用です。 もっと具体的に言うと、マスターはエージェントに何もしないコマンドを送信し、そのコマンドの結果が戻ってくる時間をチェックします。 -

\ No newline at end of file +

+ diff --git a/core/src/main/resources/hudson/node_monitors/SwapSpaceMonitor/help_ja.html b/core/src/main/resources/hudson/node_monitors/SwapSpaceMonitor/help_ja.html index f2163336f0..cc442524fb 100644 --- a/core/src/main/resources/hudson/node_monitors/SwapSpaceMonitor/help_ja.html +++ b/core/src/main/resources/hudson/node_monitors/SwapSpaceMonitor/help_ja.html @@ -1,22 +1,34 @@
- コンピュータの仮想メモリ容量(一般的には"スワップ容量")を監視し、閾値を下回るようであればそのエージェントをオフラインにします。 + コンピュータの仮想メモリ容量(一般的には"スワップ容量")を監視し、閾値を下回るようであればそのエージェントをオフラインにします。 -

- スワップ容量の正確な定義はプラットホーム依存です。 +

スワップ容量の正確な定義はプラットホーム依存です。

-
    +
    • - Windowsにおけるこの値は、 - ページファイルでの利用可能な容量ですが、 - Windowsはページファイルサイズを自動的に拡張できるので、値にあまり意味はありません。 + Windowsにおけるこの値は、 + + ページファイルでの利用可能な容量 + + ですが、 + Windowsはページファイルサイズを自動的に拡張できるので、値にあまり意味はありません。 +
    • - Linuxでのこの値は、/proc/meminfoから取得します。 - + Linuxでのこの値は、 + /proc/meminfo + から取得します。 +
      • +
    • - 他のUnixシステムでのこの値は、topコマンドの実行結果から取得します。 -
    + 他のUnixシステムでのこの値は、 + top + コマンドの実行結果から取得します。 + +
-

+

もし、この値が報告されないOSがあれば、改善できるように連絡してください。 +

diff --git a/core/src/main/resources/hudson/node_monitors/TemporarySpaceMonitor/help.html b/core/src/main/resources/hudson/node_monitors/TemporarySpaceMonitor/help.html index dd61d898f3..ea237d75ae 100644 --- a/core/src/main/resources/hudson/node_monitors/TemporarySpaceMonitor/help.html +++ b/core/src/main/resources/hudson/node_monitors/TemporarySpaceMonitor/help.html @@ -1,13 +1,18 @@
- This monitors the available disk space of the temporary directory, and if it gets below a certain threshold - the node will be made offline. + This monitors the available disk space of the temporary directory, and if it + gets below a certain threshold the node will be made offline. -

- Java tools and tests/builds often create files in the temporary directory, and may not function - properly if there's no available space. +

+ Java tools and tests/builds often create files in the temporary directory, + and may not function properly if there's no available space. +

-

- More specifically, it checks the available disk space of a partition - that includes directory designated by the java.io.tmpdir system property. - To check where this directory is on a given agent, go to ${rootURL}/computer/AGENTNAME/systemInfo. +

+ More specifically, it checks the available disk space of a partition that + includes directory designated by the + java.io.tmpdir + system property. To check where this directory is on a given agent, go to + ${rootURL}/computer/AGENTNAME/systemInfo + . +

diff --git a/core/src/main/resources/hudson/node_monitors/TemporarySpaceMonitor/help_bg.html b/core/src/main/resources/hudson/node_monitors/TemporarySpaceMonitor/help_bg.html index 04aa1d317e..c921b08caf 100644 --- a/core/src/main/resources/hudson/node_monitors/TemporarySpaceMonitor/help_bg.html +++ b/core/src/main/resources/hudson/node_monitors/TemporarySpaceMonitor/help_bg.html @@ -1,16 +1,21 @@
- Този датчик указва свободното дисково пространство в директорията за - временни файлове. Когато то падне под определен праг, машината се указва - като извън линия. + Този датчик указва свободното дисково пространство в директорията за временни + файлове. Когато то падне под определен праг, машината се указва като извън + линия. -

+

Инструментите на Java както и тестовете и изгражданията често създават временни файлове в нея и може да не работят правилно, когато няма свободно пространство. +

-

+

По-специално, проверката се извършва на файловата система, която съдържа - директорията указвана от системното свойство „java.io.tmpdir“. - За да проверите къде тя се намира на определена машина, прегледайте файла - „${rootURL}/computer/AGENTNAME/systemInfo“. + директорията указвана от системното свойство „ + java.io.tmpdir + “. За да проверите къде тя се намира на определена машина, прегледайте файла + „ + ${rootURL}/computer/AGENTNAME/systemInfo + “. +

diff --git a/core/src/main/resources/hudson/node_monitors/TemporarySpaceMonitor/help_it.html b/core/src/main/resources/hudson/node_monitors/TemporarySpaceMonitor/help_it.html index 42ddb1fe91..4888ded9b2 100644 --- a/core/src/main/resources/hudson/node_monitors/TemporarySpaceMonitor/help_it.html +++ b/core/src/main/resources/hudson/node_monitors/TemporarySpaceMonitor/help_it.html @@ -1,17 +1,22 @@
- Questo modulo mantiene sotto controllo lo spazio su disco disponibile - per la directory temporanea e, se questo scende al di sotto di una certa - soglia, il nodo sarà contrassegnato come non in linea. + Questo modulo mantiene sotto controllo lo spazio su disco disponibile per la + directory temporanea e, se questo scende al di sotto di una certa soglia, il + nodo sarà contrassegnato come non in linea. -

+

Gli strumenti Java e i test/le compilazioni creano spesso file nella - directory temporanea e potrebbero non funzionare correttamente se non - c'è spazio disponibile. + directory temporanea e potrebbero non funzionare correttamente se non c'è + spazio disponibile. +

-

+

Più nello specifico, questo modulo controlla lo spazio su disco disponibile della partizione che include la directory a cui punta la proprietà di - sistema java.io.tmpdir. Per verificare il percorso di questa - directory su un determinato agente, aprire - ${rootURL}/computer/NOMEAGENTE/systemInfo. + sistema + java.io.tmpdir + . Per verificare il percorso di questa directory su un determinato agente, + aprire + ${rootURL}/computer/NOMEAGENTE/systemInfo + . +

diff --git a/core/src/main/resources/hudson/node_monitors/TemporarySpaceMonitor/help_ja.html b/core/src/main/resources/hudson/node_monitors/TemporarySpaceMonitor/help_ja.html index e431210ac2..ebf924eba9 100644 --- a/core/src/main/resources/hudson/node_monitors/TemporarySpaceMonitor/help_ja.html +++ b/core/src/main/resources/hudson/node_monitors/TemporarySpaceMonitor/help_ja.html @@ -1,11 +1,17 @@
- 利用可能なテンポラリディレクトリのディスク容量を監視し、ある閾値を下回るようであれば、ノードはオフラインになります。 + 利用可能なテンポラリディレクトリのディスク容量を監視し、ある閾値を下回るようであれば、ノードはオフラインになります。 -

+

Javaのツール、テストおよびビルドは、よくテンポラリディレクトリにファイルを作成しますが、 利用可能な容量がなければ正しく動作しない可能性があります。 +

-

- もっと具体的に言うと、システムプロパティjava.io.tmpdirで指定されたディレクトリを含むパーティションの利用可能なディスク容量をチェックします。 - エージェントでのこのディレクトリが何であるかチェックするには、${rootURL}/computer/AGENTNAME/systemInfoを参照してください。 +

+ もっと具体的に言うと、システムプロパティ + java.io.tmpdir + で指定されたディレクトリを含むパーティションの利用可能なディスク容量をチェックします。 + エージェントでのこのディレクトリが何であるかチェックするには、 + ${rootURL}/computer/AGENTNAME/systemInfo + を参照してください。 +

diff --git a/core/src/main/resources/hudson/security/AuthorizationStrategy/Unsecured/help.html b/core/src/main/resources/hudson/security/AuthorizationStrategy/Unsecured/help.html index 7f8779198b..e27a185f1a 100644 --- a/core/src/main/resources/hudson/security/AuthorizationStrategy/Unsecured/help.html +++ b/core/src/main/resources/hudson/security/AuthorizationStrategy/Unsecured/help.html @@ -3,8 +3,9 @@ including anonymous users who haven't signed on.

- This is useful in situations where you run Jenkins in a trusted environment - (such as a company intranet) and just want to use authentication for - personalization support. In this way, if someone needs to make a quick - change to Jenkins, they won't be forced to log in. - \ No newline at end of file + This is useful in situations where you run Jenkins in a trusted environment + (such as a company intranet) and just want to use authentication for + personalization support. In this way, if someone needs to make a quick + change to Jenkins, they won't be forced to log in. +

+ diff --git a/core/src/main/resources/hudson/security/AuthorizationStrategy/Unsecured/help_bg.html b/core/src/main/resources/hudson/security/AuthorizationStrategy/Unsecured/help_bg.html index 6c99ea3e59..1e27457f39 100644 --- a/core/src/main/resources/hudson/security/AuthorizationStrategy/Unsecured/help_bg.html +++ b/core/src/main/resources/hudson/security/AuthorizationStrategy/Unsecured/help_bg.html @@ -2,8 +2,9 @@ Всички придобиват пълни права надJenkins, включително анонимните потребители.

- Този режим е удобен в доверени среди, напр. интранета на компания, и се - нуждаете от идентификация само за персонализирането на Jenkins. В такъв - случай, ако някой трябва да направи някаква промяна, няма да има нужда да се - идентифицира и влезе в Jenkins. - \ No newline at end of file + Този режим е удобен в доверени среди, напр. интранета на компания, и се + нуждаете от идентификация само за персонализирането на Jenkins. В такъв + случай, ако някой трябва да направи някаква промяна, няма да има нужда да се + идентифицира и влезе в Jenkins. +

+ diff --git a/core/src/main/resources/hudson/security/AuthorizationStrategy/Unsecured/help_de.html b/core/src/main/resources/hudson/security/AuthorizationStrategy/Unsecured/help_de.html index 54a86c586e..9232ada311 100644 --- a/core/src/main/resources/hudson/security/AuthorizationStrategy/Unsecured/help_de.html +++ b/core/src/main/resources/hudson/security/AuthorizationStrategy/Unsecured/help_de.html @@ -2,9 +2,10 @@ Es findet keine Autorisierung statt. Jeder erhält volle Kontrolle über Jenkins, inklusive anonymer Anwender, die sich nicht angemeldet haben.

- Dies ist praktikabel in Situationen, in denen Sie Jenkins in einer - vertrauenswürdigen Umgebung (z.B. einem Firmenintranet) betreiben und Sie - Authentifizierung nur für personalisierte Anzeigen benötigen. In diesem - Modus muss sich ein Anwender für kleine, schnelle Änderungen in Jenkins nicht - jedesmal explizit anmelden. - \ No newline at end of file + Dies ist praktikabel in Situationen, in denen Sie Jenkins in einer + vertrauenswürdigen Umgebung (z.B. einem Firmenintranet) betreiben und Sie + Authentifizierung nur für personalisierte Anzeigen benötigen. In diesem + Modus muss sich ein Anwender für kleine, schnelle Änderungen in Jenkins + nicht jedesmal explizit anmelden. +

+ diff --git a/core/src/main/resources/hudson/security/AuthorizationStrategy/Unsecured/help_fr.html b/core/src/main/resources/hudson/security/AuthorizationStrategy/Unsecured/help_fr.html index acf958a7ba..50af7f5f8d 100644 --- a/core/src/main/resources/hudson/security/AuthorizationStrategy/Unsecured/help_fr.html +++ b/core/src/main/resources/hudson/security/AuthorizationStrategy/Unsecured/help_fr.html @@ -1,12 +1,13 @@ 
Aucune restriction n'est faite sur les autorisations. Tous les utilisateurs - ont le contrôle complet de Jenkins, y compris les utilisateurs anonymes qui - ne se sont pas authentifiés. + ont le contrôle complet de Jenkins, y compris les utilisateurs anonymes qui ne + se sont pas authentifiés.

- Cela est utile dans les situations où vous lancez Jenkins dans un - environnement de confiance (comme un intranet d'entreprise) et où vous - souhaitez utiliser l'authentification uniquement pour la personnalisation. - De cette façon, si quelqu'un a besoin de faire un changement rapide - sur Jenkins, cette personne ne sera pas forcée à s'authentifier. -

\ No newline at end of file + Cela est utile dans les situations où vous lancez Jenkins dans un + environnement de confiance (comme un intranet d'entreprise) et où vous + souhaitez utiliser l'authentification uniquement pour la personnalisation. + De cette façon, si quelqu'un a besoin de faire un changement rapide sur + Jenkins, cette personne ne sera pas forcée à s'authentifier. +

+ diff --git a/core/src/main/resources/hudson/security/AuthorizationStrategy/Unsecured/help_it.html b/core/src/main/resources/hudson/security/AuthorizationStrategy/Unsecured/help_it.html index 2669ec92f4..38bbfbf437 100644 --- a/core/src/main/resources/hudson/security/AuthorizationStrategy/Unsecured/help_it.html +++ b/core/src/main/resources/hudson/security/AuthorizationStrategy/Unsecured/help_it.html @@ -1,12 +1,13 @@
- Non viene eseguito alcun controllo relativo all'autorizzazione. Chiunque ha - il controllo completo su Jenkins, inclusi gli utenti anonimi che non hanno + Non viene eseguito alcun controllo relativo all'autorizzazione. Chiunque ha il + controllo completo su Jenkins, inclusi gli utenti anonimi che non hanno eseguito l'accesso.

- Ciò è utile in situazioni in cui si esegue Jenkins in un ambiente affidabile - (come un'intranet aziendale) e si vuole semplicemente utilizzare - l'autenticazione come supporto alla personalizzazione. In questo modo, se - qualcuno ha la necessità di apportare una piccola modifica a Jenkins, tale - persona non sarà obbligata ad eseguire l'accesso. + Ciò è utile in situazioni in cui si esegue Jenkins in un ambiente affidabile + (come un'intranet aziendale) e si vuole semplicemente utilizzare + l'autenticazione come supporto alla personalizzazione. In questo modo, se + qualcuno ha la necessità di apportare una piccola modifica a Jenkins, tale + persona non sarà obbligata ad eseguire l'accesso. +

diff --git a/core/src/main/resources/hudson/security/AuthorizationStrategy/Unsecured/help_ja.html b/core/src/main/resources/hudson/security/AuthorizationStrategy/Unsecured/help_ja.html index daa72b4463..a38fb427c0 100644 --- a/core/src/main/resources/hudson/security/AuthorizationStrategy/Unsecured/help_ja.html +++ b/core/src/main/resources/hudson/security/AuthorizationStrategy/Unsecured/help_ja.html @@ -2,7 +2,8 @@ 承認は行いません。ログインしていない匿名ユーザーを含む誰もが、 Jenkinsの全権限を持ちます。

- 信頼できる環境(企業のイントラネットなど)でJenkinsを動作させたり、 - 専用の認証のみ使用したい場合に便利です。 - このように、Jenkinsを素早く変更したい場合に、ログインは強制されません。 + 信頼できる環境(企業のイントラネットなど)でJenkinsを動作させたり、 + 専用の認証のみ使用したい場合に便利です。 + このように、Jenkinsを素早く変更したい場合に、ログインは強制されません。 +

diff --git a/core/src/main/resources/hudson/security/AuthorizationStrategy/Unsecured/help_pt_BR.html b/core/src/main/resources/hudson/security/AuthorizationStrategy/Unsecured/help_pt_BR.html index fc57d11f66..6a2f28e027 100644 --- a/core/src/main/resources/hudson/security/AuthorizationStrategy/Unsecured/help_pt_BR.html +++ b/core/src/main/resources/hudson/security/AuthorizationStrategy/Unsecured/help_pt_BR.html @@ -1,10 +1,14 @@
- Nenhuma checagem de autorização é feita. Todos obtêm control total do Jenkins, - incluindo usuários anônimos que não possuem conta. + Nenhuma checagem de autorização é feita. Todos obtêm + control total do Jenkins, incluindo usuários anônimos que não + possuem conta.

- Isto é útil em situações onde você executa o Jenkins em um ambiente confiável - (tal como em uma rede interna de uma empresa) e apenas quer usar a autenticação para - questão de personalização. Neste caso, se alguém precisar fazer uma rápida - mudança no Jenkins, não será forçado a se logar. + Isto é útil em situações onde você executa o + Jenkins em um ambiente confiável (tal como em uma rede interna de uma + empresa) e apenas quer usar a autenticação para questão de + personalização. Neste caso, se alguém precisar fazer uma + rápida mudança no Jenkins, não será forçado a se + logar. +

diff --git a/core/src/main/resources/hudson/security/AuthorizationStrategy/Unsecured/help_ru.html b/core/src/main/resources/hudson/security/AuthorizationStrategy/Unsecured/help_ru.html index a711f83514..ebc1fd8004 100644 --- a/core/src/main/resources/hudson/security/AuthorizationStrategy/Unsecured/help_ru.html +++ b/core/src/main/resources/hudson/security/AuthorizationStrategy/Unsecured/help_ru.html @@ -1,11 +1,11 @@ 
- Авторизация не производится. Любой посетитель обладает полным контролем над Jenkins, - включая анонимных пользователей. + Авторизация не производится. Любой посетитель обладает полным контролем над + Jenkins, включая анонимных пользователей.

- Этот режим может использоваться в закрытых защищенных окружениях (таких как - корпоративный интранет) и аутентификация используется лишь для использования - персонифицированных настроек. Если кому-либо нужно сделать простые изменения - в конфигурации Jenkins, он может сделать это без прохождения аутентификации. - -

\ No newline at end of file + Этот режим может использоваться в закрытых защищенных окружениях (таких как + корпоративный интранет) и аутентификация используется лишь для использования + персонифицированных настроек. Если кому-либо нужно сделать простые изменения + в конфигурации Jenkins, он может сделать это без прохождения аутентификации. +

+ diff --git a/core/src/main/resources/hudson/security/AuthorizationStrategy/Unsecured/help_tr.html b/core/src/main/resources/hudson/security/AuthorizationStrategy/Unsecured/help_tr.html index 6ec00bf431..b5b447d8f2 100644 --- a/core/src/main/resources/hudson/security/AuthorizationStrategy/Unsecured/help_tr.html +++ b/core/src/main/resources/hudson/security/AuthorizationStrategy/Unsecured/help_tr.html @@ -1,8 +1,12 @@
- Herhangi bir yetkilendirme yapılmaz. Bilinmeyen kullanıcılar da dahil, tüm - kullanıcılar, Jenkins üzerinde tam yetkiye sahip olur. + Herhangi bir yetkilendirme yapılmaz. Bilinmeyen kullanıcılar da + dahil, tüm kullanıcılar, Jenkins üzerinde tam yetkiye + sahip olur.

- Bu güvenlik seçeneği, şirket içi intranet gibi güvenli ortamlarda, kullanıcı - girişinin sadece kişiselleştirme amaçlı kullanıldığı durumlarda faydalı olacaktır. -

\ No newline at end of file + Bu güvenlik seçeneği, şirket içi intranet gibi + güvenli ortamlarda, kullanıcı girişinin sadece + kişiselleştirme amaçlı kullanıldığı + durumlarda faydalı olacaktır. +

+ diff --git a/core/src/main/resources/hudson/security/AuthorizationStrategy/Unsecured/help_zh_TW.html b/core/src/main/resources/hudson/security/AuthorizationStrategy/Unsecured/help_zh_TW.html index ca522ce1c1..1cb367bd18 100644 --- a/core/src/main/resources/hudson/security/AuthorizationStrategy/Unsecured/help_zh_TW.html +++ b/core/src/main/resources/hudson/security/AuthorizationStrategy/Unsecured/help_zh_TW.html @@ -2,6 +2,7 @@ 完全不檢查授權。所有人都可以完成控制 Jenkins，包含沒有登入的匿名使用者。

- 適用裝在可信任環境 (例如公司內網)，而且只想用驗證來做個人化的 Jenkins。 - 這個情況下，有人隨時想改 Jenkins 設定，也不必先登入系統。 - \ No newline at end of file + 適用裝在可信任環境 (例如公司內網)，而且只想用驗證來做個人化的 Jenkins。 + 這個情況下，有人隨時想改 Jenkins 設定，也不必先登入系統。 +

+ diff --git a/core/src/main/resources/hudson/security/FullControlOnceLoggedInAuthorizationStrategy/help-allowAnonymousRead.html b/core/src/main/resources/hudson/security/FullControlOnceLoggedInAuthorizationStrategy/help-allowAnonymousRead.html index 0f357d28e1..6726554f02 100644 --- a/core/src/main/resources/hudson/security/FullControlOnceLoggedInAuthorizationStrategy/help-allowAnonymousRead.html +++ b/core/src/main/resources/hudson/security/FullControlOnceLoggedInAuthorizationStrategy/help-allowAnonymousRead.html @@ -1,3 +1,4 @@
- If checked, this will allow users who are not authenticated to access Jenkins in a read-only mode. + If checked, this will allow users who are not authenticated to access Jenkins + in a read-only mode.
diff --git a/core/src/main/resources/hudson/security/FullControlOnceLoggedInAuthorizationStrategy/help.html b/core/src/main/resources/hudson/security/FullControlOnceLoggedInAuthorizationStrategy/help.html index 3db0e5ac39..b48e35e63a 100644 --- a/core/src/main/resources/hudson/security/FullControlOnceLoggedInAuthorizationStrategy/help.html +++ b/core/src/main/resources/hudson/security/FullControlOnceLoggedInAuthorizationStrategy/help.html @@ -3,7 +3,9 @@ who won't have full control is anonymous user, who only gets read access.

- This mode is useful to force users to log in before taking actions, so that - you can keep record of who has done what. This setting can be also used in - public-facing Jenkins, where you only allow trusted users to have user accounts. - \ No newline at end of file + This mode is useful to force users to log in before taking actions, so that + you can keep record of who has done what. This setting can be also used in + public-facing Jenkins, where you only allow trusted users to have user + accounts. +

+ diff --git a/core/src/main/resources/hudson/security/FullControlOnceLoggedInAuthorizationStrategy/help_bg.html b/core/src/main/resources/hudson/security/FullControlOnceLoggedInAuthorizationStrategy/help_bg.html index b077010e86..5142b94c34 100644 --- a/core/src/main/resources/hudson/security/FullControlOnceLoggedInAuthorizationStrategy/help_bg.html +++ b/core/src/main/resources/hudson/security/FullControlOnceLoggedInAuthorizationStrategy/help_bg.html @@ -4,8 +4,9 @@ управляват Jenkins.

- Този режим кара потребителите да влязат в системата, преди да могат да - извършат промяна. Така може да се следи кой какви промени прави. Режимът е - удобен и при публично достъпни инсталации на Jenkins, при които само на - определени потребители може да се има доверие и да имат регистрации. + Този режим кара потребителите да влязат в системата, преди да могат да + извършат промяна. Така може да се следи кой какви промени прави. Режимът е + удобен и при публично достъпни инсталации на Jenkins, при които само на + определени потребители може да се има доверие и да имат регистрации. +

diff --git a/core/src/main/resources/hudson/security/FullControlOnceLoggedInAuthorizationStrategy/help_de.html b/core/src/main/resources/hudson/security/FullControlOnceLoggedInAuthorizationStrategy/help_de.html index 0fb5b57b06..5d80cd93b9 100644 --- a/core/src/main/resources/hudson/security/FullControlOnceLoggedInAuthorizationStrategy/help_de.html +++ b/core/src/main/resources/hudson/security/FullControlOnceLoggedInAuthorizationStrategy/help_de.html @@ -4,9 +4,10 @@ Benutzer, der nun Lesezugriff erhält.

- Dieser Modus ist sinnvoll, weil er nur angemeldeten Benutzern erlaubt, - Aktionen in Jenkins auszulösen und Sie damit Aufzeichnungen darüber - erstellen können, wer was getan hat. Dieser Modus kann auch in öffentlich - zugänglichen Jenkins-Installationen verwendet werden, bei denen nur - vertrauenswürdige Benutzer Benutzerkonten erhalten. - \ No newline at end of file + Dieser Modus ist sinnvoll, weil er nur angemeldeten Benutzern erlaubt, + Aktionen in Jenkins auszulösen und Sie damit Aufzeichnungen darüber + erstellen können, wer was getan hat. Dieser Modus kann auch in öffentlich + zugänglichen Jenkins-Installationen verwendet werden, bei denen nur + vertrauenswürdige Benutzer Benutzerkonten erhalten. +

+ diff --git a/core/src/main/resources/hudson/security/FullControlOnceLoggedInAuthorizationStrategy/help_fr.html b/core/src/main/resources/hudson/security/FullControlOnceLoggedInAuthorizationStrategy/help_fr.html index 7b713401c8..fa2be7c94a 100644 --- a/core/src/main/resources/hudson/security/FullControlOnceLoggedInAuthorizationStrategy/help_fr.html +++ b/core/src/main/resources/hudson/security/FullControlOnceLoggedInAuthorizationStrategy/help_fr.html @@ -1,12 +1,13 @@ 
- Dans ce mode, un utilisateur connecté obtient le contrôle complet de - Jenkins. Le seul utilisateur qui n'a pas le contrôle complet est - l'utilisateur anonymous, qui n'a que l'accès en lecture seule. + Dans ce mode, un utilisateur connecté obtient le contrôle complet de Jenkins. + Le seul utilisateur qui n'a pas le contrôle complet est l'utilisateur + anonymous, qui n'a que l'accès en lecture seule.

- Ce mode est utile pour forcer les utilisateurs à se logger avant de faire - certaines actions, afin de conserver une trace de qui a fait quoi. - Ce mode peut également être utilisé dans le cas d'une installation publique - de Jenkins, où vous ne pouvez avoir confiance que dans les utilisateurs - qui possèdent des comptes. -

\ No newline at end of file + Ce mode est utile pour forcer les utilisateurs à se logger avant de faire + certaines actions, afin de conserver une trace de qui a fait quoi. Ce mode + peut également être utilisé dans le cas d'une installation publique de + Jenkins, où vous ne pouvez avoir confiance que dans les utilisateurs qui + possèdent des comptes. +

+ diff --git a/core/src/main/resources/hudson/security/FullControlOnceLoggedInAuthorizationStrategy/help_it.html b/core/src/main/resources/hudson/security/FullControlOnceLoggedInAuthorizationStrategy/help_it.html index f7a76cbfca..9d6dad2572 100644 --- a/core/src/main/resources/hudson/security/FullControlOnceLoggedInAuthorizationStrategy/help_it.html +++ b/core/src/main/resources/hudson/security/FullControlOnceLoggedInAuthorizationStrategy/help_it.html @@ -1,12 +1,13 @@
In questa modalità, ogni utente che ha eseguito l'accesso ha il controllo - completo su Jenkins. L'unico utente che non disporrà del controllo completo - è l'utente anonimo, che disporrà unicamente dell'accesso in lettura. + completo su Jenkins. L'unico utente che non disporrà del controllo completo è + l'utente anonimo, che disporrà unicamente dell'accesso in lettura.

- Questa modalità è utile per obbligare gli utenti ad accedere prima di - intraprendere azioni, in modo da tracciare chi ha eseguito cosa. - Quest'opzione può essere utilizzata anche nelle installazioni di Jenkins - pubbliche in cui si consente solo a utenti affidabili di disporre di un - account utente. + Questa modalità è utile per obbligare gli utenti ad accedere prima di + intraprendere azioni, in modo da tracciare chi ha eseguito cosa. + Quest'opzione può essere utilizzata anche nelle installazioni di Jenkins + pubbliche in cui si consente solo a utenti affidabili di disporre di un + account utente. +

diff --git a/core/src/main/resources/hudson/security/FullControlOnceLoggedInAuthorizationStrategy/help_ja.html b/core/src/main/resources/hudson/security/FullControlOnceLoggedInAuthorizationStrategy/help_ja.html index 877ff811b2..8aafa5dd52 100644 --- a/core/src/main/resources/hudson/security/FullControlOnceLoggedInAuthorizationStrategy/help_ja.html +++ b/core/src/main/resources/hudson/security/FullControlOnceLoggedInAuthorizationStrategy/help_ja.html @@ -3,6 +3,7 @@ 全権限を持たない唯一のユーザーは匿名ユーザーで、参照のみできます。

- このモードは、誰が何をしたか記録をとれるように、必ずログインさせたい場合に便利です。 - Jenkinsを外部公開していて、信用できるユーザーにだけアカウントを発行する場合にも、この設定は便利です。 + このモードは、誰が何をしたか記録をとれるように、必ずログインさせたい場合に便利です。 + Jenkinsを外部公開していて、信用できるユーザーにだけアカウントを発行する場合にも、この設定は便利です。 +

diff --git a/core/src/main/resources/hudson/security/FullControlOnceLoggedInAuthorizationStrategy/help_pt_BR.html b/core/src/main/resources/hudson/security/FullControlOnceLoggedInAuthorizationStrategy/help_pt_BR.html index 21215512f9..d7f607ab04 100644 --- a/core/src/main/resources/hudson/security/FullControlOnceLoggedInAuthorizationStrategy/help_pt_BR.html +++ b/core/src/main/resources/hudson/security/FullControlOnceLoggedInAuthorizationStrategy/help_pt_BR.html @@ -1,9 +1,13 @@
- Neste modo, todo usuário logado obtém o controle total do Jenkins. O único usuário - que não terá controle total é o usuário anônimo, que apenas consegue acesso a leitura. + Neste modo, todo usuário logado obtém o controle total do Jenkins. O + único usuário que não terá controle total é o + usuário anônimo, que apenas consegue acesso a leitura.

- Este modo é útil para forcar usuários a logar antes de fazer alguma ação, assim - você pode manter registro de quem fez o quê. Esta configuração também pode ser usada - numa instalação pública do Jenkins, onde você apenas permite usuários confiáveis a ter conta de usuário. + Este modo é útil para forcar usuários a logar antes de fazer + alguma ação, assim você pode manter registro de quem fez o + quê. Esta configuração também pode ser usada numa + instalação pública do Jenkins, onde você apenas permite + usuários confiáveis a ter conta de usuário. +

diff --git a/core/src/main/resources/hudson/security/FullControlOnceLoggedInAuthorizationStrategy/help_ru.html b/core/src/main/resources/hudson/security/FullControlOnceLoggedInAuthorizationStrategy/help_ru.html index 14a490c9e8..9df3f07d0c 100644 --- a/core/src/main/resources/hudson/security/FullControlOnceLoggedInAuthorizationStrategy/help_ru.html +++ b/core/src/main/resources/hudson/security/FullControlOnceLoggedInAuthorizationStrategy/help_ru.html @@ -1,11 +1,13 @@ 
В этом режиме каждый аутентифицированный пользователь получает полный контроль - над Jenkins. Единственный пользователь не имеющий полного доступа - Аноним, + над Jenkins. Единственный пользователь не имеющий полного доступа - Аноним, который имеет права только на просмотр.

- Этот режим полезен для приучения пользователей к аутентификации перед выполнением - каких-либо операций, чтобы вы могли знать что менял каждый пользователь. - Также этот режим может использоваться для предоставления публичного доступа - к Jenkins, когда только доверенным пользователям разрешено иметь аккаунты. -

\ No newline at end of file + Этот режим полезен для приучения пользователей к аутентификации перед + выполнением каких-либо операций, чтобы вы могли знать что менял каждый + пользователь. Также этот режим может использоваться для предоставления + публичного доступа к Jenkins, когда только доверенным пользователям + разрешено иметь аккаунты. +

+ diff --git a/core/src/main/resources/hudson/security/FullControlOnceLoggedInAuthorizationStrategy/help_tr.html b/core/src/main/resources/hudson/security/FullControlOnceLoggedInAuthorizationStrategy/help_tr.html index 35ed338f46..c547bc09f7 100644 --- a/core/src/main/resources/hudson/security/FullControlOnceLoggedInAuthorizationStrategy/help_tr.html +++ b/core/src/main/resources/hudson/security/FullControlOnceLoggedInAuthorizationStrategy/help_tr.html @@ -1,11 +1,17 @@
- Bu modda, giriş yapmış her kullanıcı, Jenkins üzerinde tam yetkiye sahip olur. - Tam yetkiye sahip olmayan tek kullanıcı türü giriş yapmamış (anonymous) kullanıcılardır ki - bu kullanıcıların sadece okuma yetkisi vardır. + Bu modda, giriş yapmış her kullanıcı, Jenkins + üzerinde tam yetkiye sahip olur. Tam yetkiye sahip olmayan tek + kullanıcı türü giriş yapmamış (anonymous) + kullanıcılardır ki bu kullanıcıların sadece + okuma yetkisi vardır.

- Bu mod, kullanıcları, aksiyon almak için giriş yapmaya zorlar. Böylece kimin - ne yaptığı ile ilgili kayıtları tutabilirsiniz. Bu ayarı açmanın bir sebebi de - Jenkins'i public olarak kullanıma açmış olmaktır. Bu şekilde, sadece güvenilir - kullanıcların kullanıcı hesapları olur, diğer tüm herkes kullanıcı girişi yapmadan - (anonymous olarak) kullanır. -

\ No newline at end of file + Bu mod, kullanıcları, aksiyon almak için giriş yapmaya + zorlar. Böylece kimin ne yaptığı ile ilgili + kayıtları tutabilirsiniz. Bu ayarı açmanın bir + sebebi de Jenkins'i public olarak kullanıma açmış + olmaktır. Bu şekilde, sadece güvenilir + kullanıcların kullanıcı hesapları olur, diğer + tüm herkes kullanıcı girişi yapmadan (anonymous olarak) + kullanır. +

+ diff --git a/core/src/main/resources/hudson/security/FullControlOnceLoggedInAuthorizationStrategy/help_zh_TW.html b/core/src/main/resources/hudson/security/FullControlOnceLoggedInAuthorizationStrategy/help_zh_TW.html index 2579fa9239..8d58f71477 100644 --- a/core/src/main/resources/hudson/security/FullControlOnceLoggedInAuthorizationStrategy/help_zh_TW.html +++ b/core/src/main/resources/hudson/security/FullControlOnceLoggedInAuthorizationStrategy/help_zh_TW.html @@ -1,7 +1,9 @@
- 在這個模式下，每個次入 Jenkins 的使用者都可以控制整個系統。但是匿名使用者只有讀取的權限。 + 在這個模式下，每個次入 Jenkins + 的使用者都可以控制整個系統。但是匿名使用者只有讀取的權限。

- 如果您需要追蹤什麼人做了什麼事，這個設定可以強制使用者在做任何異動前都要先用自己身分登入。 - 也可以用在公開的 Jenkins 上，您只會讓受信任的使用者有自己的帳號。 -

\ No newline at end of file + 如果您需要追蹤什麼人做了什麼事，這個設定可以強制使用者在做任何異動前都要先用自己身分登入。 + 也可以用在公開的 Jenkins 上，您只會讓受信任的使用者有自己的帳號。 +

+ diff --git a/core/src/main/resources/hudson/security/GlobalSecurityConfiguration/help-agentProtocol.html b/core/src/main/resources/hudson/security/GlobalSecurityConfiguration/help-agentProtocol.html index bf0c73bfb2..01bcd8d3b2 100644 --- a/core/src/main/resources/hudson/security/GlobalSecurityConfiguration/help-agentProtocol.html +++ b/core/src/main/resources/hudson/security/GlobalSecurityConfiguration/help-agentProtocol.html @@ -1,4 +1,4 @@
- Jenkins uses a TCP port to communicate with various remote agents. This option allows control - over which agent protocols are enabled. -
\ No newline at end of file + Jenkins uses a TCP port to communicate with various remote agents. This option + allows control over which agent protocols are enabled. + diff --git a/core/src/main/resources/hudson/security/GlobalSecurityConfiguration/help-agentProtocol_bg.html b/core/src/main/resources/hudson/security/GlobalSecurityConfiguration/help-agentProtocol_bg.html index d4b9034831..41852a0729 100644 --- a/core/src/main/resources/hudson/security/GlobalSecurityConfiguration/help-agentProtocol_bg.html +++ b/core/src/main/resources/hudson/security/GlobalSecurityConfiguration/help-agentProtocol_bg.html @@ -1,4 +1,4 @@
- Jenkins използва порт па TCP, за да комуникира с подчинените компютри. - Тази опция задава кои протоколи за връзка са включени. + Jenkins използва порт па TCP, за да комуникира с подчинените компютри. Тази + опция задава кои протоколи за връзка са включени.
diff --git a/core/src/main/resources/hudson/security/GlobalSecurityConfiguration/help-disableRememberMe.html b/core/src/main/resources/hudson/security/GlobalSecurityConfiguration/help-disableRememberMe.html index 0fbfed08ae..fb23458960 100644 --- a/core/src/main/resources/hudson/security/GlobalSecurityConfiguration/help-disableRememberMe.html +++ b/core/src/main/resources/hudson/security/GlobalSecurityConfiguration/help-disableRememberMe.html @@ -1,3 +1,4 @@
- Select this option to remove the “Remember me on this computer” checkbox from the login screen. -
\ No newline at end of file + Select this option to remove the “Remember me on this computer” checkbox from + the login screen. + diff --git a/core/src/main/resources/hudson/security/GlobalSecurityConfiguration/help-disableRememberMe_bg.html b/core/src/main/resources/hudson/security/GlobalSecurityConfiguration/help-disableRememberMe_bg.html index 6e25c42168..50375dd469 100644 --- a/core/src/main/resources/hudson/security/GlobalSecurityConfiguration/help-disableRememberMe_bg.html +++ b/core/src/main/resources/hudson/security/GlobalSecurityConfiguration/help-disableRememberMe_bg.html @@ -1,4 +1,4 @@
- Изберете тази опция, за да премахнете полето „Запомняне на този компютър“ от - екрана за вход. -
\ No newline at end of file + Изберете тази опция, за да премахнете полето „Запомняне на този компютър“ от + екрана за вход. + diff --git a/core/src/main/resources/hudson/security/GlobalSecurityConfiguration/help-disableRememberMe_de.html b/core/src/main/resources/hudson/security/GlobalSecurityConfiguration/help-disableRememberMe_de.html index 060ef51cc5..5aab8d722a 100644 --- a/core/src/main/resources/hudson/security/GlobalSecurityConfiguration/help-disableRememberMe_de.html +++ b/core/src/main/resources/hudson/security/GlobalSecurityConfiguration/help-disableRememberMe_de.html @@ -1,4 +1,4 @@
- Wählen Sie diese Option, um die "Meine Anmeldedaten auf diesem Rechner speichern"-Option - vom Benutzeranmeldedialog zu entfernen. + Wählen Sie diese Option, um die "Meine Anmeldedaten auf diesem Rechner + speichern"-Option vom Benutzeranmeldedialog zu entfernen.
diff --git a/core/src/main/resources/hudson/security/GlobalSecurityConfiguration/help-disableRememberMe_it.html b/core/src/main/resources/hudson/security/GlobalSecurityConfiguration/help-disableRememberMe_it.html index 3aca802e49..c3efad3577 100644 --- a/core/src/main/resources/hudson/security/GlobalSecurityConfiguration/help-disableRememberMe_it.html +++ b/core/src/main/resources/hudson/security/GlobalSecurityConfiguration/help-disableRememberMe_it.html @@ -1,4 +1,4 @@
- Selezionare quest'opzione per rimuovere la casella di controllo "Ricordami - su questo computer" dalla schermata di accesso. + Selezionare quest'opzione per rimuovere la casella di controllo "Ricordami su + questo computer" dalla schermata di accesso.
diff --git a/core/src/main/resources/hudson/security/GlobalSecurityConfiguration/help-disableRememberMe_ja.html b/core/src/main/resources/hudson/security/GlobalSecurityConfiguration/help-disableRememberMe_ja.html index cf02243b62..09083085d4 100644 --- a/core/src/main/resources/hudson/security/GlobalSecurityConfiguration/help-disableRememberMe_ja.html +++ b/core/src/main/resources/hudson/security/GlobalSecurityConfiguration/help-disableRememberMe_ja.html @@ -1,3 +1 @@ -
- ログイン画面の"次回から入力を省略"を非表示にします。 -
\ No newline at end of file +
ログイン画面の"次回から入力を省略"を非表示にします。
diff --git a/core/src/main/resources/hudson/security/GlobalSecurityConfiguration/help-slaveAgentPort.html b/core/src/main/resources/hudson/security/GlobalSecurityConfiguration/help-slaveAgentPort.html index 1e6f2732c8..ec7aad0028 100644 --- a/core/src/main/resources/hudson/security/GlobalSecurityConfiguration/help-slaveAgentPort.html +++ b/core/src/main/resources/hudson/security/GlobalSecurityConfiguration/help-slaveAgentPort.html @@ -1,10 +1,9 @@
If you are not using inbound agents, it's recommended that you disable this - entirely, which is the default installation behavior. - Jenkins uses a TCP port to communicate with agents connected inbound. - If you're going to use inbound agents, you can allow the system to randomly - select a port at launch (this avoids interfering with other programs, - including other Jenkins instances). - As it's hard for firewalls to secure a random port, you can instead - specify a fixed port number and configure your firewall accordingly. + entirely, which is the default installation behavior. Jenkins uses a TCP port + to communicate with agents connected inbound. If you're going to use inbound + agents, you can allow the system to randomly select a port at launch (this + avoids interfering with other programs, including other Jenkins instances). As + it's hard for firewalls to secure a random port, you can instead specify a + fixed port number and configure your firewall accordingly.
diff --git a/core/src/main/resources/hudson/security/GlobalSecurityConfiguration/help-slaveAgentPort_bg.html b/core/src/main/resources/hudson/security/GlobalSecurityConfiguration/help-slaveAgentPort_bg.html index 82a37de400..c589fa4b9f 100644 --- a/core/src/main/resources/hudson/security/GlobalSecurityConfiguration/help-slaveAgentPort_bg.html +++ b/core/src/main/resources/hudson/security/GlobalSecurityConfiguration/help-slaveAgentPort_bg.html @@ -5,4 +5,4 @@ ползвате агенти с JNLP, по-добре е да изключите този порт на TCP. Другият вариант и да въведете постоянен порт, което улеснява настройването на защитната стена. - \ No newline at end of file + diff --git a/core/src/main/resources/hudson/security/GlobalSecurityConfiguration/help-slaveAgentPort_fr.html b/core/src/main/resources/hudson/security/GlobalSecurityConfiguration/help-slaveAgentPort_fr.html index ff55164f09..f5b77a1b54 100644 --- a/core/src/main/resources/hudson/security/GlobalSecurityConfiguration/help-slaveAgentPort_fr.html +++ b/core/src/main/resources/hudson/security/GlobalSecurityConfiguration/help-slaveAgentPort_fr.html @@ -1,10 +1,8 @@ 
Si vous n'utilisez pas d'agent à connexions entrantes, il est recommandé de - désactiver ce port, il s'agit du comportement par défaut. - Jenkins utilise un port TCP pour communiquer avec les agents - à connexions entrantes. - Normalement, ce numéro de port est choisi au hasard pour - éviter les collisions, mais cela peut compliquer la sécurisation du - système. Vous pouvez donc spécifier un numéro de port fixe afin de - permettre la configuration de votre firewall. + désactiver ce port, il s'agit du comportement par défaut. Jenkins utilise un + port TCP pour communiquer avec les agents à connexions entrantes. Normalement, + ce numéro de port est choisi au hasard pour éviter les collisions, mais cela + peut compliquer la sécurisation du système. Vous pouvez donc spécifier un + numéro de port fixe afin de permettre la configuration de votre firewall.
diff --git a/core/src/main/resources/hudson/security/GlobalSecurityConfiguration/help-slaveAgentPort_it.html b/core/src/main/resources/hudson/security/GlobalSecurityConfiguration/help-slaveAgentPort_it.html index 7426b33a59..bd93624353 100644 --- a/core/src/main/resources/hudson/security/GlobalSecurityConfiguration/help-slaveAgentPort_it.html +++ b/core/src/main/resources/hudson/security/GlobalSecurityConfiguration/help-slaveAgentPort_it.html @@ -1,11 +1,11 @@
Se non si utilizzano agenti in ingresso, è consigliato disabilitare - completamente quest'opzione (che è il comportamento predefinito). - Jenkins utilizza una porta TCP per comunicare con gli agenti in ingresso. - Se si utilizzeranno gli agenti in ingresso, è possibile consentire al - sistema di selezionare casualmente una porta all'avvio (ciò consente di - evitare interferenze con altri programmi, incluse altre istanze di Jenkins). - Poiché per i firewall è difficile mettere in sicurezza una porta casuale, - come alternativa è possibile specificare un numero di porta fisso e - configurare il proprio firewall di conseguenza. + completamente quest'opzione (che è il comportamento predefinito). Jenkins + utilizza una porta TCP per comunicare con gli agenti in ingresso. Se si + utilizzeranno gli agenti in ingresso, è possibile consentire al sistema di + selezionare casualmente una porta all'avvio (ciò consente di evitare + interferenze con altri programmi, incluse altre istanze di Jenkins). Poiché + per i firewall è difficile mettere in sicurezza una porta casuale, come + alternativa è possibile specificare un numero di porta fisso e configurare il + proprio firewall di conseguenza.
diff --git a/core/src/main/resources/hudson/security/GlobalSecurityConfiguration/help-slaveAgentPort_ja.html b/core/src/main/resources/hudson/security/GlobalSecurityConfiguration/help-slaveAgentPort_ja.html index 78e89b594e..dfc93a62cc 100644 --- a/core/src/main/resources/hudson/security/GlobalSecurityConfiguration/help-slaveAgentPort_ja.html +++ b/core/src/main/resources/hudson/security/GlobalSecurityConfiguration/help-slaveAgentPort_ja.html @@ -3,4 +3,4 @@ 通常このポートは衝突を避けるためにランダムに選ばれますが、システムをセキュアにするのが難しくなります。 JNLPを使用しないなら、このTCPポートをなしにすることをおすすめします。 もしくは、ファイアーウォールを設定できるように、このポート番号を固定にすることもできます。 - \ No newline at end of file + diff --git a/core/src/main/resources/hudson/security/GlobalSecurityConfiguration/help-slaveAgentPort_ru.html b/core/src/main/resources/hudson/security/GlobalSecurityConfiguration/help-slaveAgentPort_ru.html index 52245d7573..03c89069ed 100644 --- a/core/src/main/resources/hudson/security/GlobalSecurityConfiguration/help-slaveAgentPort_ru.html +++ b/core/src/main/resources/hudson/security/GlobalSecurityConfiguration/help-slaveAgentPort_ru.html @@ -1,8 +1,9 @@ 
Jenkins использует порт TCP для общения с агентами подчиненных узлов запущенных через JNLP. Обычно этот порт выбирается автоматически для - предотвращения коллизий, но это может сделать управление безопасностью на - сетевом уровне более сложным. Если вы не используете JNLP для подчиненных - узлов, рекомендуется заблокировать этот порт. Также вы можете указать - статически номер порта и сконфигурировать ваш брандмауэр соответствующим образом. + предотвращения коллизий, но это может сделать управление безопасностью на + сетевом уровне более сложным. Если вы не используете JNLP для подчиненных + узлов, рекомендуется заблокировать этот порт. Также вы можете указать + статически номер порта и сконфигурировать ваш брандмауэр соответствующим + образом.
diff --git a/core/src/main/resources/hudson/security/GlobalSecurityConfiguration/help-useSecurity.html b/core/src/main/resources/hudson/security/GlobalSecurityConfiguration/help-useSecurity.html index 6a4fb22e65..204b9e468b 100644 --- a/core/src/main/resources/hudson/security/GlobalSecurityConfiguration/help-useSecurity.html +++ b/core/src/main/resources/hudson/security/GlobalSecurityConfiguration/help-useSecurity.html @@ -1,15 +1,18 @@

- Enabling security allows configuring authentication (how people can identify themselves) and authorization (what - permissions they get). + Enabling security allows configuring authentication (how people can identify + themselves) and authorization (what permissions they get).

- A number of options are built in. Please note that granting significant permissions to anonymous users, or allowing - users to sign up and granting permissions to all authenticated users, does not actually increase security. + A number of options are built in. Please note that granting significant + permissions to anonymous users, or allowing users to sign up and granting + permissions to all authenticated users, does not actually increase security.

For more information about security and Jenkins, see - this document. + this document + . +

diff --git a/core/src/main/resources/hudson/security/GlobalSecurityConfiguration/help-useSecurity_bg.html b/core/src/main/resources/hudson/security/GlobalSecurityConfiguration/help-useSecurity_bg.html index 77956bb588..6f3f10088a 100644 --- a/core/src/main/resources/hudson/security/GlobalSecurityConfiguration/help-useSecurity_bg.html +++ b/core/src/main/resources/hudson/security/GlobalSecurityConfiguration/help-useSecurity_bg.html @@ -1,14 +1,21 @@

- Включването на сигурността осигурява идентификацията (кои са) и упълномощаването (какви права имат) на потребителите. + Включването на сигурността осигурява идентификацията (кои са) и + упълномощаването (какви права имат) на потребителите.

- Има доста вградени варианти. Даването на прекомерни права на анонимни потребители или даването на прекомерни права - на всеки, който може да влезе, при условие, че може свободно да се регистрира, не е начин да се увеличи сигурността. + Има доста вградени варианти. Даването на прекомерни права на анонимни + потребители или даването на прекомерни права на всеки, който може да влезе, + при условие, че може свободно да се регистрира, не е начин да се увеличи + сигурността.

- За повече информация за сигурността и Jenkins вижте - документацията в уикито. + За повече информация за сигурността и Jenkins вижте + + документацията в уикито + + . +

diff --git a/core/src/main/resources/hudson/security/GlobalSecurityConfiguration/help-useSecurity_de.html b/core/src/main/resources/hudson/security/GlobalSecurityConfiguration/help-useSecurity_de.html index 4ea1ff7dee..4e1017e575 100644 --- a/core/src/main/resources/hudson/security/GlobalSecurityConfiguration/help-useSecurity_de.html +++ b/core/src/main/resources/hudson/security/GlobalSecurityConfiguration/help-useSecurity_de.html @@ -1,24 +1,32 @@
- Wenn aktiviert, müssen Sie sich mit einem Benutzernamen und Passwort anmelden, dem - die "admin"-Rolle zugewiesen ist, um Konfigurationen zu ändern oder neue Builds - zu starten. Die Anmeldung erfolgt über den "Anmelden"-Link oben rechts auf der Seite. + Wenn aktiviert, müssen Sie sich mit einem Benutzernamen und Passwort anmelden, + dem die "admin"-Rolle zugewiesen ist, um Konfigurationen zu ändern oder neue + Builds zu starten. Die Anmeldung erfolgt über den "Anmelden"-Link oben rechts + auf der Seite.

- Die Konfiguration von Benutzerkonten ist anhängig vom Webcontainer, den Sie - einsetzen. Tomcat verwendet beispielsweise standardmäßig die Datei - $TOMCAT_HOME/conf/tomcat-users.xml. + Die Konfiguration von Benutzerkonten ist anhängig vom Webcontainer, den Sie + einsetzen. Tomcat verwendet beispielsweise standardmäßig die Datei + $TOMCAT_HOME/conf/tomcat-users.xml + . +

- Wenn Sie Jenkins im Intranet (oder in einer vertrauenswürdigen Umgebung) einsetzen, - bleibt diese Option in der Regel deaktiviert. Dadurch kann jeder Entwickler - seine Projekte selbst konfigurieren, ohne Sie damit belästigen zu müssen. + Wenn Sie Jenkins im Intranet (oder in einer vertrauenswürdigen Umgebung) + einsetzen, bleibt diese Option in der Regel deaktiviert. Dadurch kann jeder + Entwickler seine Projekte selbst konfigurieren, ohne Sie damit belästigen zu + müssen. +

- Wenn Sie Jenkins hingegen im Internet einsetzen, sollten Sie unbedingt diese - Option aktivieren. Jenkins startet Prozesse auf Ihrem System - ein unsicheres - Jenkins-System ist daher ein sicherer Weg, "gehackt" zu werden. - + Wenn Sie Jenkins hingegen im Internet einsetzen, sollten Sie unbedingt diese + Option aktivieren. Jenkins startet Prozesse auf Ihrem System - ein + unsicheres Jenkins-System ist daher ein sicherer Weg, "gehackt" zu werden. +

+

- Weitere Informationen zum Thema "Sicherheit und Jenkins" finden Sie - hier. + Weitere Informationen zum Thema "Sicherheit und Jenkins" finden Sie + hier + . +

diff --git a/core/src/main/resources/hudson/security/GlobalSecurityConfiguration/help-useSecurity_fr.html b/core/src/main/resources/hudson/security/GlobalSecurityConfiguration/help-useSecurity_fr.html index 1d6cee26d0..0f6c6dd668 100644 --- a/core/src/main/resources/hudson/security/GlobalSecurityConfiguration/help-useSecurity_fr.html +++ b/core/src/main/resources/hudson/security/GlobalSecurityConfiguration/help-useSecurity_fr.html @@ -1,22 +1,29 @@ 
- Si cette option est activée, vous devrez vous connecter avec un nom d'utilisateur - et un mot de passe qui ont le rôle "admin" pour pouvoir changer la configuration ou - lancer un nouveau build (utiliser le lien "login" en haut à droite de cette page). - La configuration des comptes utilisateurs est spécifique au conteneur web que vous - utilisez. Par exemple, par défaut, Tomcat utilise - $TOMCAT_HOME/conf/tomcat-users.xml). + Si cette option est activée, vous devrez vous connecter avec un nom + d'utilisateur et un mot de passe qui ont le rôle "admin" pour pouvoir changer + la configuration ou lancer un nouveau build (utiliser le lien "login" en haut + à droite de cette page). La configuration des comptes utilisateurs est + spécifique au conteneur web que vous utilisez. Par exemple, par défaut, Tomcat + utilise + $TOMCAT_HOME/conf/tomcat-users.xml + ).

- Si vous utilisez Jenkins sur un intranet (ou d'autres environnements "de confiance"), - il est souvent préférable de laisser cette case décochée, ce qui permet à chaque - développeur de configurer son propre projet sans vous déranger. + Si vous utilisez Jenkins sur un intranet (ou d'autres environnements "de + confiance"), il est souvent préférable de laisser cette case décochée, ce + qui permet à chaque développeur de configurer son propre projet sans vous + déranger. +

- Si vous exposez Jenkins sur internet, vous devez activer cette option. Jenkins lance des - processes, donc une installation non-sécurisée de Jenkins est un bon moyen d'attirer - les hackers. + Si vous exposez Jenkins sur internet, vous devez activer cette option. + Jenkins lance des processes, donc une installation non-sécurisée de Jenkins + est un bon moyen d'attirer les hackers. +

- Pour plus d'informations sur la sécurité dans Jenkins, voir - ce document. + Pour plus d'informations sur la sécurité dans Jenkins, voir + ce document + . +

diff --git a/core/src/main/resources/hudson/security/GlobalSecurityConfiguration/help-useSecurity_it.html b/core/src/main/resources/hudson/security/GlobalSecurityConfiguration/help-useSecurity_it.html index 3816dbdf40..9b7c2484e5 100644 --- a/core/src/main/resources/hudson/security/GlobalSecurityConfiguration/help-useSecurity_it.html +++ b/core/src/main/resources/hudson/security/GlobalSecurityConfiguration/help-useSecurity_it.html @@ -1,18 +1,22 @@

- L'abilitazione della sicurezza consente di configurare l'autenticazione - (le modalità con cui le persone possono identificarsi) e l'autorizzazione - (quali permessi ottengono). + L'abilitazione della sicurezza consente di configurare l'autenticazione (le + modalità con cui le persone possono identificarsi) e l'autorizzazione (quali + permessi ottengono).

Sono incorporate svariate opzioni. Si noti che concedere permessi - significativi agli utenti anonimi, o consentire agli utenti di registrarsi - e concedere permessi a tutti gli utenti autenticati, non aumenta - veramente il livello di sicurezza. + significativi agli utenti anonimi, o consentire agli utenti di registrarsi e + concedere permessi a tutti gli utenti autenticati, non aumenta veramente il + livello di sicurezza.

Per ulteriori informazioni sulla sicurezza e su Jenkins, si veda - questo documento. + + questo documento + + . +

diff --git a/core/src/main/resources/hudson/security/GlobalSecurityConfiguration/help-useSecurity_ja.html b/core/src/main/resources/hudson/security/GlobalSecurityConfiguration/help-useSecurity_ja.html index 073a4897bc..d631f1cdd7 100644 --- a/core/src/main/resources/hudson/security/GlobalSecurityConfiguration/help-useSecurity_ja.html +++ b/core/src/main/resources/hudson/security/GlobalSecurityConfiguration/help-useSecurity_ja.html @@ -1,16 +1,28 @@ 
有効にすると，構成を変えたりビルドを実行するには，"管理者(admin)"権限でログインしなければなりません （ページの右上にログイン用のリンクがあります）。 - ユーザアカウントは，使用しているWebコンテナに設定します（たとえば Tomcatの場合，デフォルトでは， - $TOMCAT_HOME/conf/tomcat-users.xmlに設定します）。 + ユーザアカウントは，使用しているWebコンテナに設定します（たとえば + Tomcatの場合，デフォルトでは， + $TOMCAT_HOME/conf/tomcat-users.xml + に設定します）。

- もし Jenkins をイントラネット（または信頼された環境）で使うのであれば、このチェックボックスはOFFにするのが望ましいです。 - その結果、各プロジェクト開発者はあなたの手を煩わせずに、自分のプロジェクトを設定することができます。 + もし Jenkins + をイントラネット（または信頼された環境）で使うのであれば、このチェックボックスはOFFにするのが望ましいです。 + その結果、各プロジェクト開発者はあなたの手を煩わせずに、自分のプロジェクトを設定することができます。 +

+

- もし、Jenkins をインターネットに公開している場合は，これを有効にしなければなりません。 - 有効でないままJenkinsのプロセスを起動すると、Jenkinsはハックされてしまいます。 + もし、Jenkins + をインターネットに公開している場合は，これを有効にしなければなりません。 + 有効でないままJenkinsのプロセスを起動すると、Jenkinsはハックされてしまいます。 +

+

- Jenkins のセキュリティの詳細については， - このドキュメントを参照してください。 + Jenkins のセキュリティの詳細については， + + このドキュメント + + を参照してください。 +

diff --git a/core/src/main/resources/hudson/security/GlobalSecurityConfiguration/help-useSecurity_pt_BR.html b/core/src/main/resources/hudson/security/GlobalSecurityConfiguration/help-useSecurity_pt_BR.html index 7fda160171..4245ef1b11 100644 --- a/core/src/main/resources/hudson/security/GlobalSecurityConfiguration/help-useSecurity_pt_BR.html +++ b/core/src/main/resources/hudson/security/GlobalSecurityConfiguration/help-useSecurity_pt_BR.html @@ -1,20 +1,31 @@
- Se habilitado, você tem que se logar com um usuário e senha que tenha o papel "admin" - antes de mudar a configuração ou executar uma nova construção (procure pelo link "login" - no canto superior direito da página). - A configuração de contas de usuários é específica para o contêiner web que você está usando. - (Por exemplo, no Tomcat, por padrão, ele procura por $TOMCAT_HOME/conf/tomcat-users.xml) + Se habilitado, você tem que se logar com um usuário e senha que + tenha o papel "admin" antes de mudar a configuração ou executar uma + nova construção (procure pelo link "login" no canto superior direito + da página). A configuração de contas de usuários é + específica para o contêiner web que você está usando. (Por + exemplo, no Tomcat, por padrão, ele procura por + $TOMCAT_HOME/conf/tomcat-users.xml + )

- Se você está usando o Jenkins em uma intranet (ou outro ambiente "confiável"), é geralmente - desejável deixar este checkbox desligado, tal que o desenvolvedor do projeto possa configurar seus próprios - projetos sem incomodar você. + Se você está usando o Jenkins em uma intranet (ou outro ambiente + "confiável"), é geralmente desejável deixar este checkbox + desligado, tal que o desenvolvedor do projeto possa configurar seus + próprios projetos sem incomodar você. +

- Se você está expondo Jenkins para a internet, você deve ligar esta opção. O Jenkins é quem lança - os processos, assim um Jenkins inseguro é um caminho certo para ser hackeado. + Se você está expondo Jenkins para a internet, você deve ligar + esta opção. O Jenkins é quem lança os processos, assim + um Jenkins inseguro é um caminho certo para ser hackeado. +

- Para mais informações sobre segurança e Jenkins, veja - este documento. + Para mais informações sobre segurança e Jenkins, veja + + este documento + + . +

diff --git a/core/src/main/resources/hudson/security/GlobalSecurityConfiguration/help-useSecurity_ru.html b/core/src/main/resources/hudson/security/GlobalSecurityConfiguration/help-useSecurity_ru.html index 28184825eb..49a42f273d 100644 --- a/core/src/main/resources/hudson/security/GlobalSecurityConfiguration/help-useSecurity_ru.html +++ b/core/src/main/resources/hudson/security/GlobalSecurityConfiguration/help-useSecurity_ru.html @@ -1,22 +1,27 @@ 
- Если включено, вы будете вынуждены войти в Jenkins используя имя пользователя и пароль имеющими - роль администратора ("admin") для смены настроек или запуска новой сборки (ищите - ссылку "Вход" в правом верхнем углу страницы). - Настройка учетных записей пользователей зависит от контейнера, который вы используете для - запуска Jenkins. (Например, в Tomcat, по-умолчанию, используется файл - $TOMCAT_HOME/conf/tomcat-users.xml) + Если включено, вы будете вынуждены войти в Jenkins используя имя пользователя + и пароль имеющими роль администратора ("admin") для смены настроек или запуска + новой сборки (ищите ссылку "Вход" в правом верхнем углу страницы). Настройка + учетных записей пользователей зависит от контейнера, который вы используете + для запуска Jenkins. (Например, в Tomcat, по-умолчанию, используется файл + $TOMCAT_HOME/conf/tomcat-users.xml + )

- Если вы используете Jenkins в локальной сети (или другом "защищенном" окружении), обычно - не имеет смысла включать эту опцию, так что каждый разработчик может настраивать свои - проекты не отвлекая админа. + Если вы используете Jenkins в локальной сети (или другом "защищенном" + окружении), обычно не имеет смысла включать эту опцию, так что каждый + разработчик может настраивать свои проекты не отвлекая админа. +

- Если вы открываете Jenkins в Интернет, то вам обязательно нужно включить эту опцию. - Jenkins запускает различные процессы, поэтому незащищенный Jenkins - легкий путь для - хакера. + Если вы открываете Jenkins в Интернет, то вам обязательно нужно включить эту + опцию. Jenkins запускает различные процессы, поэтому незащищенный Jenkins - + легкий путь для хакера. +

- Для получения дополнительной информации о безопасности в Jenkins, прочтите - этот документ. + Для получения дополнительной информации о безопасности в Jenkins, прочтите + этот документ + . +

diff --git a/core/src/main/resources/hudson/security/GlobalSecurityConfiguration/help-useSecurity_tr.html b/core/src/main/resources/hudson/security/GlobalSecurityConfiguration/help-useSecurity_tr.html index 49123a314a..f3c632bb95 100644 --- a/core/src/main/resources/hudson/security/GlobalSecurityConfiguration/help-useSecurity_tr.html +++ b/core/src/main/resources/hudson/security/GlobalSecurityConfiguration/help-useSecurity_tr.html @@ -1,20 +1,35 @@
- Eğer bu opsiyonu devreye alırsanız, konfigürasyonu değiştirmek veya yeni bir yapılandırmayı - başlatmak için "admin" rolüne sahip bir kullanıcı ve şifre ile giriş yapmanız gerekir. - (Sayfanın sağ-üst kısmında "giriş" linkini bulabilirsiniz) Kullanıcı hesaplarının konfigürasyonu, - kullandığınız web container'a özeldir. (Mesela, Tomcat kullanıyorsanız, - $TOMCAT_HOME/conf/tomcat-users.xml dosyası dikkate alınır) + Eğer bu opsiyonu devreye alırsanız, konfigürasyonu + değiştirmek veya yeni bir yapılandırmayı + başlatmak için "admin" rolüne sahip bir kullanıcı ve + şifre ile giriş yapmanız gerekir. (Sayfanın + sağ-üst kısmında "giriş" linkini bulabilirsiniz) + Kullanıcı hesaplarının konfigürasyonu, + kullandığınız web container'a özeldir. (Mesela, + Tomcat kullanıyorsanız, + $TOMCAT_HOME/conf/tomcat-users.xml + dosyası dikkate alınır)

- Jenkins'i intranet (veya başka "güvenilir" bir ortamda) içerisinde kullanıyorsanız, bu kutucuğu - işaretlemeyebilirsiniz. Bu durumda proje sahipleri, sizi rahatsız etmeden projelerini - yapılandırabilirler. + Jenkins'i intranet (veya başka "güvenilir" bir ortamda) + içerisinde kullanıyorsanız, bu kutucuğu + işaretlemeyebilirsiniz. Bu durumda proje sahipleri, sizi rahatsız + etmeden projelerini yapılandırabilirler. +

- Jenkins'i internete açacaksanız, güvenliği mutlaka devreye alın. Jenkins'in çalıştırdığı işlemleri - düşünürseniz, güvenlik ayarı olamayan bir Jenkins, hacklenmenin kesin bir yoludur. + Jenkins'i internete açacaksanız, güvenliği mutlaka + devreye alın. Jenkins'in + çalıştırdığı işlemleri + düşünürseniz, güvenlik ayarı olamayan bir + Jenkins, hacklenmenin kesin bir yoludur. +

- Güvenlik ile ilgili daha fazla bilgiyi bu dokümanda - bulabilirsiniz. + Güvenlik ile ilgili daha fazla bilgiyi + + bu dokümanda + + bulabilirsiniz. +

diff --git a/core/src/main/resources/hudson/security/GlobalSecurityConfiguration/help-useSecurity_zh_TW.html b/core/src/main/resources/hudson/security/GlobalSecurityConfiguration/help-useSecurity_zh_TW.html index ea68cdf866..0d2d5b3153 100644 --- a/core/src/main/resources/hudson/security/GlobalSecurityConfiguration/help-useSecurity_zh_TW.html +++ b/core/src/main/resources/hudson/security/GlobalSecurityConfiguration/help-useSecurity_zh_TW.html @@ -1,18 +1,24 @@
- 啟用後，要用具備 "admin" 角色的使用者帳號及密碼登入才能修改設定或是執行新的建置 - (請看頁面右上角的 "登入" 連結)。 - 使用者帳號設定取決於您使用的 Web Container - (以 Tomcat 來說，預設會放在 $TOMCAT_HOME/conf/tomcat-users.xml)。 + 啟用後，要用具備 "admin" + 角色的使用者帳號及密碼登入才能修改設定或是執行新的建置 (請看頁面右上角的 + "登入" 連結)。 使用者帳號設定取決於您使用的 Web Container (以 Tomcat + 來說，預設會放在 + $TOMCAT_HOME/conf/tomcat-users.xml + )。

- 如果您在內網或是其他「信任」的環境中使用 Jenkins，一般不會勾選這個項目。 - 讓每個開發人員都能設定自己的專案，而不用每次都來煩您。 + 如果您在內網或是其他「信任」的環境中使用 Jenkins，一般不會勾選這個項目。 + 讓每個開發人員都能設定自己的專案，而不用每次都來煩您。 +

- 如果您的 Jenkins 可以從網際網路連到，請啟用這個功能。 - Jenkins 會啟動處理序，所以不安全的 Jenkins 肯定是被駭的好路子。 + 如果您的 Jenkins 可以從網際網路連到，請啟用這個功能。 Jenkins + 會啟動處理序，所以不安全的 Jenkins 肯定是被駭的好路子。 +

- 參考這份文件， - 可以看到更多有關安全性及 Jenkins 的資訊。 + 參考 + 這份文件 + ， 可以看到更多有關安全性及 Jenkins 的資訊。 +

diff --git a/core/src/main/resources/hudson/security/HudsonPrivateSecurityRealm/_entryFormPage/resources.css b/core/src/main/resources/hudson/security/HudsonPrivateSecurityRealm/_entryFormPage/resources.css index 00657b8258..dd652033b7 100644 --- a/core/src/main/resources/hudson/security/HudsonPrivateSecurityRealm/_entryFormPage/resources.css +++ b/core/src/main/resources/hudson/security/HudsonPrivateSecurityRealm/_entryFormPage/resources.css @@ -1,12 +1,12 @@ .form-content input { - /* match width with captcha image */ - width:200px; + /* match width with captcha image */ + width: 200px; } .form-content { - margin: 2em; + margin: 2em; } .form-content .error { - margin-bottom: 1em; + margin-bottom: 1em; } diff --git a/core/src/main/resources/hudson/security/HudsonPrivateSecurityRealm/help-allowsSignup.html b/core/src/main/resources/hudson/security/HudsonPrivateSecurityRealm/help-allowsSignup.html index f6e881e3fe..2add9fd1b3 100644 --- a/core/src/main/resources/hudson/security/HudsonPrivateSecurityRealm/help-allowsSignup.html +++ b/core/src/main/resources/hudson/security/HudsonPrivateSecurityRealm/help-allowsSignup.html @@ -1,10 +1,20 @@
- This option allows users to create accounts by themselves, via the "sign up" link on the top right shoulder of the page. - Make sure to not grant significant permissions to authenticated users, as anyone on the network will be able to get them. + This option allows users to create accounts by themselves, via the "sign up" + link on the top right shoulder of the page. + + Make sure to not grant significant permissions to authenticated users, as + anyone on the network will be able to get them. +

- When this checkbox is unchecked, someone with the administrator role would have to create accounts. + When this checkbox is unchecked, someone with the administrator role would + have to create accounts. +

+

- By default, Jenkins does not use captcha verification if the user creates an account by themself. - If you'd like to enable captcha verification, install a captcha support plugin, e.g. the Jenkins - JCaptcha Plugin. + By default, Jenkins does not use captcha verification if the user creates an + account by themself. If you'd like to enable captcha verification, install a + captcha support plugin, e.g. the Jenkins + JCaptcha Plugin + . +

diff --git a/core/src/main/resources/hudson/security/HudsonPrivateSecurityRealm/help-allowsSignup_it.html b/core/src/main/resources/hudson/security/HudsonPrivateSecurityRealm/help-allowsSignup_it.html index 903b2696d4..db5547e89c 100644 --- a/core/src/main/resources/hudson/security/HudsonPrivateSecurityRealm/help-allowsSignup_it.html +++ b/core/src/main/resources/hudson/security/HudsonPrivateSecurityRealm/help-allowsSignup_it.html @@ -1,14 +1,21 @@
Quest'opzione consente agli utenti di creare autonomamente degli account tramite il collegamento "Registrati" in alto a destra nella pagina. - Assicurarsi di non concedere permessi significativi agli utenti - autenticati, in quanto chiunque sulla rete sarà in grado di ottenerli. + + Assicurarsi di non concedere permessi significativi agli utenti autenticati, + in quanto chiunque sulla rete sarà in grado di ottenerli. +

- Quando questa casella di controllo è deselezionata, sarà un utente con il - ruolo di amministratore a dover creare gli account. + Quando questa casella di controllo è deselezionata, sarà un utente con il + ruolo di amministratore a dover creare gli account. +

+

- Per impostazione predefinita, Jenkins non utilizza la verifica CAPTCHA se un - utente crea autonomamente un account. Se si desidera abilitare la verifica - CAPTCHA, installare un componente aggiuntivo di supporto CAPTCHA, ad es. il - plugin di Jenkins JCaptcha. + Per impostazione predefinita, Jenkins non utilizza la verifica CAPTCHA se un + utente crea autonomamente un account. Se si desidera abilitare la verifica + CAPTCHA, installare un componente aggiuntivo di supporto CAPTCHA, ad es. il + plugin di Jenkins + JCaptcha + . +

diff --git a/core/src/main/resources/hudson/security/HudsonPrivateSecurityRealm/help.html b/core/src/main/resources/hudson/security/HudsonPrivateSecurityRealm/help.html index 25a9dd2909..5a7f053362 100644 --- a/core/src/main/resources/hudson/security/HudsonPrivateSecurityRealm/help.html +++ b/core/src/main/resources/hudson/security/HudsonPrivateSecurityRealm/help.html @@ -1,6 +1,7 @@
- Use Jenkins's own user list for authentication, - instead of delegating that to an external system. - This is suitable for smaller set up where you have no existing - user database elsewhere. -
\ No newline at end of file + Use + Jenkins's own user list + for authentication, instead of delegating that to an external system. This is + suitable for smaller set up where you have no existing user database + elsewhere. + diff --git a/core/src/main/resources/hudson/security/HudsonPrivateSecurityRealm/help_bg.html b/core/src/main/resources/hudson/security/HudsonPrivateSecurityRealm/help_bg.html index 924283f48f..f955b58d46 100644 --- a/core/src/main/resources/hudson/security/HudsonPrivateSecurityRealm/help_bg.html +++ b/core/src/main/resources/hudson/security/HudsonPrivateSecurityRealm/help_bg.html @@ -1,6 +1,7 @@
- Използвайте списъка на потребители на Jenkins за - идентификация, вместо това да го прави външна система. Този вариант е подходящ - за по-малки инсталации, при които няма вече съществуваща база от данни с - потребители. -
\ No newline at end of file + Използвайте + списъка на потребители на Jenkins + за идентификация, вместо това да го прави външна система. Този вариант е + подходящ за по-малки инсталации, при които няма вече съществуваща база от + данни с потребители. + diff --git a/core/src/main/resources/hudson/security/HudsonPrivateSecurityRealm/help_de.html b/core/src/main/resources/hudson/security/HudsonPrivateSecurityRealm/help_de.html index 1fdd67c4e8..af17ac5851 100644 --- a/core/src/main/resources/hudson/security/HudsonPrivateSecurityRealm/help_de.html +++ b/core/src/main/resources/hudson/security/HudsonPrivateSecurityRealm/help_de.html @@ -1,6 +1,7 @@
- Verwenden Sie Jenkins' Benutzerverzeichnis zur - Authentifizierung statt dies an ein externes System zu delegieren. - Dies ist praktikabel für kleinere Installationen, bei denen kein bereits + Verwenden Sie + Jenkins' Benutzerverzeichnis + zur Authentifizierung statt dies an ein externes System zu delegieren. Dies + ist praktikabel für kleinere Installationen, bei denen kein bereits bestehendes Benutzerverzeichnis verwendet werden kann. -
\ No newline at end of file + diff --git a/core/src/main/resources/hudson/security/HudsonPrivateSecurityRealm/help_fr.html b/core/src/main/resources/hudson/security/HudsonPrivateSecurityRealm/help_fr.html index 5d14991842..20be70aaca 100644 --- a/core/src/main/resources/hudson/security/HudsonPrivateSecurityRealm/help_fr.html +++ b/core/src/main/resources/hudson/security/HudsonPrivateSecurityRealm/help_fr.html @@ -1,6 +1,7 @@ 
- Utilise la liste des utilisateurs gérée par Jenkins - pour les authentifier, plutôt que de déléguer à un système externe. - Cette solution est pratique pour les configurations simples où vous - n'avez pas d'utilisateurs dans une base de données ailleurs. -
\ No newline at end of file + Utilise la + liste des utilisateurs gérée par Jenkins + pour les authentifier, plutôt que de déléguer à un système externe. Cette + solution est pratique pour les configurations simples où vous n'avez pas + d'utilisateurs dans une base de données ailleurs. + diff --git a/core/src/main/resources/hudson/security/HudsonPrivateSecurityRealm/help_it.html b/core/src/main/resources/hudson/security/HudsonPrivateSecurityRealm/help_it.html index 627208b46e..f439292c08 100644 --- a/core/src/main/resources/hudson/security/HudsonPrivateSecurityRealm/help_it.html +++ b/core/src/main/resources/hudson/security/HudsonPrivateSecurityRealm/help_it.html @@ -1,6 +1,7 @@
- Utilizza l'elenco utenti di Jenkins per - l'autenticazione anziché delegarla a un sistema esterno. Questa è una scelta - adatta per piccole installazioni dove non si dispone di un database utente - esistente salvato altrove. + Utilizza + l'elenco utenti di Jenkins + per l'autenticazione anziché delegarla a un sistema esterno. Questa è una + scelta adatta per piccole installazioni dove non si dispone di un database + utente esistente salvato altrove.
diff --git a/core/src/main/resources/hudson/security/HudsonPrivateSecurityRealm/help_ja.html b/core/src/main/resources/hudson/security/HudsonPrivateSecurityRealm/help_ja.html index 60780133af..f581b9f1a4 100644 --- a/core/src/main/resources/hudson/security/HudsonPrivateSecurityRealm/help_ja.html +++ b/core/src/main/resources/hudson/security/HudsonPrivateSecurityRealm/help_ja.html @@ -1,4 +1,6 @@
- 外部システムに頼るのではなく、Jenkins自身のユーザーリストを認証に使用します。 + 外部システムに頼るのではなく、 + Jenkins自身のユーザーリスト + を認証に使用します。 小規模で、ユーザーデータベースがどこにもない環境で使用する場合に向いています。 -
\ No newline at end of file + diff --git a/core/src/main/resources/hudson/security/HudsonPrivateSecurityRealm/help_pt_BR.html b/core/src/main/resources/hudson/security/HudsonPrivateSecurityRealm/help_pt_BR.html index 316405bf28..056d1977a0 100644 --- a/core/src/main/resources/hudson/security/HudsonPrivateSecurityRealm/help_pt_BR.html +++ b/core/src/main/resources/hudson/security/HudsonPrivateSecurityRealm/help_pt_BR.html @@ -1,6 +1,7 @@
- Usa a própria lista de usuários do Jenkins para fazer a autenticação, - ao invés de delegar isto para um sistema externo. - Isto é indicado para uma configuração simples onde você não tem uma base - de usuário em lugar algum. + Usa + a própria lista de usuários do Jenkins + para fazer a autenticação, ao invés de delegar isto para um + sistema externo. Isto é indicado para uma configuração simples + onde você não tem uma base de usuário em lugar algum.
diff --git a/core/src/main/resources/hudson/security/HudsonPrivateSecurityRealm/help_ru.html b/core/src/main/resources/hudson/security/HudsonPrivateSecurityRealm/help_ru.html index d47be84b18..998759238e 100644 --- a/core/src/main/resources/hudson/security/HudsonPrivateSecurityRealm/help_ru.html +++ b/core/src/main/resources/hudson/security/HudsonPrivateSecurityRealm/help_ru.html @@ -1,5 +1,6 @@ 
- Использовать собственный список пользователей для - аутентификации вместо делегирования этого внешней системе. Подходит для + Использовать + собственный список пользователей + для аутентификации вместо делегирования этого внешней системе. Подходит для небольших инсталляций, для которых у вас ещё нет никакой базы пользователей.
diff --git a/core/src/main/resources/hudson/security/HudsonPrivateSecurityRealm/help_tr.html b/core/src/main/resources/hudson/security/HudsonPrivateSecurityRealm/help_tr.html index 1524ed4ee9..a59f8be543 100644 --- a/core/src/main/resources/hudson/security/HudsonPrivateSecurityRealm/help_tr.html +++ b/core/src/main/resources/hudson/security/HudsonPrivateSecurityRealm/help_tr.html @@ -1,4 +1,6 @@
- Yetkilendirmeyi dış sisteme vermek yerine, Hudson'ın kendi kullanıcı listesi'ni - kullanır. Herhangi bir kullanıcı veritabanı olmayan, küçük çaplı kurulumlar için uygundur. -
\ No newline at end of file + Yetkilendirmeyi dış sisteme vermek yerine, + Hudson'ın kendi kullanıcı listesi + 'ni kullanır. Herhangi bir kullanıcı veritabanı olmayan, + küçük çaplı kurulumlar için uygundur. + diff --git a/core/src/main/resources/hudson/security/HudsonPrivateSecurityRealm/help_zh_TW.html b/core/src/main/resources/hudson/security/HudsonPrivateSecurityRealm/help_zh_TW.html index 5eb3a926dd..341cac728d 100644 --- a/core/src/main/resources/hudson/security/HudsonPrivateSecurityRealm/help_zh_TW.html +++ b/core/src/main/resources/hudson/security/HudsonPrivateSecurityRealm/help_zh_TW.html @@ -1,4 +1,5 @@
- 使用 Jenkins 自己的使用者清單來認證，不要委由外部系統。 - 適合少少人，也沒有別的使用者資料庫時使時。 -
\ No newline at end of file + 使用 + Jenkins 自己的使用者清單 + 來認證，不要委由外部系統。 適合少少人，也沒有別的使用者資料庫時使時。 + diff --git a/core/src/main/resources/hudson/security/LegacyAuthorizationStrategy/help.html b/core/src/main/resources/hudson/security/LegacyAuthorizationStrategy/help.html index 28f2443a77..8f2ad7bc91 100644 --- a/core/src/main/resources/hudson/security/LegacyAuthorizationStrategy/help.html +++ b/core/src/main/resources/hudson/security/LegacyAuthorizationStrategy/help.html @@ -1,5 +1,5 @@
- Behaves exactly the same as Jenkins <1.164. Namely, if you have the "admin" role, - you'll be granted full control over the system, and otherwise (including anonymous - users) you'll only have the read access. + Behaves exactly the same as Jenkins <1.164. Namely, if you have the "admin" + role, you'll be granted full control over the system, and otherwise (including + anonymous users) you'll only have the read access.
diff --git a/core/src/main/resources/hudson/security/LegacyAuthorizationStrategy/help_bg.html b/core/src/main/resources/hudson/security/LegacyAuthorizationStrategy/help_bg.html index 7da733ecae..92b22497d4 100644 --- a/core/src/main/resources/hudson/security/LegacyAuthorizationStrategy/help_bg.html +++ b/core/src/main/resources/hudson/security/LegacyAuthorizationStrategy/help_bg.html @@ -1,5 +1,5 @@
- Поведение като версиите на Jenkins преди 1.164. Ако притежавате ролята - „admin“ ще имате пълен контрол върху системата, в противен случай, - включително, ако не сте влезли, имате права само за четене. + Поведение като версиите на Jenkins преди 1.164. Ако притежавате ролята „admin“ + ще имате пълен контрол върху системата, в противен случай, включително, ако не + сте влезли, имате права само за четене.
diff --git a/core/src/main/resources/hudson/security/LegacyAuthorizationStrategy/help_de.html b/core/src/main/resources/hudson/security/LegacyAuthorizationStrategy/help_de.html index f6a04e61cb..9ece929945 100644 --- a/core/src/main/resources/hudson/security/LegacyAuthorizationStrategy/help_de.html +++ b/core/src/main/resources/hudson/security/LegacyAuthorizationStrategy/help_de.html @@ -2,4 +2,4 @@ Verhält sich exakt wie Jenkins Version <1.164. In der Rolle 'admin' wird Ihnen die volle Kontrolle über das System erteilt. In allen anderen Fällen (dies schließt anonyme Anwender ein), wird nur lesender Zugriff gestattet. - \ No newline at end of file + diff --git a/core/src/main/resources/hudson/security/LegacyAuthorizationStrategy/help_fr.html b/core/src/main/resources/hudson/security/LegacyAuthorizationStrategy/help_fr.html index 263f9d133f..d4f395eda4 100644 --- a/core/src/main/resources/hudson/security/LegacyAuthorizationStrategy/help_fr.html +++ b/core/src/main/resources/hudson/security/LegacyAuthorizationStrategy/help_fr.html @@ -1,7 +1,6 @@ 
- Ceci permet un comportement exactement similaire à celui de Jenkins - d'avant la version 1.164. C'est-à-dire que, si vous avez le rôle - "admin", vous aurez le contrôle complet sur le système. Si vous n'avez - pas ce rôle (ce qui est le cas des utilisateurs anonymes), vous n'aurez - que l'accès en lecture seule. -
\ No newline at end of file + Ceci permet un comportement exactement similaire à celui de Jenkins d'avant la + version 1.164. C'est-à-dire que, si vous avez le rôle "admin", vous aurez le + contrôle complet sur le système. Si vous n'avez pas ce rôle (ce qui est le cas + des utilisateurs anonymes), vous n'aurez que l'accès en lecture seule. + diff --git a/core/src/main/resources/hudson/security/LegacyAuthorizationStrategy/help_it.html b/core/src/main/resources/hudson/security/LegacyAuthorizationStrategy/help_it.html index b93c9caf30..37d19b3be2 100644 --- a/core/src/main/resources/hudson/security/LegacyAuthorizationStrategy/help_it.html +++ b/core/src/main/resources/hudson/security/LegacyAuthorizationStrategy/help_it.html @@ -1,6 +1,6 @@
- Si comporta esattamente come Jenkins 1.164 o una versione precedente, cioè: - se si dispone del ruolo "amministratore" verrà concesso l'accesso completo - al sistema, altrimenti (ciò include gli utenti anonimi) si disporrà solo + Si comporta esattamente come Jenkins 1.164 o una versione precedente, cioè: se + si dispone del ruolo "amministratore" verrà concesso l'accesso completo al + sistema, altrimenti (ciò include gli utenti anonimi) si disporrà solo dell'accesso in lettura.
diff --git a/core/src/main/resources/hudson/security/LegacyAuthorizationStrategy/help_pt_BR.html b/core/src/main/resources/hudson/security/LegacyAuthorizationStrategy/help_pt_BR.html index 6163d4b5d9..999bb9667e 100644 --- a/core/src/main/resources/hudson/security/LegacyAuthorizationStrategy/help_pt_BR.html +++ b/core/src/main/resources/hudson/security/LegacyAuthorizationStrategy/help_pt_BR.html @@ -1,5 +1,6 @@
- Se comporta exatamente da mesma maneira que Jenkins <1.164. Se você tem o papel "admin", - você terá controle total sobre o sistema, e caso contrário (incluindo usuário anônimos) - você apenas terá acesso de leitura. + Se comporta exatamente da mesma maneira que Jenkins <1.164. Se você + tem o papel "admin", você terá controle total sobre o sistema, e + caso contrário (incluindo usuário anônimos) você apenas + terá acesso de leitura.
diff --git a/core/src/main/resources/hudson/security/LegacyAuthorizationStrategy/help_ru.html b/core/src/main/resources/hudson/security/LegacyAuthorizationStrategy/help_ru.html index 8bc13bb79e..160c2570be 100644 --- a/core/src/main/resources/hudson/security/LegacyAuthorizationStrategy/help_ru.html +++ b/core/src/main/resources/hudson/security/LegacyAuthorizationStrategy/help_ru.html @@ -1,5 +1,5 @@ 
- Поступает точно также как Jenkins версий <1.164. То есть если у вас есть роль - "Администратор", вы получаете полный контроль над системой, иначе у вас есть - доступ только для просмотра. -
\ No newline at end of file + Поступает точно также как Jenkins версий <1.164. То есть если у вас есть + роль "Администратор", вы получаете полный контроль над системой, иначе у вас + есть доступ только для просмотра. + diff --git a/core/src/main/resources/hudson/security/LegacyAuthorizationStrategy/help_tr.html b/core/src/main/resources/hudson/security/LegacyAuthorizationStrategy/help_tr.html index f42f63b82d..80a95bc979 100644 --- a/core/src/main/resources/hudson/security/LegacyAuthorizationStrategy/help_tr.html +++ b/core/src/main/resources/hudson/security/LegacyAuthorizationStrategy/help_tr.html @@ -1,5 +1,6 @@
- Jenkins'in 1.164 sürümünden önceki güvenlik davranışıdır. Yani, kullanıcı "admin" - rolünde ise Jenkins üzerinde tam kontrole sahiptir, aksi takdirde sadece okuma - hakkına sahip olacaktır. -
\ No newline at end of file + Jenkins'in 1.164 sürümünden önceki güvenlik + davranışıdır. Yani, kullanıcı "admin" + rolünde ise Jenkins üzerinde tam kontrole sahiptir, aksi takdirde + sadece okuma hakkına sahip olacaktır. + diff --git a/core/src/main/resources/hudson/security/LegacyAuthorizationStrategy/help_zh_TW.html b/core/src/main/resources/hudson/security/LegacyAuthorizationStrategy/help_zh_TW.html index 9a996abdcd..b8f55b003a 100644 --- a/core/src/main/resources/hudson/security/LegacyAuthorizationStrategy/help_zh_TW.html +++ b/core/src/main/resources/hudson/security/LegacyAuthorizationStrategy/help_zh_TW.html @@ -1,4 +1,4 @@
- 跟 Jenkins 1.164 以前的驗證方式一樣。 - 也就是說，如果您身兼 "admin" 角色，就可以控制整個系統，否則 (包含匿名使用者) 就只有讀取權限。 -
\ No newline at end of file + 跟 Jenkins 1.164 以前的驗證方式一樣。 也就是說，如果您身兼 "admin" + 角色，就可以控制整個系統，否則 (包含匿名使用者) 就只有讀取權限。 + diff --git a/core/src/main/resources/hudson/security/LegacySecurityRealm/help.html b/core/src/main/resources/hudson/security/LegacySecurityRealm/help.html index 72596b0d27..f1f329f523 100644 --- a/core/src/main/resources/hudson/security/LegacySecurityRealm/help.html +++ b/core/src/main/resources/hudson/security/LegacySecurityRealm/help.html @@ -1,16 +1,18 @@
- Use the servlet container to authenticate users, as per defined by the servlet spec. - This is historically what Jenkins has been doing up to 1.163. It is useful mainly - for the following situations: + Use the servlet container to authenticate users, as per defined by the servlet + spec. This is historically what Jenkins has been doing up to 1.163. It is + useful mainly for the following situations:
  1. - You've been using Jenkins before 1.164 and would like to keep its behavior. + You've been using Jenkins before 1.164 and would like to keep its + behavior.
  2. You've already configured your container with the right security realm and - prefer Jenkins to just use it. (Sometimes the container offers better documentation - or custom implementations to connect to a specific user realm.) + prefer Jenkins to just use it. (Sometimes the container offers better + documentation or custom implementations to connect to a specific user + realm.)
diff --git a/core/src/main/resources/hudson/security/LegacySecurityRealm/help_bg.html b/core/src/main/resources/hudson/security/LegacySecurityRealm/help_bg.html index f715198cea..2cb3742d4f 100644 --- a/core/src/main/resources/hudson/security/LegacySecurityRealm/help_bg.html +++ b/core/src/main/resources/hudson/security/LegacySecurityRealm/help_bg.html @@ -1,16 +1,18 @@
- Използване на контейнера за сървлети за идентификация на потребителите по спецификация. - Това е, което Jenkins правеше до версия 1.163, включително. Полезно е в следните случаи: + Използване на контейнера за сървлети за идентификация на потребителите по + спецификация. Това е, което Jenkins правеше до версия 1.163, включително. + Полезно е в следните случаи:
  1. - Използвали сте Jenkins преди версия 1.164 и искате да запазите поведението. + Използвали сте Jenkins преди версия 1.164 и искате да запазите + поведението.
  2. Вече сте настроили контейнера да ползва правилната област за сигурност и искате Jenkins просто да я ползва. (Понякога контейнерите имат по-добра - документация или ползват специфичен начин или реализация на връзка с област - потребители.) + документация или ползват специфичен начин или реализация на връзка с + област потребители.)
diff --git a/core/src/main/resources/hudson/security/LegacySecurityRealm/help_de.html b/core/src/main/resources/hudson/security/LegacySecurityRealm/help_de.html index 7a10e0e428..de85495316 100644 --- a/core/src/main/resources/hudson/security/LegacySecurityRealm/help_de.html +++ b/core/src/main/resources/hudson/security/LegacySecurityRealm/help_de.html @@ -1,8 +1,8 @@
Verwenden Sie den Servlet-Container, um Benutzer zu authentifizieren, so wie - dies in der Servlet-Spezifikation festgelegt ist. - Dies ist das Verfahren, das Jenkins bis Version 1.163 eingesetzt hat. - Es ist hauptsächlich in folgenden Situationen sinnvoll: + dies in der Servlet-Spezifikation festgelegt ist. Dies ist das Verfahren, das + Jenkins bis Version 1.163 eingesetzt hat. Es ist hauptsächlich in folgenden + Situationen sinnvoll:
  1. Sie verwenden Jenkins schon bereits vor Version 1.164 und Sie möchten @@ -11,8 +11,8 @@
  2. Sie haben bereits Ihren Container mit den richtigen Benutzerverzeichnissen konfiguriert und möchten, dass Jenkins diese verwendet. In manchen Fällen - bietet der Container eine bessere Dokumentation oder angepasste Implementierungen - um auf bestimmte Benutzerverzeichnisse zuzugreifen. + bietet der Container eine bessere Dokumentation oder angepasste + Implementierungen um auf bestimmte Benutzerverzeichnisse zuzugreifen.
-
\ No newline at end of file + diff --git a/core/src/main/resources/hudson/security/LegacySecurityRealm/help_fr.html b/core/src/main/resources/hudson/security/LegacySecurityRealm/help_fr.html index 3b7630c406..b03c871124 100644 --- a/core/src/main/resources/hudson/security/LegacySecurityRealm/help_fr.html +++ b/core/src/main/resources/hudson/security/LegacySecurityRealm/help_fr.html @@ -1,20 +1,19 @@ 
- Utilise le conteneur de servlet pour authentifier les utilisateurs, - comme défini dans les spécifications des servlets. - C'est historiquement ce qu'a fait Jenkins jusqu'à la version 1.163. - Cela reste utile principalement dans les situations suivantes : + Utilise le conteneur de servlet pour authentifier les utilisateurs, comme + défini dans les spécifications des servlets. C'est historiquement ce qu'a fait + Jenkins jusqu'à la version 1.163. Cela reste utile principalement dans les + situations suivantes :
  1. - Vous avez utilisé Jenkins avant la version 1.164 et vous désirez - conserver le même comportement. + Vous avez utilisé Jenkins avant la version 1.164 et vous désirez conserver + le même comportement.
  2. - Vous avez déjà configuré votre conteneur avec le bon royaume (realm) - de sécurité et vous souhaitez le faire utiliser par Jenkins. - (parfois le conteneur fournit une meilleure documentation ou des - implémentations custom pour se connecter à un royaume utilisateur - spécifique) + Vous avez déjà configuré votre conteneur avec le bon royaume (realm) de + sécurité et vous souhaitez le faire utiliser par Jenkins. (parfois le + conteneur fournit une meilleure documentation ou des implémentations + custom pour se connecter à un royaume utilisateur spécifique)
-
\ No newline at end of file + diff --git a/core/src/main/resources/hudson/security/LegacySecurityRealm/help_it.html b/core/src/main/resources/hudson/security/LegacySecurityRealm/help_it.html index 257227df2e..014db60204 100644 --- a/core/src/main/resources/hudson/security/LegacySecurityRealm/help_it.html +++ b/core/src/main/resources/hudson/security/LegacySecurityRealm/help_it.html @@ -1,18 +1,18 @@
- Utilizza il container servlet per autenticare gli utenti, così come - definito nella specifica servlet. Storicamente questo è ciò che Jenkins ha - eseguito fino alla versione 1.163. L'opzione è utile principalmente nelle - seguenti situazioni: + Utilizza il container servlet per autenticare gli utenti, così come definito + nella specifica servlet. Storicamente questo è ciò che Jenkins ha eseguito + fino alla versione 1.163. L'opzione è utile principalmente nelle seguenti + situazioni:
  1. - Si è utilizzato Jenkins prima della versione 1.164 e si desidera - mantenere tale comportamento. + Si è utilizzato Jenkins prima della versione 1.164 e si desidera mantenere + tale comportamento.
  2. - Si è già configurato il proprio container con l'area di sicurezza - corretta e si preferisce che Jenkins semplicemente la utilizzi. (A volte - il container offre una documentazione migliore o implementazioni + Si è già configurato il proprio container con l'area di sicurezza corretta + e si preferisce che Jenkins semplicemente la utilizzi. (A volte il + container offre una documentazione migliore o implementazioni personalizzate per collegarsi a un'area utente specifica.)
diff --git a/core/src/main/resources/hudson/security/LegacySecurityRealm/help_ja.html b/core/src/main/resources/hudson/security/LegacySecurityRealm/help_ja.html index ed79653f25..de94d852d1 100644 --- a/core/src/main/resources/hudson/security/LegacySecurityRealm/help_ja.html +++ b/core/src/main/resources/hudson/security/LegacySecurityRealm/help_ja.html @@ -4,9 +4,7 @@ 主に、次のような状況で便利です。
    -
  1. - 1.164以前からJenkinsを使用していて、そのまま使用したい場合。 -
    2. +
  2. 1.164以前からJenkinsを使用していて、そのまま使用したい場合。
  3. 既にコンテナーにセキュリティ・レルムを構築済みで、Jenkinsではそれを使用したい場合 (良質なドキュメントや、独自のユーザー・レルムに接続する実装を提供するコンテナーもあります)。 diff --git a/core/src/main/resources/hudson/security/LegacySecurityRealm/help_pt_BR.html b/core/src/main/resources/hudson/security/LegacySecurityRealm/help_pt_BR.html index bb10ce6ba2..ab8d9da98e 100644 --- a/core/src/main/resources/hudson/security/LegacySecurityRealm/help_pt_BR.html +++ b/core/src/main/resources/hudson/security/LegacySecurityRealm/help_pt_BR.html @@ -1,16 +1,21 @@
    - Usa o contêiner de servlet para autenticar os usuários, conforme definido pela especificação do servlet. - Isto é históricamente o que o Jenkins estava fazendo até a versão 1.163. Isto é útil principalmente - para as seguintes situações: + Usa o contêiner de servlet para autenticar os usuários, conforme + definido pela especificação do servlet. Isto é + históricamente o que o Jenkins estava fazendo até a versão + 1.163. Isto é útil principalmente para as seguintes + situações:
    1. - Você estava usando uma versão anterior a 1.164 e gostaria de manter seu comportamento. + Você estava usando uma versão anterior a 1.164 e gostaria de + manter seu comportamento.
    2. - Você já configurou seu contêiner com domínio de segurança correto e - prefere que o Jenkins use-o. (algumas vezes o contêiner oferece uma documentação melhor - ou implementações customizadas para conectar a domínio de usuários específico.) + Você já configurou seu contêiner com domínio de + segurança correto e prefere que o Jenkins use-o. (algumas vezes o + contêiner oferece uma documentação melhor ou + implementações customizadas para conectar a domínio de + usuários específico.)
    diff --git a/core/src/main/resources/hudson/security/LegacySecurityRealm/help_ru.html b/core/src/main/resources/hudson/security/LegacySecurityRealm/help_ru.html index 6a7d0cd49e..918e38f848 100644 --- a/core/src/main/resources/hudson/security/LegacySecurityRealm/help_ru.html +++ b/core/src/main/resources/hudson/security/LegacySecurityRealm/help_ru.html @@ -1,16 +1,19 @@ 
    - Использовать контейнер сервлетов для аутентификации пользователей, в соответствии с - документацией к используемому вами контейнеру. Это исторически сохранившийся способ - использовался в Jenkins до версии 1.163. Он может быть полезен в следующих ситуациях: + Использовать контейнер сервлетов для аутентификации пользователей, в + соответствии с документацией к используемому вами контейнеру. Это исторически + сохранившийся способ использовался в Jenkins до версии 1.163. Он может быть + полезен в следующих ситуациях:
    1. - Вы использовали Jenkins до версии 1.164 и хотели бы сохранить привычное поведение. + Вы использовали Jenkins до версии 1.164 и хотели бы сохранить привычное + поведение.
    2. - Вы уже настроили ваш контейнер с модулем безопасности и предпочитаете чтобы Jenkins - использовал его. (Иногда контейнер предлагает лучшую документированность и - более гибкие возможности настройки для соединения с конкретным модулем безопасности). + Вы уже настроили ваш контейнер с модулем безопасности и предпочитаете + чтобы Jenkins использовал его. (Иногда контейнер предлагает лучшую + документированность и более гибкие возможности настройки для соединения с + конкретным модулем безопасности).
    -
    \ No newline at end of file +
diff --git a/core/src/main/resources/hudson/security/LegacySecurityRealm/help_tr.html b/core/src/main/resources/hudson/security/LegacySecurityRealm/help_tr.html index ff43926126..dc1eff876d 100644 --- a/core/src/main/resources/hudson/security/LegacySecurityRealm/help_tr.html +++ b/core/src/main/resources/hudson/security/LegacySecurityRealm/help_tr.html @@ -1,15 +1,22 @@
- Servlet spesifikasyonunda belirtildiği gibi, kullanıcları yönetmek için servlet container'ı kullanabilirsiniz. - Jenkins 1.163 sürümüne kadar bu yöntemle çalışmaktaydı. Aşağıdaki durumlarda hayli kullanışlıdır. + Servlet spesifikasyonunda belirtildiği gibi, kullanıcları + yönetmek için servlet container'ı kullanabilirsiniz. Jenkins + 1.163 sürümüne kadar bu yöntemle + çalışmaktaydı. Aşağıdaki durumlarda hayli + kullanışlıdır.
  1. - Jenkins'i 1.164'ten önceki bir versiyonundan beri kullanıyor ve davranış şeklini değiştirmek istemiyorsanız. + Jenkins'i 1.164'ten önceki bir versiyonundan beri kullanıyor ve + davranış şeklini değiştirmek istemiyorsanız.
  2. - Container'ınızı doğru güvenlik ayarları ile konfigüre ettiyseniz ve Jenkins'in de buna uymasını istiyorsanız. - (Bazı durumlarda, container, kullanıcının kullanmak istediği güvenlik metodu için daha iyi dokümantasyon veya - daha kendine has altyapı sağlayabilir) + Container'ınızı doğru güvenlik ayarları ile + konfigüre ettiyseniz ve Jenkins'in de buna uymasını + istiyorsanız. (Bazı durumlarda, container, + kullanıcının kullanmak istediği güvenlik metodu + için daha iyi dokümantasyon veya daha kendine has altyapı + sağlayabilir)
-
\ No newline at end of file + diff --git a/core/src/main/resources/hudson/security/LegacySecurityRealm/help_zh_TW.html b/core/src/main/resources/hudson/security/LegacySecurityRealm/help_zh_TW.html index 15e8045a28..868f4e8aef 100644 --- a/core/src/main/resources/hudson/security/LegacySecurityRealm/help_zh_TW.html +++ b/core/src/main/resources/hudson/security/LegacySecurityRealm/help_zh_TW.html @@ -1,14 +1,12 @@
- 由 Servlet Container 驗證使用者，就像 Servlet 規格裡定義的那樣。 - 這是 Jenkins 1.163 及更早以前版本的陳年機制。主要適用於: + 由 Servlet Container 驗證使用者，就像 Servlet 規格裡定義的那樣。 這是 Jenkins + 1.163 及更早以前版本的陳年機制。主要適用於:
    +
  1. 您從 1.164 之前就開始用 Jenkins，而且很念舊。
  2. - 您從 1.164 之前就開始用 Jenkins，而且很念舊。 -
    3. -
  3. - 您已經在 Container 裡設好正確的安全性領域，希望 Jenkins 直接用。 - (有時 Container 提供的文件更齊全，或是有連到特定使用者資料庫的更好實作機制。) + 您已經在 Container 裡設好正確的安全性領域，希望 Jenkins 直接用。 (有時 + Container 提供的文件更齊全，或是有連到特定使用者資料庫的更好實作機制。)
diff --git a/core/src/main/resources/hudson/security/csrf/DefaultCrumbIssuer/help-excludeClientIPFromCrumb.html b/core/src/main/resources/hudson/security/csrf/DefaultCrumbIssuer/help-excludeClientIPFromCrumb.html index 268a1934f1..25392c0583 100644 --- a/core/src/main/resources/hudson/security/csrf/DefaultCrumbIssuer/help-excludeClientIPFromCrumb.html +++ b/core/src/main/resources/hudson/security/csrf/DefaultCrumbIssuer/help-excludeClientIPFromCrumb.html @@ -1,7 +1,7 @@
- Some HTTP proxies filter out information that the default crumb issuer uses - to calculate the nonce value. If an HTTP proxy sits between your browser client - and your Jenkins server and you receive a 403 response when submitting a form - to Jenkins, checking this option may help. Using this option makes the nonce - value easier to forge. + Some HTTP proxies filter out information that the default crumb issuer uses to + calculate the nonce value. If an HTTP proxy sits between your browser client + and your Jenkins server and you receive a 403 response when submitting a form + to Jenkins, checking this option may help. Using this option makes the nonce + value easier to forge.
diff --git a/core/src/main/resources/hudson/security/csrf/DefaultCrumbIssuer/help-excludeClientIPFromCrumb_bg.html b/core/src/main/resources/hudson/security/csrf/DefaultCrumbIssuer/help-excludeClientIPFromCrumb_bg.html index e43be4d96f..e77482c2ec 100644 --- a/core/src/main/resources/hudson/security/csrf/DefaultCrumbIssuer/help-excludeClientIPFromCrumb_bg.html +++ b/core/src/main/resources/hudson/security/csrf/DefaultCrumbIssuer/help-excludeClientIPFromCrumb_bg.html @@ -1,7 +1,7 @@
- Някои сървъри-посредници за HTTP филтрират информацията, която стандартно се - използва за изчисляване на еднократно използваните стойности. Ако между - браузъра и Jenkins стои сървър-посредник и получавате код за грешка 403, - когато подавате формуляр, пробвайте да зададете тази настройка. Недостатъкът - е, че така еднократните стойности се фалшифицират по-лесно. + Някои сървъри-посредници за HTTP филтрират информацията, която стандартно се + използва за изчисляване на еднократно използваните стойности. Ако между + браузъра и Jenkins стои сървър-посредник и получавате код за грешка 403, + когато подавате формуляр, пробвайте да зададете тази настройка. Недостатъкът + е, че така еднократните стойности се фалшифицират по-лесно.
diff --git a/core/src/main/resources/hudson/security/csrf/DefaultCrumbIssuer/help-excludeClientIPFromCrumb_it.html b/core/src/main/resources/hudson/security/csrf/DefaultCrumbIssuer/help-excludeClientIPFromCrumb_it.html index 9306f593df..27b772fc45 100644 --- a/core/src/main/resources/hudson/security/csrf/DefaultCrumbIssuer/help-excludeClientIPFromCrumb_it.html +++ b/core/src/main/resources/hudson/security/csrf/DefaultCrumbIssuer/help-excludeClientIPFromCrumb_it.html @@ -1,8 +1,8 @@
- Alcuni proxy HTTP filtrano le informazioni che il componente predefinito di - emissione dei crumb utilizza per calcolare il valore del nonce. Se c'è un - proxy HTTP collocato fra il browser e il server Jenkins e si riceve una - risposta 403 quando si invia un modulo a Jenkins, l'abilitazione di - quest'opzione potrebbe essere di aiuto. L'utilizzo di quest'opzione rende - il valore del nonce più facile da falsificare. + Alcuni proxy HTTP filtrano le informazioni che il componente predefinito di + emissione dei crumb utilizza per calcolare il valore del nonce. Se c'è un + proxy HTTP collocato fra il browser e il server Jenkins e si riceve una + risposta 403 quando si invia un modulo a Jenkins, l'abilitazione di + quest'opzione potrebbe essere di aiuto. L'utilizzo di quest'opzione rende il + valore del nonce più facile da falsificare.
diff --git a/core/src/main/resources/hudson/security/csrf/DefaultCrumbIssuer/help-excludeClientIPFromCrumb_zh_TW.html b/core/src/main/resources/hudson/security/csrf/DefaultCrumbIssuer/help-excludeClientIPFromCrumb_zh_TW.html index 1f6fd0f869..d7ede809a1 100644 --- a/core/src/main/resources/hudson/security/csrf/DefaultCrumbIssuer/help-excludeClientIPFromCrumb_zh_TW.html +++ b/core/src/main/resources/hudson/security/csrf/DefaultCrumbIssuer/help-excludeClientIPFromCrumb_zh_TW.html @@ -1,6 +1,6 @@
- 某些 HTTP 代理伺服器會將預設 Crumb 簽發程式用來計算 Nonce 值的資訊過濾掉。 - 如果您的瀏覽器與 Jenkins 伺服器之間有 HTTP 代理伺服器，而且當您送出表單後收到 403 回應， - 把這個選項勾起來可能會有幫助。 - 使用這個功能會讓 Nonce 值更容易偽造。 + 某些 HTTP 代理伺服器會將預設 Crumb 簽發程式用來計算 Nonce 值的資訊過濾掉。 + 如果您的瀏覽器與 Jenkins 伺服器之間有 HTTP 代理伺服器，而且當您送出表單後收到 + 403 回應， 把這個選項勾起來可能會有幫助。 使用這個功能會讓 Nonce + 值更容易偽造。
diff --git a/core/src/main/resources/hudson/security/csrf/GlobalCrumbIssuerConfiguration/help-csrf.html b/core/src/main/resources/hudson/security/csrf/GlobalCrumbIssuerConfiguration/help-csrf.html index aa7e7e3da2..cb4a797eae 100644 --- a/core/src/main/resources/hudson/security/csrf/GlobalCrumbIssuerConfiguration/help-csrf.html +++ b/core/src/main/resources/hudson/security/csrf/GlobalCrumbIssuerConfiguration/help-csrf.html @@ -1,18 +1,33 @@
- A cross site request forgery (or CSRF/XSRF) is an exploit that enables - an unauthorized third party to take actions on a web site as you. In Jenkins, - this could allow someone to delete jobs, builds or change Jenkins' configuration. + A cross site request forgery (or CSRF/XSRF) is an exploit that enables an + unauthorized third party to take actions on a web site as you. In Jenkins, + this could allow someone to delete jobs, builds or change Jenkins' + configuration.

- When this option is enabled, Jenkins will check for a generated nonce value, or - "crumb", on any request that may cause a change on the Jenkins server. This - includes any form submission and calls to the remote API. -

- Enabling this option can result in some problems, like the following: + When this option is enabled, Jenkins will check for a generated nonce value, + or "crumb", on any request that may cause a change on the Jenkins server. + This includes any form submission and calls to the remote API. +

+ +

Enabling this option can result in some problems, like the following:

+
    -
  • Some Jenkins features (like the remote API) are more difficult to use when this option is enabled.
    • -
  • Some features, especially in plugins not tested with this option enabled, may not work at all.
    • -
  • If you are accessing Jenkins through a reverse proxy, it may strip the CSRF HTTP header, resulting in some protected actions failing.
    • +
  • + Some Jenkins features (like the remote API) are more difficult to use when + this option is enabled. +
    • +
  • + Some features, especially in plugins not tested with this option enabled, + may not work at all. +
    • +
  • + If you are accessing Jenkins through a reverse proxy, it may strip the + CSRF HTTP header, resulting in some protected actions failing. +

- More information about CSRF exploits can be found here. + More information about CSRF exploits can be found + here + . +

diff --git a/core/src/main/resources/hudson/security/csrf/GlobalCrumbIssuerConfiguration/help-csrf_bg.html b/core/src/main/resources/hudson/security/csrf/GlobalCrumbIssuerConfiguration/help-csrf_bg.html index 9187dea50e..3ab824f7f0 100644 --- a/core/src/main/resources/hudson/security/csrf/GlobalCrumbIssuerConfiguration/help-csrf_bg.html +++ b/core/src/main/resources/hudson/security/csrf/GlobalCrumbIssuerConfiguration/help-csrf_bg.html @@ -1,24 +1,34 @@
Заявките с фалшив произход (CSRF/XSRF) са начин, който позволява на трета страна да извършва действия на сайта от ваше име, без да има право на това. В - случая на Jenkins това би позволило на неупълномощени лица да изтриват задания, - изграждания или да променят настройките на Jenkins. + случая на Jenkins това би позволило на неупълномощени лица да изтриват + задания, изграждания или да променят настройките на Jenkins.

- Когато това е включено, Jenkins ще проверява за специална еднократна стойност - при всяка заявка, която променя нещо на сървъра. Това включва подаването на - всеки формуляр и заявките към отдалеченото API. -

- Включването на тази опция може да доведе и до някои проблеми, например: + Когато това е включено, Jenkins ще проверява за специална еднократна + стойност при всяка заявка, която променя нещо на сървъра. Това включва + подаването на всеки формуляр и заявките към отдалеченото API. +

+ +

Включването на тази опция може да доведе и до някои проблеми, например:

+
    -
  • някои възможности на Jenkins, като отдалеченото API стават по-трудни за - употреба
    • -
  • някои възможности в приставките, особено тези, които не са тествани - достатъчно, може съвсем да не работят;
    • -
  • ако достъпвате Jenkins през насрещен сървър-посредник, той може да - филтрира заглавните части на HTTP за CSRF, което ще направи някои - защитени действия невъзможни.
    • +
  • + някои възможности на Jenkins, като отдалеченото API стават по-трудни за + употреба +
    • +
  • + някои възможности в приставките, особено тези, които не са тествани + достатъчно, може съвсем да не работят; +
    • +
  • + ако достъпвате Jenkins през насрещен сървър-посредник, той може да + филтрира заглавните части на HTTP за CSRF, което ще направи някои защитени + действия невъзможни. +

- Повече информация за заявките с фалшив произход (CSRF) има - тук. + Повече информация за заявките с фалшив произход (CSRF) има + тук + . +

diff --git a/core/src/main/resources/hudson/security/csrf/GlobalCrumbIssuerConfiguration/help-csrf_de.html b/core/src/main/resources/hudson/security/csrf/GlobalCrumbIssuerConfiguration/help-csrf_de.html index 6163b2c352..32664a2644 100644 --- a/core/src/main/resources/hudson/security/csrf/GlobalCrumbIssuerConfiguration/help-csrf_de.html +++ b/core/src/main/resources/hudson/security/csrf/GlobalCrumbIssuerConfiguration/help-csrf_de.html @@ -1,14 +1,19 @@
- Eine "cross site request forgery" (CSRF/XSRF), zu deutsch etwa "Site-übergreifende Aufruf-Manipulation", - ist ein Angriff auf ein Computersystem, bei dem der Angreifer unberechtigt Daten in einer Webanwendung - verändert. Im Falle von Jenkins würde dies Unbefugten etwa erlauben, Jobs und Builds zu löschen - oder Jenkins Systemkonfiguration zu verändern. - + Eine "cross site request forgery" (CSRF/XSRF), zu deutsch etwa + "Site-übergreifende Aufruf-Manipulation", ist ein Angriff auf ein + Computersystem, bei dem der Angreifer unberechtigt Daten in einer Webanwendung + verändert. Im Falle von Jenkins würde dies Unbefugten etwa erlauben, Jobs und + Builds zu löschen oder Jenkins Systemkonfiguration zu verändern. +

- Wenn angewählt, wird Jenkins jede Anfrage, die den Server verändern könnte, nach einem - speziell generierten Wert ("crumb") überprüfen. Dies beinhaltet alle Formularübermittlungen - und Aufrufe der Remote-API. + Wenn angewählt, wird Jenkins jede Anfrage, die den Server verändern könnte, + nach einem speziell generierten Wert ("crumb") überprüfen. Dies beinhaltet + alle Formularübermittlungen und Aufrufe der Remote-API. +

- Mehr über CSRF-Angriffe finden Sie hier. + Mehr über CSRF-Angriffe finden Sie + hier + . +

diff --git a/core/src/main/resources/hudson/security/csrf/GlobalCrumbIssuerConfiguration/help-csrf_it.html b/core/src/main/resources/hudson/security/csrf/GlobalCrumbIssuerConfiguration/help-csrf_it.html index 609b059c9a..096fcbccc2 100644 --- a/core/src/main/resources/hudson/security/csrf/GlobalCrumbIssuerConfiguration/help-csrf_it.html +++ b/core/src/main/resources/hudson/security/csrf/GlobalCrumbIssuerConfiguration/help-csrf_it.html @@ -1,27 +1,39 @@
- Una cross site request forgery (o CSRF/XSRF) è un exploit che consente a - una terza parte non autorizzata di eseguire azioni su un sito Web con le - proprie credenziali. In Jenkins, ciò potrebbe consentire a qualcuno di - eliminare processi, compilazioni o di modificare la configurazione di Jenkins. + Una cross site request forgery (o CSRF/XSRF) è un exploit che consente a una + terza parte non autorizzata di eseguire azioni su un sito Web con le proprie + credenziali. In Jenkins, ciò potrebbe consentire a qualcuno di eliminare + processi, compilazioni o di modificare la configurazione di Jenkins.

- Quando quest'opzione è abilitata, Jenkins verificherà la presenza di un - valore nonce generato, o "crumb", all'interno di qualunque richiesta che - potrebbe causare una modifica sul server Jenkins. Ciò include qualunque - invio di moduli e le chiamate all'API remota. + Quando quest'opzione è abilitata, Jenkins verificherà la presenza di un + valore nonce generato, o "crumb", all'interno di qualunque richiesta che + potrebbe causare una modifica sul server Jenkins. Ciò include qualunque + invio di moduli e le chiamate all'API remota. +

+

- L'abilitazione di quest'opzione potrebbe comportare alcuni problemi, come i - seguenti: + L'abilitazione di quest'opzione potrebbe comportare alcuni problemi, come i + seguenti: +

+
    -
  • Alcune funzionalità di Jenkins (come l'API remota) sono più difficili - da utilizzare quando quest'opzione è abilitata.
    • -
  • Alcune funzionalità, in particolar modo quelle presenti nei componenti - aggiuntivi non testati con quest'opzione abilitata, potrebbero non - funzionare.
    • -
  • Se si accede a Jenkins tramite un reverse proxy, questo potrebbe - rimuovere l'intestazione HTTP CSRF, il che fa sì che alcune azioni - protette non riescano.
    • +
  • + Alcune funzionalità di Jenkins (come l'API remota) sono più difficili da + utilizzare quando quest'opzione è abilitata. +
    • +
  • + Alcune funzionalità, in particolar modo quelle presenti nei componenti + aggiuntivi non testati con quest'opzione abilitata, potrebbero non + funzionare. +
    • +
  • + Se si accede a Jenkins tramite un reverse proxy, questo potrebbe rimuovere + l'intestazione HTTP CSRF, il che fa sì che alcune azioni protette non + riescano. +

- È possibile reperire ulteriori informazioni sugli exploit CSRF - qui. + È possibile reperire ulteriori informazioni sugli exploit CSRF + qui + . +

diff --git a/core/src/main/resources/hudson/security/csrf/GlobalCrumbIssuerConfiguration/help-csrf_ja.html b/core/src/main/resources/hudson/security/csrf/GlobalCrumbIssuerConfiguration/help-csrf_ja.html index d79200a977..76ad4506f8 100644 --- a/core/src/main/resources/hudson/security/csrf/GlobalCrumbIssuerConfiguration/help-csrf_ja.html +++ b/core/src/main/resources/hudson/security/csrf/GlobalCrumbIssuerConfiguration/help-csrf_ja.html @@ -2,8 +2,13 @@ クロスサイトリクエストフォージェリ(CSRFもしくはXSRF)は、認証されていない第３者があなたを装って何かしらの操作を行うことを許してしまう脆弱性です。 Jenkinsでは、ジョブの削除、ビルドおよび設定変更を行うことができてしまいます。

- このオプションを有効にすると、Jenkinsサーバでの変更を伴うリクエストについて、ノンス(使い捨ての乱数)や"crumb"をチェックします。 - フォームの実行やリモートAPIの呼び出しでも同様です。 + このオプションを有効にすると、Jenkinsサーバでの変更を伴うリクエストについて、ノンス(使い捨ての乱数)や"crumb"をチェックします。 + フォームの実行やリモートAPIの呼び出しでも同様です。 +

+

- CSRFについての詳細は、ここを参照してください。 + CSRFについての詳細は、 + ここ + を参照してください。 +

diff --git a/core/src/main/resources/hudson/security/csrf/GlobalCrumbIssuerConfiguration/help-csrf_zh_TW.html b/core/src/main/resources/hudson/security/csrf/GlobalCrumbIssuerConfiguration/help-csrf_zh_TW.html index 8c0851877f..ba75a76f22 100644 --- a/core/src/main/resources/hudson/security/csrf/GlobalCrumbIssuerConfiguration/help-csrf_zh_TW.html +++ b/core/src/main/resources/hudson/security/csrf/GlobalCrumbIssuerConfiguration/help-csrf_zh_TW.html @@ -1,9 +1,16 @@
- 跨站要求偽造 (Cross-Site Request Forgery，簡寫 CSRF/XSRF) 是一種由未經授權的第三方， - 以您的身分在網站上做事情的入侵政擊。在 Jenkins 裡，代表別人可以刪除專案、建置或修改 Jenkins 設定。 + 跨站要求偽造 (Cross-Site Request Forgery，簡寫 CSRF/XSRF) + 是一種由未經授權的第三方， 以您的身分在網站上做事情的入侵政擊。在 Jenkins + 裡，代表別人可以刪除專案、建置或修改 Jenkins 設定。

- 啟動這個選項後，Jenkins 會檢查任何可能修改 Jenkins 伺服器設定的要求，看看產生的 Nonce 值 (或叫做 "Crumb") 是否正確。 - 這類要求包含表單送出，以及呼叫遠端 API。 + 啟動這個選項後，Jenkins 會檢查任何可能修改 Jenkins + 伺服器設定的要求，看看產生的 Nonce 值 (或叫做 "Crumb") 是否正確。 + 這類要求包含表單送出，以及呼叫遠端 API。 +

+

- 您可以在這裡找到更多有關 CSRF 入侵的資訊。 + 您可以在 + 這裡 + 找到更多有關 CSRF 入侵的資訊。 +

diff --git a/core/src/main/resources/hudson/slaves/AbstractCloudImpl/help-instanceCapStr.html b/core/src/main/resources/hudson/slaves/AbstractCloudImpl/help-instanceCapStr.html index 75a258c36e..61f08729a8 100644 --- a/core/src/main/resources/hudson/slaves/AbstractCloudImpl/help-instanceCapStr.html +++ b/core/src/main/resources/hudson/slaves/AbstractCloudImpl/help-instanceCapStr.html @@ -1,13 +1,15 @@
- You can place the upward limit to the number of agents that Jenkins may launch from this cloud. - This is useful for avoiding surprises in the billing statement. + You can place the upward limit to the number of agents that Jenkins may launch + from this cloud. This is useful for avoiding surprises in the billing + statement. -

- For example, if this field is 3, Jenkins will only launch a new instance - as long as total number of instances you run on this cloud doesn't exceed this number. In this way, - even in the worst case of Jenkins starting instances and forgetting about them, - you have an upper bound in the number of instances that are concurrently executed. +

+ For example, if this field is 3, Jenkins will only launch a new instance as + long as total number of instances you run on this cloud doesn't exceed this + number. In this way, even in the worst case of Jenkins starting instances + and forgetting about them, you have an upper bound in the number of + instances that are concurrently executed. +

-

- Leave this field empty to remove a cap. +

Leave this field empty to remove a cap.

diff --git a/core/src/main/resources/hudson/slaves/AbstractCloudImpl/help-instanceCapStr_bg.html b/core/src/main/resources/hudson/slaves/AbstractCloudImpl/help-instanceCapStr_bg.html index 990f02b4d2..96b1afd2db 100644 --- a/core/src/main/resources/hudson/slaves/AbstractCloudImpl/help-instanceCapStr_bg.html +++ b/core/src/main/resources/hudson/slaves/AbstractCloudImpl/help-instanceCapStr_bg.html @@ -1,13 +1,16 @@
- Може да зададете максималният брой агенти, които Jenkins може да стартира в - облака. Така ще избегнете неприятни изненади, когато пристигне сметката - за ползваните ресурси. + Може да зададете максималният брой агенти, които Jenkins може да стартира в + облака. Така ще избегнете неприятни изненади, когато пристигне сметката за + ползваните ресурси. -

- Ако въведете 3, Jenkins ще стартира нови агенти само докато общият им брой не - надхвърли това число. Дори и в най-лошия случай да забравите да ги спрете, - има граница, която няма де се надхвърли. +

+ Ако въведете 3, Jenkins ще стартира нови агенти само докато общият им брой + не надхвърли това число. Дори и в най-лошия случай да забравите да ги + спрете, има граница, която няма де се надхвърли. +

-

- Ако полето е празно, няма никакви ограничения за използваните ресурси в този облак. +

+ Ако полето е празно, няма никакви ограничения за използваните ресурси в този + облак. +

diff --git a/core/src/main/resources/hudson/slaves/AbstractCloudImpl/help-instanceCapStr_it.html b/core/src/main/resources/hudson/slaves/AbstractCloudImpl/help-instanceCapStr_it.html index a051d67ded..d027470332 100644 --- a/core/src/main/resources/hudson/slaves/AbstractCloudImpl/help-instanceCapStr_it.html +++ b/core/src/main/resources/hudson/slaves/AbstractCloudImpl/help-instanceCapStr_it.html @@ -1,15 +1,14 @@
- È possibile fissare un limite massimo al numero di agenti che Jenkins - può avviare da questo cloud. Ciò è utile per evitare sorprese in - fattura. + È possibile fissare un limite massimo al numero di agenti che Jenkins può + avviare da questo cloud. Ciò è utile per evitare sorprese in fattura. -

+

Ad esempio, se il valore di questo campo è 3, Jenkins avvierà una nuova istanza solo se il numero totale di istanze eseguite su questo cloud non - eccede questo valore. In questo modo, anche nel caso peggiore in cui - Jenkins avvii istanze e se ne dimentichi, si ha un limite superiore al - numero di istanze eseguite concorrentemente. + eccede questo valore. In questo modo, anche nel caso peggiore in cui Jenkins + avvii istanze e se ne dimentichi, si ha un limite superiore al numero di + istanze eseguite concorrentemente. +

-

- Lasciare questo campo vuoto per rimuovere il limite. +

Lasciare questo campo vuoto per rimuovere il limite.

diff --git a/core/src/main/resources/hudson/slaves/JNLPLauncher/help-vmargs.html b/core/src/main/resources/hudson/slaves/JNLPLauncher/help-vmargs.html index 2a398539e6..ca9f969c52 100644 --- a/core/src/main/resources/hudson/slaves/JNLPLauncher/help-vmargs.html +++ b/core/src/main/resources/hudson/slaves/JNLPLauncher/help-vmargs.html @@ -1,5 +1,10 @@
- If the agent JVM should be launched with additional VM arguments, such as "-Xmx256m", - specify those here. List of all the options are available - here. -
\ No newline at end of file + If the agent JVM should be launched with additional VM arguments, such as + "-Xmx256m", specify those here. List of all the options are available + + here + + . + diff --git a/core/src/main/resources/hudson/slaves/JNLPLauncher/help-vmargs_bg.html b/core/src/main/resources/hudson/slaves/JNLPLauncher/help-vmargs_bg.html index 551c5cbb74..c34c4265ab 100644 --- a/core/src/main/resources/hudson/slaves/JNLPLauncher/help-vmargs_bg.html +++ b/core/src/main/resources/hudson/slaves/JNLPLauncher/help-vmargs_bg.html @@ -1,6 +1,11 @@
- При необходимост тук попълнете допълнителните аргументи за стартирането на - виртуалната машина на Java на подчинените компютри като „-Xmx256m“. - Погледнете документацията за - пълния списък. + При необходимост тук попълнете допълнителните аргументи за стартирането на + виртуалната машина на Java на подчинените компютри като „-Xmx256m“. Погледнете + документацията за + + пълния списък + + .
diff --git a/core/src/main/resources/hudson/slaves/JNLPLauncher/help-vmargs_fr.html b/core/src/main/resources/hudson/slaves/JNLPLauncher/help-vmargs_fr.html index ef2647a625..37cc50fb27 100644 --- a/core/src/main/resources/hudson/slaves/JNLPLauncher/help-vmargs_fr.html +++ b/core/src/main/resources/hudson/slaves/JNLPLauncher/help-vmargs_fr.html @@ -1,5 +1,11 @@
- Si la JVM agent doit être lancée avec des arguments supplémentaires, comme "-Xmx256m", - indiquez-les ici. La liste de toutes options disponibles est disponible - ici. -
\ No newline at end of file + Si la JVM agent doit être lancée avec des arguments supplémentaires, comme + "-Xmx256m", indiquez-les ici. La liste de toutes options disponibles est + disponible + + ici + + . + diff --git a/core/src/main/resources/hudson/slaves/JNLPLauncher/help-vmargs_it.html b/core/src/main/resources/hudson/slaves/JNLPLauncher/help-vmargs_it.html index 9dcbbe93bb..0cea9285b8 100644 --- a/core/src/main/resources/hudson/slaves/JNLPLauncher/help-vmargs_it.html +++ b/core/src/main/resources/hudson/slaves/JNLPLauncher/help-vmargs_it.html @@ -1,6 +1,10 @@
- Se la JVM dell'agente deve essere avviata con argomenti VM aggiuntivi, - come "-Xmx256m", specificarli qui. Un elenco con tutte le opzioni è - disponibile - qui. + Se la JVM dell'agente deve essere avviata con argomenti VM aggiuntivi, come + "-Xmx256m", specificarli qui. Un elenco con tutte le opzioni è disponibile + + qui + + .
diff --git a/core/src/main/resources/hudson/slaves/JNLPLauncher/help-vmargs_ja.html b/core/src/main/resources/hudson/slaves/JNLPLauncher/help-vmargs_ja.html index 3356babf6f..ed1fed0152 100644 --- a/core/src/main/resources/hudson/slaves/JNLPLauncher/help-vmargs_ja.html +++ b/core/src/main/resources/hudson/slaves/JNLPLauncher/help-vmargs_ja.html @@ -1,4 +1,9 @@
- エージェントのJVMに"-Xmx256m"のようなオプションをつけて起動する必要があるなら、ここで指定します。 - 利用可能なオプションの一覧を参照してください。 -
\ No newline at end of file + エージェントのJVMに"-Xmx256m"のようなオプションをつけて起動する必要があるなら、ここで指定します。 + + 利用可能なオプションの一覧 + + を参照してください。 + diff --git a/core/src/main/resources/hudson/slaves/JNLPLauncher/help-webSocket.html b/core/src/main/resources/hudson/slaves/JNLPLauncher/help-webSocket.html index 35c5bdadab..0243741733 100644 --- a/core/src/main/resources/hudson/slaves/JNLPLauncher/help-webSocket.html +++ b/core/src/main/resources/hudson/slaves/JNLPLauncher/help-webSocket.html @@ -1,4 +1,5 @@
- Use WebSocket to connect to the Jenkins master rather than the TCP port. - See JEP-222 for background. + Use WebSocket to connect to the Jenkins master rather than the TCP port. See + JEP-222 + for background.
diff --git a/core/src/main/resources/hudson/slaves/JNLPLauncher/help-webSocket_it.html b/core/src/main/resources/hudson/slaves/JNLPLauncher/help-webSocket_it.html index 3a44359ce9..f18a700d2b 100644 --- a/core/src/main/resources/hudson/slaves/JNLPLauncher/help-webSocket_it.html +++ b/core/src/main/resources/hudson/slaves/JNLPLauncher/help-webSocket_it.html @@ -1,5 +1,6 @@
- Utilizza WebSocket per connettersi al master Jenkins anziché una porta - TCP. Si veda JEP-222 per il - contesto. + Utilizza WebSocket per connettersi al master Jenkins anziché una porta TCP. Si + veda + JEP-222 + per il contesto.
diff --git a/core/src/main/resources/hudson/tasks/ArtifactArchiver/help-allowEmptyArchive.html b/core/src/main/resources/hudson/tasks/ArtifactArchiver/help-allowEmptyArchive.html index 2c97f795e4..e0989d9a95 100644 --- a/core/src/main/resources/hudson/tasks/ArtifactArchiver/help-allowEmptyArchive.html +++ b/core/src/main/resources/hudson/tasks/ArtifactArchiver/help-allowEmptyArchive.html @@ -1,5 +1,5 @@
- Normally, a build fails if archiving returns zero artifacts. - This option allows the archiving process to return nothing without failing the build. - Instead, the build will simply throw a warning. -
\ No newline at end of file + Normally, a build fails if archiving returns zero artifacts. This option + allows the archiving process to return nothing without failing the build. + Instead, the build will simply throw a warning. + diff --git a/core/src/main/resources/hudson/tasks/ArtifactArchiver/help-allowEmptyArchive_bg.html b/core/src/main/resources/hudson/tasks/ArtifactArchiver/help-allowEmptyArchive_bg.html index b909b753f7..7eef61ac47 100644 --- a/core/src/main/resources/hudson/tasks/ArtifactArchiver/help-allowEmptyArchive_bg.html +++ b/core/src/main/resources/hudson/tasks/ArtifactArchiver/help-allowEmptyArchive_bg.html @@ -1,6 +1,5 @@
- Обичайно изграждане, при което отсъстват обектите за архивиране, се - обявява за неуспешно. Ако изберете тази опция, отсъствието на - обекти за архивиране ще доведе само до предупреждение, изграждането - ще се третира като успешно. + Обичайно изграждане, при което отсъстват обектите за архивиране, се обявява за + неуспешно. Ако изберете тази опция, отсъствието на обекти за архивиране ще + доведе само до предупреждение, изграждането ще се третира като успешно.
diff --git a/core/src/main/resources/hudson/tasks/ArtifactArchiver/help-allowEmptyArchive_it.html b/core/src/main/resources/hudson/tasks/ArtifactArchiver/help-allowEmptyArchive_it.html index 84db9bdf1a..b7e1f92670 100644 --- a/core/src/main/resources/hudson/tasks/ArtifactArchiver/help-allowEmptyArchive_it.html +++ b/core/src/main/resources/hudson/tasks/ArtifactArchiver/help-allowEmptyArchive_it.html @@ -1,7 +1,6 @@
- Normalmente, una compilazione fallisce se il passaggio di archiviazione non - restituisce alcun artefatto. Quest'opzione consente al processo di - archiviazione di non restituire nulla senza far terminare la compilazione - con un errore. La compilazione, in tal caso, restituirà semplicemente un - avviso. + Normalmente, una compilazione fallisce se il passaggio di archiviazione non + restituisce alcun artefatto. Quest'opzione consente al processo di + archiviazione di non restituire nulla senza far terminare la compilazione con + un errore. La compilazione, in tal caso, restituirà semplicemente un avviso.
diff --git a/core/src/main/resources/hudson/tasks/ArtifactArchiver/help-allowEmptyArchive_zh_TW.html b/core/src/main/resources/hudson/tasks/ArtifactArchiver/help-allowEmptyArchive_zh_TW.html index b51c974150..1ef022109c 100644 --- a/core/src/main/resources/hudson/tasks/ArtifactArchiver/help-allowEmptyArchive_zh_TW.html +++ b/core/src/main/resources/hudson/tasks/ArtifactArchiver/help-allowEmptyArchive_zh_TW.html @@ -1,4 +1,4 @@
- 一般情況下，如果建置沒有任何檔案可以封存，就算失敗。 - 這個選項能讓封存程序就算沒有封存到任何檔案，也不要將建置標為失敗，只會單純的丟出警告訊息。 -
\ No newline at end of file + 一般情況下，如果建置沒有任何檔案可以封存，就算失敗。 + 這個選項能讓封存程序就算沒有封存到任何檔案，也不要將建置標為失敗，只會單純的丟出警告訊息。 + diff --git a/core/src/main/resources/hudson/tasks/ArtifactArchiver/help-artifacts.html b/core/src/main/resources/hudson/tasks/ArtifactArchiver/help-artifacts.html index 4dd95467fc..adfc24f409 100644 --- a/core/src/main/resources/hudson/tasks/ArtifactArchiver/help-artifacts.html +++ b/core/src/main/resources/hudson/tasks/ArtifactArchiver/help-artifacts.html @@ -1,31 +1,37 @@
- You can use wildcards like 'module/dist/**/*.zip'. - See - the includes attribute of Ant fileset for the exact format - -- except that "," (comma) is the only supported separator. - The base directory is the workspace. - You can only archive files that are located in your workspace. + You can use wildcards like 'module/dist/**/*.zip'. See + + the includes attribute of Ant fileset + + for the exact format -- except that + "," + ( + comma + ) is the only supported separator. The base directory is + the workspace + . You can only archive files that are located in your workspace.
-
+
-

Here are some examples of usage for pipeline:

-
    -
  • How to archive multiple artifacts from a specific folder: +

    Here are some examples of usage for pipeline:

    +
      +
    • + How to archive multiple artifacts from a specific folder: - 
      archiveArtifacts artifacts: 'target/*.jar'
      -
      • -
      - -
    • How to archive multiple artifacts with different patterns: - 
      archiveArtifacts artifacts: 'target/*.jar, target/*.war'
      -
      • -
      -
    • - How to archive multiple nested artifacts: - 
      archiveArtifacts artifacts: '**/*.jar'
      -
      • -
      -
    + 
    archiveArtifacts artifacts: 'target/*.jar'
    +
    • +
    +
  • + How to archive multiple artifacts with different patterns: + 
    archiveArtifacts artifacts: 'target/*.jar, target/*.war'
    +
    • +
    +
  • + How to archive multiple nested artifacts: + 
    archiveArtifacts artifacts: '**/*.jar'
    +
    • +
    +
diff --git a/core/src/main/resources/hudson/tasks/ArtifactArchiver/help-artifacts_bg.html b/core/src/main/resources/hudson/tasks/ArtifactArchiver/help-artifacts_bg.html index 27b8ea31ce..ac0c6369c1 100644 --- a/core/src/main/resources/hudson/tasks/ArtifactArchiver/help-artifacts_bg.html +++ b/core/src/main/resources/hudson/tasks/ArtifactArchiver/help-artifacts_bg.html @@ -1,8 +1,10 @@
- Можете да използвате шаблонни знаци като „module/dist/**/*.zip“. - За точния формат погледнете - документацията - на атрибута „includes“ за наборите от файлове на Ant. Базовата - директория е работното пространство. Можете да - архивирате само файлове, които се съдържат в него. + Можете да използвате шаблонни знаци като „module/dist/**/*.zip“. За точния + формат погледнете + + документацията на атрибута „includes“ за наборите от файлове на Ant + + . Базовата директория е + работното пространство + . Можете да архивирате само файлове, които се съдържат в него.
diff --git a/core/src/main/resources/hudson/tasks/ArtifactArchiver/help-artifacts_de.html b/core/src/main/resources/hudson/tasks/ArtifactArchiver/help-artifacts_de.html index e3c93fbf31..0a814f283d 100644 --- a/core/src/main/resources/hudson/tasks/ArtifactArchiver/help-artifacts_de.html +++ b/core/src/main/resources/hudson/tasks/ArtifactArchiver/help-artifacts_de.html @@ -1,7 +1,10 @@
- Sie können Platzhalterzeichen verwenden wie z.B. 'module/dist/**/*.zip'. - Das unterstützte Format entspricht der Angabe des - includes-Attributes eines Ant FileSets. - Das Basisverzeichnis ist der Arbeitsbereich. - Sie können nur Dateien archivieren, die im Arbeitsbereich liegen. -
\ No newline at end of file + Sie können Platzhalterzeichen verwenden wie z.B. 'module/dist/**/*.zip'. Das + unterstützte Format entspricht der Angabe des + + includes-Attributes eines Ant FileSets + + . Das Basisverzeichnis ist der + Arbeitsbereich + . Sie können nur Dateien archivieren, die im Arbeitsbereich liegen. + diff --git a/core/src/main/resources/hudson/tasks/ArtifactArchiver/help-artifacts_fr.html b/core/src/main/resources/hudson/tasks/ArtifactArchiver/help-artifacts_fr.html index db7ac4cb7a..8076381e55 100644 --- a/core/src/main/resources/hudson/tasks/ArtifactArchiver/help-artifacts_fr.html +++ b/core/src/main/resources/hudson/tasks/ArtifactArchiver/help-artifacts_fr.html @@ -1,6 +1,9 @@ 
- Vous pouvez utilisez ici des wildcards du type 'module/dist/**/*.zip'. - Voir - les @includes d'un fileset Ant pour le format exact. - Le répertoire de base est le workspace. -
\ No newline at end of file + Vous pouvez utilisez ici des wildcards du type 'module/dist/**/*.zip'. Voir + + les @includes d'un fileset Ant + + pour le format exact. Le répertoire de base est + le workspace + . + diff --git a/core/src/main/resources/hudson/tasks/ArtifactArchiver/help-artifacts_it.html b/core/src/main/resources/hudson/tasks/ArtifactArchiver/help-artifacts_it.html index e5c10c1eb3..7cd861ac2d 100644 --- a/core/src/main/resources/hudson/tasks/ArtifactArchiver/help-artifacts_it.html +++ b/core/src/main/resources/hudson/tasks/ArtifactArchiver/help-artifacts_it.html @@ -1,10 +1,14 @@
- È possibile utilizzare caratteri jolly come 'module/dist/**/*.zip'. - Si veda - l'attributo includes dei fileset Ant per il formato esatto; come - eccezione, "," (la virgola) è l'unico separatore - supportato. - La directory di base è lo spazio di lavoro. - È possibile archiviare solamente i file situati nel proprio spazio di - lavoro. + È possibile utilizzare caratteri jolly come 'module/dist/**/*.zip'. Si veda + + l'attributo includes dei fileset Ant + + per il formato esatto; come eccezione, + "," + (la + virgola + ) è l'unico separatore supportato. La directory di base è + lo spazio di lavoro + . È possibile archiviare solamente i file situati nel proprio spazio di + lavoro.
diff --git a/core/src/main/resources/hudson/tasks/ArtifactArchiver/help-artifacts_ja.html b/core/src/main/resources/hudson/tasks/ArtifactArchiver/help-artifacts_ja.html index d7ab805472..38d4ad9894 100644 --- a/core/src/main/resources/hudson/tasks/ArtifactArchiver/help-artifacts_ja.html +++ b/core/src/main/resources/hudson/tasks/ArtifactArchiver/help-artifacts_ja.html @@ -1,6 +1,10 @@
- ワイルドカードを使用できます(例 'module/dist/**/*.zip')。正確な形式については、 - - includes属性(Antのファイルセット)を参考にしてください。 - 基準となるディレクトリは、ワークスペースです。 -
\ No newline at end of file + ワイルドカードを使用できます(例 + 'module/dist/**/*.zip')。正確な形式については、 + + includes属性(Antのファイルセット) + + を参考にしてください。 基準となるディレクトリは、 + ワークスペース + です。 + diff --git a/core/src/main/resources/hudson/tasks/ArtifactArchiver/help-artifacts_nl.html b/core/src/main/resources/hudson/tasks/ArtifactArchiver/help-artifacts_nl.html index 0dcef9278e..ae6a15b1cd 100644 --- a/core/src/main/resources/hudson/tasks/ArtifactArchiver/help-artifacts_nl.html +++ b/core/src/main/resources/hudson/tasks/ArtifactArchiver/help-artifacts_nl.html @@ -1,7 +1,9 @@
- U kunt jokercharacter gebruiken, vb. 'module/dist/**/*.zip'. - Zie - de @includes in een Ant 'fileset' voor meer informatie over het exacte - formaat. - De basisfolder is de werkplaats. -
\ No newline at end of file + U kunt jokercharacter gebruiken, vb. 'module/dist/**/*.zip'. Zie + + de @includes in een Ant 'fileset' + + voor meer informatie over het exacte formaat. De basisfolder is + de werkplaats + . + diff --git a/core/src/main/resources/hudson/tasks/ArtifactArchiver/help-artifacts_pt_BR.html b/core/src/main/resources/hudson/tasks/ArtifactArchiver/help-artifacts_pt_BR.html index 1dc0a30e46..2031fed583 100644 --- a/core/src/main/resources/hudson/tasks/ArtifactArchiver/help-artifacts_pt_BR.html +++ b/core/src/main/resources/hudson/tasks/ArtifactArchiver/help-artifacts_pt_BR.html @@ -1,7 +1,9 @@
- Pode usar coringas como 'module/dist/**/*.zip'. - Veja - o @includes do fileset do Ant para o formato exato. - O diretório base é o workspace. + Pode usar coringas como 'module/dist/**/*.zip'. Veja + + o @includes do fileset do Ant + + para o formato exato. O diretório base é + o workspace + .
- diff --git a/core/src/main/resources/hudson/tasks/ArtifactArchiver/help-artifacts_ru.html b/core/src/main/resources/hudson/tasks/ArtifactArchiver/help-artifacts_ru.html index a1bb677a68..d184d9356d 100644 --- a/core/src/main/resources/hudson/tasks/ArtifactArchiver/help-artifacts_ru.html +++ b/core/src/main/resources/hudson/tasks/ArtifactArchiver/help-artifacts_ru.html @@ -1,6 +1,9 @@ 
- Возможно использование масок вида 'module/dist/**/*.zip'. - Смотрите - @includes из Ant для полной документации о синтаксисе. - Текущей директориея является сборочная директория. -
\ No newline at end of file + Возможно использование масок вида 'module/dist/**/*.zip'. Смотрите + + @includes из Ant + + для полной документации о синтаксисе. Текущей директориея является + сборочная директория + . + diff --git a/core/src/main/resources/hudson/tasks/ArtifactArchiver/help-artifacts_tr.html b/core/src/main/resources/hudson/tasks/ArtifactArchiver/help-artifacts_tr.html index fe2587718c..fe58e6061c 100644 --- a/core/src/main/resources/hudson/tasks/ArtifactArchiver/help-artifacts_tr.html +++ b/core/src/main/resources/hudson/tasks/ArtifactArchiver/help-artifacts_tr.html @@ -1,6 +1,10 @@
- 'module/dist/**/*.zip' gibi joker kalıpları kullanabilirsiniz. - Yardım için, - the @includes of Ant fileset linkine bakın. - Temel dizin çalışma alanıdır. -
\ No newline at end of file + 'module/dist/**/*.zip' gibi joker kalıpları kullanabilirsiniz. + Yardım için, + + the @includes of Ant fileset + + linkine bakın. Temel dizin + çalışma alanı + dır. + diff --git a/core/src/main/resources/hudson/tasks/ArtifactArchiver/help-artifacts_zh_TW.html b/core/src/main/resources/hudson/tasks/ArtifactArchiver/help-artifacts_zh_TW.html index 849a21e649..edc619112d 100644 --- a/core/src/main/resources/hudson/tasks/ArtifactArchiver/help-artifacts_zh_TW.html +++ b/core/src/main/resources/hudson/tasks/ArtifactArchiver/help-artifacts_zh_TW.html @@ -1,5 +1,9 @@
- 可以像 "module/dist/**/*.zip" 這樣使用萬用字元。 - 確切格式可以參考 Ant fileset 的 @includes。 - 工作目錄就是工作區目錄。 -
\ No newline at end of file + 可以像 "module/dist/**/*.zip" 這樣使用萬用字元。 確切格式可以參考 + + Ant fileset 的 @includes + + 。 工作目錄就是 + 工作區目錄 + 。 + diff --git a/core/src/main/resources/hudson/tasks/ArtifactArchiver/help-caseSensitive.html b/core/src/main/resources/hudson/tasks/ArtifactArchiver/help-caseSensitive.html index 4d8200d063..5ae3efd2f1 100644 --- a/core/src/main/resources/hudson/tasks/ArtifactArchiver/help-caseSensitive.html +++ b/core/src/main/resources/hudson/tasks/ArtifactArchiver/help-caseSensitive.html @@ -1,5 +1,11 @@
- Artifact archiver uses Ant org.apache.tools.ant.DirectoryScanner which by default is case sensitive. - For instance, if the job produces *.hpi files, pattern "**/*.HPI" will fail to find them.

- This option can be used to disable case sensitivity. When it's unchecked, pattern "**/*.HPI" will match any *.hpi files, or pattern "**/cAsEsEnSiTiVe.jar" will match a file called caseSensitive.jar. -
\ No newline at end of file + Artifact archiver uses Ant + org.apache.tools.ant.DirectoryScanner + which by default is case sensitive. For instance, if the job produces *.hpi + files, pattern "**/*.HPI" will fail to find them. +
+
+ This option can be used to disable case sensitivity. When it's unchecked, + pattern "**/*.HPI" will match any *.hpi files, or pattern + "**/cAsEsEnSiTiVe.jar" will match a file called caseSensitive.jar. + diff --git a/core/src/main/resources/hudson/tasks/ArtifactArchiver/help-caseSensitive_bg.html b/core/src/main/resources/hudson/tasks/ArtifactArchiver/help-caseSensitive_bg.html index 0df67079cc..d45632ce39 100644 --- a/core/src/main/resources/hudson/tasks/ArtifactArchiver/help-caseSensitive_bg.html +++ b/core/src/main/resources/hudson/tasks/ArtifactArchiver/help-caseSensitive_bg.html @@ -1,8 +1,13 @@
- Архивирането на артефакти използва org.apache.tools.ant.DirectoryScanner - на Ant. Стандартно този инструмент различава главни и малки букви — ако задачата - създава файлове с разширение „.hpi“, шаблонът „**/*.HPI“ ще ги прескочи.

- Различаването на регистъра на буквите може да се изключи с тази опция. Когато тя - не е избрана, шаблонът „**/*.HPI“ ще напасва и файлове с разширение „*.hpi“, а - шаблонът „**/cAsEsEnSiTiVe.jar“ ще напасне и с файла „caseSensitive.jar“. + Архивирането на артефакти използва + org.apache.tools.ant.DirectoryScanner + на Ant. Стандартно този инструмент различава главни и малки букви — ако + задачата създава файлове с разширение „.hpi“, шаблонът „**/*.HPI“ ще ги + прескочи. +
+
+ Различаването на регистъра на буквите може да се изключи с тази опция. Когато + тя не е избрана, шаблонът „**/*.HPI“ ще напасва и файлове с разширение + „*.hpi“, а шаблонът „**/cAsEsEnSiTiVe.jar“ ще напасне и с файла + „caseSensitive.jar“.
diff --git a/core/src/main/resources/hudson/tasks/ArtifactArchiver/help-caseSensitive_it.html b/core/src/main/resources/hudson/tasks/ArtifactArchiver/help-caseSensitive_it.html index c1b0e8c3c5..2c710b4c25 100644 --- a/core/src/main/resources/hudson/tasks/ArtifactArchiver/help-caseSensitive_it.html +++ b/core/src/main/resources/hudson/tasks/ArtifactArchiver/help-caseSensitive_it.html @@ -1,12 +1,14 @@
- Il componente di archiviazione degli artefatti utilizza la classe - org.apache.tools.ant.DirectoryScanner di Ant che, per - impostazione predefinita, fa differenza tra maiuscole e minuscole. - Ad esempio, se il processo produce file *.hpi, il pattern "**/*.HPI" non - riuscirà a rilevarli.

- Quest'opzione può essere utilizzata per disattivare il rilevamento della - differenza fra maiuscole e minuscole. Quando è deselezionata, il - pattern "**/*.HPI" corrisponderà a tutti i file *.hpi, e il pattern - "**/mAiUsColeMiNuScOlE.jar" corrisponderà a un file di nome - maiuscoleMinuscole.jar. + Il componente di archiviazione degli artefatti utilizza la classe + org.apache.tools.ant.DirectoryScanner + di Ant che, per impostazione predefinita, fa differenza tra maiuscole e + minuscole. Ad esempio, se il processo produce file *.hpi, il pattern + "**/*.HPI" non riuscirà a rilevarli. +
+
+ Quest'opzione può essere utilizzata per disattivare il rilevamento della + differenza fra maiuscole e minuscole. Quando è deselezionata, il pattern + "**/*.HPI" corrisponderà a tutti i file *.hpi, e il pattern + "**/mAiUsColeMiNuScOlE.jar" corrisponderà a un file di nome + maiuscoleMinuscole.jar.
diff --git a/core/src/main/resources/hudson/tasks/ArtifactArchiver/help-excludes.html b/core/src/main/resources/hudson/tasks/ArtifactArchiver/help-excludes.html index 95963b82ae..d2a6d915dd 100644 --- a/core/src/main/resources/hudson/tasks/ArtifactArchiver/help-excludes.html +++ b/core/src/main/resources/hudson/tasks/ArtifactArchiver/help-excludes.html @@ -1,5 +1,5 @@
- Optionally specify the 'excludes' pattern, such as "foo/bar/**/*". Use "," to set a list of patterns. - A file that matches this mask will not be archived even if it matches the - mask specified in 'files to archive' section. + Optionally specify the 'excludes' pattern, such as "foo/bar/**/*". Use "," to + set a list of patterns. A file that matches this mask will not be archived + even if it matches the mask specified in 'files to archive' section.
diff --git a/core/src/main/resources/hudson/tasks/ArtifactArchiver/help-excludes_bg.html b/core/src/main/resources/hudson/tasks/ArtifactArchiver/help-excludes_bg.html index fa95de1e1b..bb277048e3 100644 --- a/core/src/main/resources/hudson/tasks/ArtifactArchiver/help-excludes_bg.html +++ b/core/src/main/resources/hudson/tasks/ArtifactArchiver/help-excludes_bg.html @@ -1,6 +1,8 @@
Допълнително може да укажете - изключващ шаблон „excludes“, - като „foo/bar/**/*“. Файл, който отговаря на такъв шаблон, няма да бъде архивиран, дори - и да напасва шаблона указан във файловете за архивиране. + + изключващ шаблон „excludes“ + + , като „foo/bar/**/*“. Файл, който отговаря на такъв шаблон, няма да бъде + архивиран, дори и да напасва шаблона указан във файловете за архивиране.
diff --git a/core/src/main/resources/hudson/tasks/ArtifactArchiver/help-excludes_de.html b/core/src/main/resources/hudson/tasks/ArtifactArchiver/help-excludes_de.html index 7f57ccbd01..ddae480580 100644 --- a/core/src/main/resources/hudson/tasks/ArtifactArchiver/help-excludes_de.html +++ b/core/src/main/resources/hudson/tasks/ArtifactArchiver/help-excludes_de.html @@ -1,6 +1,7 @@
- Optional: Geben Sie ein - Ausschlußmuster an, z.B. "foo/bar/**/*". Eine Datei, welche dieses - Muster erfüllt, wird nicht archiviert - selbst wenn sie das Muster erfüllt, - das unter "Zu archivierende Dateien" angegeben wurde. -
\ No newline at end of file + Optional: Geben Sie ein + Ausschlußmuster + an, z.B. "foo/bar/**/*". Eine Datei, welche dieses Muster erfüllt, wird nicht + archiviert - selbst wenn sie das Muster erfüllt, das unter "Zu archivierende + Dateien" angegeben wurde. + diff --git a/core/src/main/resources/hudson/tasks/ArtifactArchiver/help-excludes_fr.html b/core/src/main/resources/hudson/tasks/ArtifactArchiver/help-excludes_fr.html index 9ae3c4db7b..b68a4ed662 100644 --- a/core/src/main/resources/hudson/tasks/ArtifactArchiver/help-excludes_fr.html +++ b/core/src/main/resources/hudson/tasks/ArtifactArchiver/help-excludes_fr.html @@ -1,5 +1,9 @@ 
- Spécifie un pattern d'exclusion optionel, du type "foo/bar/**/*". - Un fichier qui correspond à ce pattern ne sera pas archivé, même s'il - correspond au masque spécifié dans la section 'fichiers à archiver'. -
\ No newline at end of file + Spécifie + + un pattern d'exclusion + + optionel, du type "foo/bar/**/*". Un fichier qui correspond à ce pattern ne + sera pas archivé, même s'il correspond au masque spécifié dans la section + 'fichiers à archiver'. + diff --git a/core/src/main/resources/hudson/tasks/ArtifactArchiver/help-excludes_it.html b/core/src/main/resources/hudson/tasks/ArtifactArchiver/help-excludes_it.html index 911e5a93e1..35787c65d1 100644 --- a/core/src/main/resources/hudson/tasks/ArtifactArchiver/help-excludes_it.html +++ b/core/src/main/resources/hudson/tasks/ArtifactArchiver/help-excludes_it.html @@ -1,6 +1,9 @@
- Specificare facoltativamente il pattern 'excludes', - ad esempio "pippo/pluto/**/*". Un file corrispondente a questa maschera non + Specificare facoltativamente + + il pattern 'excludes' + + , ad esempio "pippo/pluto/**/*". Un file corrispondente a questa maschera non sarà archiviato anche nel caso in cui corrisponda alla maschera specificata nella sezione "File da archiviare".
diff --git a/core/src/main/resources/hudson/tasks/ArtifactArchiver/help-excludes_ja.html b/core/src/main/resources/hudson/tasks/ArtifactArchiver/help-excludes_ja.html index 9f26656e34..430fca34db 100644 --- a/core/src/main/resources/hudson/tasks/ArtifactArchiver/help-excludes_ja.html +++ b/core/src/main/resources/hudson/tasks/ArtifactArchiver/help-excludes_ja.html @@ -1,4 +1,7 @@
- '除外'するパターンを指定します(例 "foo/bar/**/*")。 + + '除外'するパターン + + を指定します(例 "foo/bar/**/*")。 このマスクに一致するファイルは、'保存するファイル'で指定したマスクに一致していても、アーカイブされません。 -
\ No newline at end of file + diff --git a/core/src/main/resources/hudson/tasks/ArtifactArchiver/help-excludes_nl.html b/core/src/main/resources/hudson/tasks/ArtifactArchiver/help-excludes_nl.html index 2ce9fe30ab..362eb56cc3 100644 --- a/core/src/main/resources/hudson/tasks/ArtifactArchiver/help-excludes_nl.html +++ b/core/src/main/resources/hudson/tasks/ArtifactArchiver/help-excludes_nl.html @@ -1,6 +1,9 @@
- Optioneel kunt u een - uitsluitingspatroon zoals 'foo/bar/**/*' opgeven. Een bestand dat voldoet - aan dit patroon zal niet mee gearchiveerd worden. Dit zelfs wanneer het bestand - voldoet aan het patroon opgegeven in de sectie 'Te archiveren bestanden'. -
\ No newline at end of file + Optioneel kunt u een + + uitsluitingspatroon + + zoals 'foo/bar/**/*' opgeven. Een bestand dat voldoet aan dit patroon zal niet + mee gearchiveerd worden. Dit zelfs wanneer het bestand voldoet aan het patroon + opgegeven in de sectie 'Te archiveren bestanden'. + diff --git a/core/src/main/resources/hudson/tasks/ArtifactArchiver/help-excludes_pt_BR.html b/core/src/main/resources/hudson/tasks/ArtifactArchiver/help-excludes_pt_BR.html index e8c2e6cbe7..d3caffb720 100644 --- a/core/src/main/resources/hudson/tasks/ArtifactArchiver/help-excludes_pt_BR.html +++ b/core/src/main/resources/hudson/tasks/ArtifactArchiver/help-excludes_pt_BR.html @@ -1,5 +1,9 @@
- Opcionalmente especifique o padrão de 'exclusão', - tal como "foo/bar/**/*". Um arquivo que se enquadre nesta máscara não será arquivado mesmo se ele se enquadrar - na máscara especificada na seção 'arquivos para arquivar'. + Opcionalmente especifique + + o padrão de 'exclusão' + + , tal como "foo/bar/**/*". Um arquivo que se enquadre nesta máscara + não será arquivado mesmo se ele se enquadrar na máscara + especificada na seção 'arquivos para arquivar'.
diff --git a/core/src/main/resources/hudson/tasks/ArtifactArchiver/help-excludes_ru.html b/core/src/main/resources/hudson/tasks/ArtifactArchiver/help-excludes_ru.html index acf7f4dd68..e18af97e15 100644 --- a/core/src/main/resources/hudson/tasks/ArtifactArchiver/help-excludes_ru.html +++ b/core/src/main/resources/hudson/tasks/ArtifactArchiver/help-excludes_ru.html @@ -1,5 +1,9 @@ 
- Опционально укажите шаблон 'исключений' - в виде "foo/bar/**/*". Файл, соответствующий этой маске заархивирован не будет, даже если он - соответствует маске, указанной в поле "Файлы для архивации". -
\ No newline at end of file + Опционально укажите + + шаблон 'исключений' + + в виде "foo/bar/**/*". Файл, соответствующий этой маске заархивирован не + будет, даже если он соответствует маске, указанной в поле "Файлы для + архивации". + diff --git a/core/src/main/resources/hudson/tasks/ArtifactArchiver/help-excludes_tr.html b/core/src/main/resources/hudson/tasks/ArtifactArchiver/help-excludes_tr.html index d04b908fba..da80a58e7a 100644 --- a/core/src/main/resources/hudson/tasks/ArtifactArchiver/help-excludes_tr.html +++ b/core/src/main/resources/hudson/tasks/ArtifactArchiver/help-excludes_tr.html @@ -1,6 +1,9 @@
- Opsiyonel olarak, "foo/bar/**/*" gibi - bir 'excludes' kalıbı - tanımlayabilirsiniz. Bu kalıp ile eşleşen dosyalar, 'arşivlenecek dosyalar' kısmında belirtilse dahi, + Opsiyonel olarak, "foo/bar/**/*" gibi bir + + 'excludes' kalıbı + + tanımlayabilirsiniz. Bu kalıp ile eşleşen dosyalar, + 'arşivlenecek dosyalar' kısmında belirtilse dahi, arşivlenmeyecektir. -
\ No newline at end of file + diff --git a/core/src/main/resources/hudson/tasks/ArtifactArchiver/help-excludes_zh_TW.html b/core/src/main/resources/hudson/tasks/ArtifactArchiver/help-excludes_zh_TW.html index 9efb599144..6149d080d3 100644 --- a/core/src/main/resources/hudson/tasks/ArtifactArchiver/help-excludes_zh_TW.html +++ b/core/src/main/resources/hudson/tasks/ArtifactArchiver/help-excludes_zh_TW.html @@ -1,4 +1,6 @@
- 還可以指定 "excludes" 樣式，例如 "foo/bar/**/*"。 + 還可以指定 + "excludes" 樣式 + ，例如 "foo/bar/**/*"。 符合樣式的檔案不會被封存，就算符合「要封存的檔案」設定也一樣。 -
\ No newline at end of file + diff --git a/core/src/main/resources/hudson/tasks/ArtifactArchiver/help-followSymlinks.html b/core/src/main/resources/hudson/tasks/ArtifactArchiver/help-followSymlinks.html index 597070c6e4..c4eeab186c 100644 --- a/core/src/main/resources/hudson/tasks/ArtifactArchiver/help-followSymlinks.html +++ b/core/src/main/resources/hudson/tasks/ArtifactArchiver/help-followSymlinks.html @@ -1,4 +1,4 @@
- By disabling this option all symbolic links found in the workspace will be ignored. + By disabling this option all symbolic links found in the workspace will be + ignored.
- diff --git a/core/src/main/resources/hudson/tasks/ArtifactArchiver/help-followSymlinks_de.html b/core/src/main/resources/hudson/tasks/ArtifactArchiver/help-followSymlinks_de.html index e7ce7d32a7..61a82d4435 100644 --- a/core/src/main/resources/hudson/tasks/ArtifactArchiver/help-followSymlinks_de.html +++ b/core/src/main/resources/hudson/tasks/ArtifactArchiver/help-followSymlinks_de.html @@ -1,4 +1,4 @@
- Durch Abschalten dieser Option werden sämtliche symbolische Links im Arbeitsbereich ignoriert. + Durch Abschalten dieser Option werden sämtliche symbolische Links im + Arbeitsbereich ignoriert.
- diff --git a/core/src/main/resources/hudson/tasks/ArtifactArchiver/help-followSymlinks_it.html b/core/src/main/resources/hudson/tasks/ArtifactArchiver/help-followSymlinks_it.html index 0f4a0eb63a..9ac2259218 100644 --- a/core/src/main/resources/hudson/tasks/ArtifactArchiver/help-followSymlinks_it.html +++ b/core/src/main/resources/hudson/tasks/ArtifactArchiver/help-followSymlinks_it.html @@ -1,5 +1,4 @@
- Disabilitando quest'opzione tutti i collegamenti simbolici trovati nello - spazio di lavoro saranno ignorati. + Disabilitando quest'opzione tutti i collegamenti simbolici trovati nello + spazio di lavoro saranno ignorati.
- diff --git a/core/src/main/resources/hudson/tasks/ArtifactArchiver/help.html b/core/src/main/resources/hudson/tasks/ArtifactArchiver/help.html index 25428c527b..62f2a1dfca 100644 --- a/core/src/main/resources/hudson/tasks/ArtifactArchiver/help.html +++ b/core/src/main/resources/hudson/tasks/ArtifactArchiver/help.html @@ -1,24 +1,33 @@
- Archives the build artifacts (for example, distribution zip files or jar files) - so that they can be downloaded later. - Archived files will be accessible from the Jenkins webpage. + Archives the build artifacts (for example, distribution zip files or jar + files) so that they can be downloaded later. Archived files will be accessible + from the Jenkins webpage.
- Normally, Jenkins keeps artifacts for a build as long as a build log itself is kept, - but if you don't need old artifacts and would rather save disk space, you can do so. + Normally, Jenkins keeps artifacts for a build as long as a build log itself is + kept, but if you don't need old artifacts and would rather save disk space, + you can do so.
-
+
-Note that the Maven job type automatically archives any produced Maven artifacts. -Any artifacts configured here will be archived on top of that. -Automatic artifact archiving can be disabled under the advanced Maven options. + Note that the Maven job type automatically archives any produced Maven + artifacts. Any artifacts configured here will be archived on top of that. + Automatic artifact archiving can be disabled under the advanced Maven options.
-
+
- The Pipeline Snippet Generator generates this example - when all arguments are set to true (some arguments by default are true): -
archiveArtifacts artifacts: '**/*.txt',
+  The
+  
+    Pipeline Snippet Generator
+  
+  generates this example when all arguments are set to true (some arguments by
+  default are true):
+  
archiveArtifacts artifacts: '**/*.txt',
                    allowEmptyArchive: true,
                    fingerprint: true,
                    onlyIfSuccessful: true
diff --git a/core/src/main/resources/hudson/tasks/ArtifactArchiver/help_bg.html b/core/src/main/resources/hudson/tasks/ArtifactArchiver/help_bg.html
index ffdf118007..437846b186 100644
--- a/core/src/main/resources/hudson/tasks/ArtifactArchiver/help_bg.html
+++ b/core/src/main/resources/hudson/tasks/ArtifactArchiver/help_bg.html
@@ -1,15 +1,16 @@
 

   Архивиране на изградените артефакти (напр. разпространяваните или публикувани
-  файлове), така че да могат да бъдат изтеглени по-късно.  Те ще са достъпни от
+  файлове), така че да могат да бъдат изтеглени по-късно. Те ще са достъпни от
   страницата на Jenkins.
   

   Обичайно Jenkins пази изградените обекти докато се пазят журналните записи за
-  самото изграждане.  Ако старите артефакти не ви трябват и предпочитате да имате
+  самото изграждане. Ако старите артефакти не ви трябват и предпочитате да имате
   повече дисково пространство, може да укажете това.
 

-

+

 

-Забележете, че при задача с Maven, създадените артефакти се архивират автоматично.
-Обектите, които настроите тук, се добавят към горните. Автоматичното архивиране
-на Maven може да се изключи от допълнителните настройки на Maven.
+  Забележете, че при задача с Maven, създадените артефакти се архивират
+  автоматично. Обектите, които настроите тук, се добавят към горните.
+  Автоматичното архивиране на Maven може да се изключи от допълнителните
+  настройки на Maven.
 

diff --git a/core/src/main/resources/hudson/tasks/ArtifactArchiver/help_de.html b/core/src/main/resources/hudson/tasks/ArtifactArchiver/help_de.html
index 3676704431..cf3b46ec0d 100644
--- a/core/src/main/resources/hudson/tasks/ArtifactArchiver/help_de.html
+++ b/core/src/main/resources/hudson/tasks/ArtifactArchiver/help_de.html
@@ -1,16 +1,17 @@
 

   Archiviert die Build-Artefakte (zum Beispiel ZIP- oder JAR-Dateien), so dass
-  diese zu einem späteren Zeitpunkt heruntergeladen werden können.
-  Archivierte Dateien sind über die Jenkins Web-Oberfläche erreichbar.
+  diese zu einem späteren Zeitpunkt heruntergeladen werden können. Archivierte
+  Dateien sind über die Jenkins Web-Oberfläche erreichbar.
   

   Normalerweise bewahrt Jenkins die Artefakte eines Builds so lange auf, wie die
-  Protokolldatei des Builds existiert. Sollten Sie alte Artefakte hingegen nicht mehr
-  benötigen und lieber Speicherplatz sparen wollen, so können Sie die Artefakte
-  löschen.
+  Protokolldatei des Builds existiert. Sollten Sie alte Artefakte hingegen nicht
+  mehr benötigen und lieber Speicherplatz sparen wollen, so können Sie die
+  Artefakte löschen.
 

-

+

 

-Beachten Sie, dass der Maven Job-Typ automatisch alle produzierten Maven Artefakte archiviert.
-Artefakte, die hier konfiguriert sind, werden zusätzlich dazu archiviert.
-Es gibt eine Option unter den erweiterten Maven Optionen, um die automatische Archivierung zu deaktivieren.
+  Beachten Sie, dass der Maven Job-Typ automatisch alle produzierten Maven
+  Artefakte archiviert. Artefakte, die hier konfiguriert sind, werden zusätzlich
+  dazu archiviert. Es gibt eine Option unter den erweiterten Maven Optionen, um
+  die automatische Archivierung zu deaktivieren.
 

diff --git a/core/src/main/resources/hudson/tasks/ArtifactArchiver/help_fr.html b/core/src/main/resources/hudson/tasks/ArtifactArchiver/help_fr.html
index 403e23295c..68c8be4fff 100644
--- a/core/src/main/resources/hudson/tasks/ArtifactArchiver/help_fr.html
+++ b/core/src/main/resources/hudson/tasks/ArtifactArchiver/help_fr.html
@@ -1,10 +1,9 @@
 

   Archive certains artefacts du build (par exemple, les fichiers zip de la
-  distribution ou les fichiers jar) afin permettre leur téléchargement.
-  Les fichiers archivés sont accessibles à partir de la page Jenkins du build.
+  distribution ou les fichiers jar) afin permettre leur téléchargement. Les
+  fichiers archivés sont accessibles à partir de la page Jenkins du build.
   

-  En général, Jenkins conserve les artefacts d'un build aussi longtemps que
-  le log du build. Néanmoins, si vous n'avez pas besoin des vieux
-  artefacts et préférez économiser de l'espace disque, il est possible de les
-  supprimer.
+  En général, Jenkins conserve les artefacts d'un build aussi longtemps que le
+  log du build. Néanmoins, si vous n'avez pas besoin des vieux artefacts et
+  préférez économiser de l'espace disque, il est possible de les supprimer.
 

diff --git a/core/src/main/resources/hudson/tasks/ArtifactArchiver/help_it.html b/core/src/main/resources/hudson/tasks/ArtifactArchiver/help_it.html
index 838c17d7e7..b63a3dfc5e 100644
--- a/core/src/main/resources/hudson/tasks/ArtifactArchiver/help_it.html
+++ b/core/src/main/resources/hudson/tasks/ArtifactArchiver/help_it.html
@@ -5,14 +5,13 @@
   Jenkins.
   

   Normalmente, Jenkins mantiene gli artefatti di una compilazione fintantoché
-  viene mantenuto il log di tale compilazione, ma se i vecchi artefatti non
-  sono necessari e se si preferirebbe risparmiare spazio su disco, è
-  possibile farlo.
+  viene mantenuto il log di tale compilazione, ma se i vecchi artefatti non sono
+  necessari e se si preferirebbe risparmiare spazio su disco, è possibile farlo.
-
+
-Si noti che il tipo di processo Maven archivia automaticamente tutti gli -artefatti Maven prodotti. Gli artefatti configurati qui saranno archiviati in -aggiunta a questi. L'archiviazione automatica degli artefatti può essere -disabilitata dalle opzioni avanzate di Maven. + Si noti che il tipo di processo Maven archivia automaticamente tutti gli + artefatti Maven prodotti. Gli artefatti configurati qui saranno archiviati in + aggiunta a questi. L'archiviazione automatica degli artefatti può essere + disabilitata dalle opzioni avanzate di Maven.
diff --git a/core/src/main/resources/hudson/tasks/ArtifactArchiver/help_pt_BR.html b/core/src/main/resources/hudson/tasks/ArtifactArchiver/help_pt_BR.html index 1815fc9d98..2aeb913dc2 100644 --- a/core/src/main/resources/hudson/tasks/ArtifactArchiver/help_pt_BR.html +++ b/core/src/main/resources/hudson/tasks/ArtifactArchiver/help_pt_BR.html @@ -1,10 +1,11 @@
- Arquiva os artefatos de construção (por exemplo, arquivos zip de distribuição ou arquivos jar) - desta forma eles podem ser baixados mais tarde. - Arquivos armazenados serão acessíveis da página web do Jenkins. + Arquiva os artefatos de construção (por exemplo, arquivos zip de + distribuição ou arquivos jar) desta forma eles podem ser baixados + mais tarde. Arquivos armazenados serão acessíveis da página web + do Jenkins.
- Normalmente, o Jenkins mantém os artefatos para uma construção tanto tempo quanto - um log de construção é mantido, - mas se você não necessita de artefatos antigos e gostaria de economizar espaço em disco, - é possível apagá-los. + Normalmente, o Jenkins mantém os artefatos para uma construção + tanto tempo quanto um log de construção é mantido, mas se + você não necessita de artefatos antigos e gostaria de economizar + espaço em disco, é possível apagá-los.
diff --git a/core/src/main/resources/hudson/tasks/ArtifactArchiver/help_ru.html b/core/src/main/resources/hudson/tasks/ArtifactArchiver/help_ru.html index b0af2b25b2..c53e27fabc 100644 --- a/core/src/main/resources/hudson/tasks/ArtifactArchiver/help_ru.html +++ b/core/src/main/resources/hudson/tasks/ArtifactArchiver/help_ru.html @@ -1,8 +1,9 @@ 
- Архивирует артефакты сборки (например, готовые к распространению файлы jar или zip) - так что они могут быть скачаны позже. Архивы артефактов будут доступны со страницы Jenkins. + Архивирует артефакты сборки (например, готовые к распространению файлы jar или + zip) так что они могут быть скачаны позже. Архивы артефактов будут доступны со + страницы Jenkins.
- Обычно Jenkins хранит артефакты сборки столько, сколько хранится информация о сборках, - но если вам не нужны артефакты старых сборок и вы предпочли бы уменьшить размер занятого - пространства на диске, вы можете это сделать. + Обычно Jenkins хранит артефакты сборки столько, сколько хранится информация о + сборках, но если вам не нужны артефакты старых сборок и вы предпочли бы + уменьшить размер занятого пространства на диске, вы можете это сделать.
diff --git a/core/src/main/resources/hudson/tasks/ArtifactArchiver/help_tr.html b/core/src/main/resources/hudson/tasks/ArtifactArchiver/help_tr.html index 7238dd30a1..cbd9a8fd76 100644 --- a/core/src/main/resources/hudson/tasks/ArtifactArchiver/help_tr.html +++ b/core/src/main/resources/hudson/tasks/ArtifactArchiver/help_tr.html @@ -1,8 +1,11 @@
- Daha sonra kullanılabilmesi için, yapılandırma artefaktlarını arşivler (mesela, zip veya jar - dosyaları gibi) - Arşivlenmiş dosyalara, Jenkins web sayfası üzerinden erişilebilir. + Daha sonra kullanılabilmesi için, yapılandırma + artefaktlarını arşivler (mesela, zip veya jar dosyaları + gibi) Arşivlenmiş dosyalara, Jenkins web sayfası üzerinden + erişilebilir.
- Normalde, Jenkins yapılandırma logları tutulduğu müddetçe artefaktları saklar, fakat diskte - yer kaplamasından dolayı eski artefaktları istemiyorsanız, silebilirsiniz. + Normalde, Jenkins yapılandırma logları tutulduğu + müddetçe artefaktları saklar, fakat diskte yer + kaplamasından dolayı eski artefaktları istemiyorsanız, + silebilirsiniz.
diff --git a/core/src/main/resources/hudson/tasks/ArtifactArchiver/help_zh_TW.html b/core/src/main/resources/hudson/tasks/ArtifactArchiver/help_zh_TW.html index 4892cb3d0d..ecc3fde460 100644 --- a/core/src/main/resources/hudson/tasks/ArtifactArchiver/help_zh_TW.html +++ b/core/src/main/resources/hudson/tasks/ArtifactArchiver/help_zh_TW.html @@ -1,6 +1,7 @@
- 封存建置成品 (例如 zip 發佈檔，或 jar 檔)，以便日後下載。 - 封存起來的檔案可以由 Jenkins 網頁上取得。 + 封存建置成品 (例如 zip 發佈檔，或 jar 檔)，以便日後下載。 封存起來的檔案可以由 + Jenkins 網頁上取得。
- 一般 Jenkins 會保存留有建置日的成品，不過如果您用不到舊版成品，又想節省磁碟空間，可以額外設定。 + 一般 Jenkins + 會保存留有建置日的成品，不過如果您用不到舊版成品，又想節省磁碟空間，可以額外設定。
diff --git a/core/src/main/resources/hudson/tasks/BatchFile/help-unstableReturn.html b/core/src/main/resources/hudson/tasks/BatchFile/help-unstableReturn.html index 0ee113e9e0..90d5d9a3da 100644 --- a/core/src/main/resources/hudson/tasks/BatchFile/help-unstableReturn.html +++ b/core/src/main/resources/hudson/tasks/BatchFile/help-unstableReturn.html @@ -1,9 +1,11 @@
- If set, the batch errorlevel result that will be interpreted as an unstable build result. - If the final errorlevel matches the value, the build results will be set to unstable and - next steps will be continued. Supported values match the widest errorlevel range for Windows - like systems. In Windows NT4 and beyond the ERRORLEVEL is stored as a four byte, signed integer, - yielding maximum and minimum values of 2147483647 and -2147483648, respectively. Older versions - of Windows use 2 bytes. DOS like systems use single byte, yielding errorlevels between 0-255. - The value 0 is ignored and does not make the build unstable to keep the default behaviour consistent. + If set, the batch errorlevel result that will be interpreted as an unstable + build result. If the final errorlevel matches the value, the build results + will be set to unstable and next steps will be continued. Supported values + match the widest errorlevel range for Windows like systems. In Windows NT4 and + beyond the ERRORLEVEL is stored as a four byte, signed integer, yielding + maximum and minimum values of 2147483647 and -2147483648, respectively. Older + versions of Windows use 2 bytes. DOS like systems use single byte, yielding + errorlevels between 0-255. The value 0 is ignored and does not make the build + unstable to keep the default behaviour consistent.
diff --git a/core/src/main/resources/hudson/tasks/BatchFile/help-unstableReturn_bg.html b/core/src/main/resources/hudson/tasks/BatchFile/help-unstableReturn_bg.html index 61e39ef72b..1fae97ca87 100644 --- a/core/src/main/resources/hudson/tasks/BatchFile/help-unstableReturn_bg.html +++ b/core/src/main/resources/hudson/tasks/BatchFile/help-unstableReturn_bg.html @@ -1,10 +1,11 @@
- Когато е зададена стойност, тя ще се интерпретира като изходния код, който указва нестабилно - изграждане. Ако изходният код за грешка съвпада с тази стойност, изграждането се приема за - нестабилно, но се продължава със следващите стъпки. Поддържа се най-широкия диапазон от - стойности за фамилията Windows. При Windows NT4 и следващи ERRORLEVEL е четирибайтово цяло - число със знак и интервалът е от -2147483648 до 2147483647. По-старите версии на Windows - поддържат двубайтови цели числа — от 0 до 65535. При DOS това е еднобайтова целочислена стойност - от 0 до 255. Стойност 0 се прескача и не води до обявяването на изграждането на нестабилно, - защото това е конвенцията. + Когато е зададена стойност, тя ще се интерпретира като изходния код, който + указва нестабилно изграждане. Ако изходният код за грешка съвпада с тази + стойност, изграждането се приема за нестабилно, но се продължава със + следващите стъпки. Поддържа се най-широкия диапазон от стойности за фамилията + Windows. При Windows NT4 и следващи ERRORLEVEL е четирибайтово цяло число със + знак и интервалът е от -2147483648 до 2147483647. По-старите версии на Windows + поддържат двубайтови цели числа — от 0 до 65535. При DOS това е еднобайтова + целочислена стойност от 0 до 255. Стойност 0 се прескача и не води до + обявяването на изграждането на нестабилно, защото това е конвенцията.
diff --git a/core/src/main/resources/hudson/tasks/BatchFile/help-unstableReturn_it.html b/core/src/main/resources/hudson/tasks/BatchFile/help-unstableReturn_it.html index 4b90c5c703..9962ee05f2 100644 --- a/core/src/main/resources/hudson/tasks/BatchFile/help-unstableReturn_it.html +++ b/core/src/main/resources/hudson/tasks/BatchFile/help-unstableReturn_it.html @@ -1,15 +1,14 @@
- Se l'opzione è impostata, specifica il valore ERRORLEVEL del file batch - che sarà interpretato come risultato di una compilazione instabile. - Se l'ERRORLEVEL finale corrisponde al valore, il risultato della - compilazione sarà impostato a "instabile" e i passaggi successivi - saranno eseguiti. I valori supportati corrispondono all'intervallo più - ampio di ERRORLEVEL per i sistemi di tipo Windows. Su Windows NT4 e oltre - l'ERRORLEVEL è salvato come intero con segno di quattro byte, il che fa - sì che i valori massimo e minimo siano rispettivamente 2147483647 e - -2147483648. Versioni meno recenti di Windows utilizzano due byte. I - sistemi di tipo DOS utilizzando un byte singolo, il che fa sì che gli - ERRORLEVEL siano compresi fra 0 e 255. Il valore 0 è ignorato e non - rende la compilazione instabile, in modo da mantenere il comportamento - predefinito consistente. + Se l'opzione è impostata, specifica il valore ERRORLEVEL del file batch che + sarà interpretato come risultato di una compilazione instabile. Se + l'ERRORLEVEL finale corrisponde al valore, il risultato della compilazione + sarà impostato a "instabile" e i passaggi successivi saranno eseguiti. I + valori supportati corrispondono all'intervallo più ampio di ERRORLEVEL per i + sistemi di tipo Windows. Su Windows NT4 e oltre l'ERRORLEVEL è salvato come + intero con segno di quattro byte, il che fa sì che i valori massimo e minimo + siano rispettivamente 2147483647 e -2147483648. Versioni meno recenti di + Windows utilizzano due byte. I sistemi di tipo DOS utilizzando un byte + singolo, il che fa sì che gli ERRORLEVEL siano compresi fra 0 e 255. Il valore + 0 è ignorato e non rende la compilazione instabile, in modo da mantenere il + comportamento predefinito consistente.
diff --git a/core/src/main/resources/hudson/tasks/Fingerprinter/help-caseSensitive.html b/core/src/main/resources/hudson/tasks/Fingerprinter/help-caseSensitive.html index a2278f27e2..f32b365dc9 100644 --- a/core/src/main/resources/hudson/tasks/Fingerprinter/help-caseSensitive.html +++ b/core/src/main/resources/hudson/tasks/Fingerprinter/help-caseSensitive.html @@ -1,5 +1,11 @@
- Fingerprinter uses Ant org.apache.tools.ant.DirectoryScanner which by default is case sensitive. - For instance, if the job produces *.hpi files, pattern "**/*.HPI" will fail to find them.

- This option can be used to disable case sensitivity. When it's unchecked, pattern "**/*.HPI" will match any *.hpi files, or pattern "**/cAsEsEnSiTiVe.jar" will match a file called caseSensitive.jar. + Fingerprinter uses Ant + org.apache.tools.ant.DirectoryScanner + which by default is case sensitive. For instance, if the job produces *.hpi + files, pattern "**/*.HPI" will fail to find them. +
+
+ This option can be used to disable case sensitivity. When it's unchecked, + pattern "**/*.HPI" will match any *.hpi files, or pattern + "**/cAsEsEnSiTiVe.jar" will match a file called caseSensitive.jar.
diff --git a/core/src/main/resources/hudson/tasks/Fingerprinter/help-caseSensitive_it.html b/core/src/main/resources/hudson/tasks/Fingerprinter/help-caseSensitive_it.html index a04739450e..eda49f3ad2 100644 --- a/core/src/main/resources/hudson/tasks/Fingerprinter/help-caseSensitive_it.html +++ b/core/src/main/resources/hudson/tasks/Fingerprinter/help-caseSensitive_it.html @@ -1,12 +1,14 @@
- Il componente di rilevazione delle impronte digitali utilizza la classe - org.apache.tools.ant.DirectoryScanner di Ant che, per - impostazione predefinita, fa differenza tra maiuscole e minuscole. - Ad esempio, se il processo produce file *.hpi, il pattern "**/*.HPI" non - riuscirà a rilevarli.

- Quest'opzione può essere utilizzata per disattivare il rilevamento della - differenza fra maiuscole e minuscole. Quando è deselezionata, il - pattern "**/*.HPI" corrisponderà a tutti i file *.hpi, e il pattern - "**/mAiUsColeMiNuScOlE.jar" corrisponderà a un file di nome - maiuscoleMinuscole.jar. + Il componente di rilevazione delle impronte digitali utilizza la classe + org.apache.tools.ant.DirectoryScanner + di Ant che, per impostazione predefinita, fa differenza tra maiuscole e + minuscole. Ad esempio, se il processo produce file *.hpi, il pattern + "**/*.HPI" non riuscirà a rilevarli. +
+
+ Quest'opzione può essere utilizzata per disattivare il rilevamento della + differenza fra maiuscole e minuscole. Quando è deselezionata, il pattern + "**/*.HPI" corrisponderà a tutti i file *.hpi, e il pattern + "**/mAiUsColeMiNuScOlE.jar" corrisponderà a un file di nome + maiuscoleMinuscole.jar.
diff --git a/core/src/main/resources/hudson/tasks/Fingerprinter/help-excludes.html b/core/src/main/resources/hudson/tasks/Fingerprinter/help-excludes.html index 8fc943e974..14f78bacf5 100644 --- a/core/src/main/resources/hudson/tasks/Fingerprinter/help-excludes.html +++ b/core/src/main/resources/hudson/tasks/Fingerprinter/help-excludes.html @@ -1,5 +1,6 @@
- Optionally specify the 'excludes' pattern, such as "foo/bar/**/*". Use "," to set a list of patterns. - A file that matches this mask will not be fingerprinted even if it matches the - mask specified in 'files to fingerprint' section. + Optionally specify the 'excludes' pattern, such as "foo/bar/**/*". Use "," to + set a list of patterns. A file that matches this mask will not be + fingerprinted even if it matches the mask specified in 'files to fingerprint' + section.
diff --git a/core/src/main/resources/hudson/tasks/Fingerprinter/help-excludes_it.html b/core/src/main/resources/hudson/tasks/Fingerprinter/help-excludes_it.html index ab37022632..24692b9ce0 100644 --- a/core/src/main/resources/hudson/tasks/Fingerprinter/help-excludes_it.html +++ b/core/src/main/resources/hudson/tasks/Fingerprinter/help-excludes_it.html @@ -1,6 +1,9 @@
- Specificare facoltativamente il pattern 'excludes', - ad esempio "pippo/pluto/**/*". Un file corrispondente a questa maschera non + Specificare facoltativamente + + il pattern 'excludes' + + , ad esempio "pippo/pluto/**/*". Un file corrispondente a questa maschera non sarà archiviato anche nel caso in cui corrisponda alla maschera specificata nella sezione "File di cui rilevare le impronte digitali".
diff --git a/core/src/main/resources/hudson/tasks/Fingerprinter/help-targets.html b/core/src/main/resources/hudson/tasks/Fingerprinter/help-targets.html index 364cb69bb7..152a1187b3 100644 --- a/core/src/main/resources/hudson/tasks/Fingerprinter/help-targets.html +++ b/core/src/main/resources/hudson/tasks/Fingerprinter/help-targets.html @@ -1,5 +1,11 @@
- Can use wildcards like module/dist/**/*.zip - (see the @includes of Ant fileset for the exact format). - The base directory is the workspace. + Can use wildcards like + module/dist/**/*.zip + (see the + + @includes of Ant fileset + + for the exact format). The base directory is + the workspace + .
diff --git a/core/src/main/resources/hudson/tasks/Fingerprinter/help-targets_bg.html b/core/src/main/resources/hudson/tasks/Fingerprinter/help-targets_bg.html index 80c8b16c4a..5091710108 100644 --- a/core/src/main/resources/hudson/tasks/Fingerprinter/help-targets_bg.html +++ b/core/src/main/resources/hudson/tasks/Fingerprinter/help-targets_bg.html @@ -1,7 +1,9 @@
- Можете да използвате шаблонни знаци като module/dist/**/*.zip - (за точния формат погледнете секцията за - @includes от - ръководството на Ant). - Основната директория е работното пространството. + Можете да използвате шаблонни знаци като + module/dist/**/*.zip + (за точния формат погледнете секцията за + @includes + от ръководството на Ant). Основната директория е + работното пространството + .
diff --git a/core/src/main/resources/hudson/tasks/Fingerprinter/help-targets_da.html b/core/src/main/resources/hudson/tasks/Fingerprinter/help-targets_da.html index 66f2c4ecb7..5145e2c236 100644 --- a/core/src/main/resources/hudson/tasks/Fingerprinter/help-targets_da.html +++ b/core/src/main/resources/hudson/tasks/Fingerprinter/help-targets_da.html @@ -1,3 +1 @@ -
- Du kan bruge wildcards som 'module/dist/**/*.zip'. -
+
Du kan bruge wildcards som 'module/dist/**/*.zip'.
diff --git a/core/src/main/resources/hudson/tasks/Fingerprinter/help-targets_de.html b/core/src/main/resources/hudson/tasks/Fingerprinter/help-targets_de.html index 4aa7673e81..2af2bd9254 100644 --- a/core/src/main/resources/hudson/tasks/Fingerprinter/help-targets_de.html +++ b/core/src/main/resources/hudson/tasks/Fingerprinter/help-targets_de.html @@ -1,6 +1,10 @@
- Es sind reguläre Ausdrücke wie z.B. 'module/dist/**/*.zip' erlaubt. - Das genaue Format können Sie der - Spezifikation für @includes eines Ant-Filesets entnehmen. - Das Ausgangsverzeichnis ist der Arbeitsbereich. + Es sind reguläre Ausdrücke wie z.B. 'module/dist/**/*.zip' erlaubt. Das genaue + Format können Sie der + + Spezifikation für @includes eines Ant-Filesets + + entnehmen. Das Ausgangsverzeichnis ist der + Arbeitsbereich + .
diff --git a/core/src/main/resources/hudson/tasks/Fingerprinter/help-targets_es.html b/core/src/main/resources/hudson/tasks/Fingerprinter/help-targets_es.html index 1bb91e2d9e..61f6aa3a5e 100644 --- a/core/src/main/resources/hudson/tasks/Fingerprinter/help-targets_es.html +++ b/core/src/main/resources/hudson/tasks/Fingerprinter/help-targets_es.html @@ -1,6 +1,9 @@
- Se pueden usar comodines como 'module/dist/**/*.zip'. - Echa un vistazo al - atributo @includes de la etiqueta fileset de Ant para conocer el formato exacto. - El directorio base es el workspace. + Se pueden usar comodines como 'module/dist/**/*.zip'. Echa un vistazo al + + atributo @includes de la etiqueta fileset de Ant + + para conocer el formato exacto. El directorio base es + el workspace + .
diff --git a/core/src/main/resources/hudson/tasks/Fingerprinter/help-targets_fr.html b/core/src/main/resources/hudson/tasks/Fingerprinter/help-targets_fr.html index 579074b62b..b9f9dd2008 100644 --- a/core/src/main/resources/hudson/tasks/Fingerprinter/help-targets_fr.html +++ b/core/src/main/resources/hudson/tasks/Fingerprinter/help-targets_fr.html @@ -1,5 +1,10 @@
- Les wildcards du type 'module/dist/**/*.zip' sont autorisés. - Voir le format exact des @includes des filesets Ants. - Le répertoire de base est le répertoire de travail (workspace). + Les wildcards du type 'module/dist/**/*.zip' sont autorisés. Voir le format + exact des + + @includes des filesets Ants + + . Le répertoire de base est le + répertoire de travail (workspace) + .
diff --git a/core/src/main/resources/hudson/tasks/Fingerprinter/help-targets_it.html b/core/src/main/resources/hudson/tasks/Fingerprinter/help-targets_it.html index 2e6c02b6d7..1f29fc3664 100644 --- a/core/src/main/resources/hudson/tasks/Fingerprinter/help-targets_it.html +++ b/core/src/main/resources/hudson/tasks/Fingerprinter/help-targets_it.html @@ -1,5 +1,11 @@
- È possibile utilizzare caratteri jolly come modulo/dist/**/*.zip - (si veda la direttiva @includes dei fileset di Ant per il formato esatto). - La directory di base è lo spazio di lavoro. + È possibile utilizzare caratteri jolly come + modulo/dist/**/*.zip + (si veda + + la direttiva @includes dei fileset di Ant + + per il formato esatto). La directory di base è + lo spazio di lavoro + .
diff --git a/core/src/main/resources/hudson/tasks/Fingerprinter/help-targets_ja.html b/core/src/main/resources/hudson/tasks/Fingerprinter/help-targets_ja.html index ea1103453e..10f5207fed 100644 --- a/core/src/main/resources/hudson/tasks/Fingerprinter/help-targets_ja.html +++ b/core/src/main/resources/hudson/tasks/Fingerprinter/help-targets_ja.html @@ -1,3 +1,9 @@
- 記録したいファイルのパターンをAnt fileset includes属性の書式で（ベースディレクトリはワークスペースルート）。例：module/dist/**/*.zip + 記録したいファイルのパターンを + + Ant fileset includes属性 + + の書式で（ベースディレクトリは + ワークスペースルート + ）。例：module/dist/**/*.zip
diff --git a/core/src/main/resources/hudson/tasks/Fingerprinter/help-targets_nl.html b/core/src/main/resources/hudson/tasks/Fingerprinter/help-targets_nl.html index 3c1ed02491..fed0232631 100644 --- a/core/src/main/resources/hudson/tasks/Fingerprinter/help-targets_nl.html +++ b/core/src/main/resources/hudson/tasks/Fingerprinter/help-targets_nl.html @@ -1,6 +1,9 @@
- Je kunt jokerkarakters zoals in 'module/dist/**/*.zip' gebruiken. - Zie de @includes mogelijkheid van Ant bestandsbundels voor het correcte - formaat. - De basisfolder is de werkplaats. + Je kunt jokerkarakters zoals in 'module/dist/**/*.zip' gebruiken. Zie de + + @includes mogelijkheid van Ant bestandsbundels + + voor het correcte formaat. De basisfolder is + de werkplaats + .
diff --git a/core/src/main/resources/hudson/tasks/Fingerprinter/help-targets_pt_BR.html b/core/src/main/resources/hudson/tasks/Fingerprinter/help-targets_pt_BR.html index 09cde5b86d..71752eff3a 100644 --- a/core/src/main/resources/hudson/tasks/Fingerprinter/help-targets_pt_BR.html +++ b/core/src/main/resources/hudson/tasks/Fingerprinter/help-targets_pt_BR.html @@ -1,5 +1,9 @@
- Pode usar caracteres coringas como em 'module/dist/**/*.zip'. - Veja o Fileset @includes do Ant para o formato exato. - O diret�rio base � o workspace. + Pode usar caracteres coringas como em 'module/dist/**/*.zip'. Veja o + + Fileset @includes do Ant + + para o formato exato. O diret�rio base � + o workspace + .
diff --git a/core/src/main/resources/hudson/tasks/Fingerprinter/help-targets_ru.html b/core/src/main/resources/hudson/tasks/Fingerprinter/help-targets_ru.html index 81480ccf73..4e00029fa3 100644 --- a/core/src/main/resources/hudson/tasks/Fingerprinter/help-targets_ru.html +++ b/core/src/main/resources/hudson/tasks/Fingerprinter/help-targets_ru.html @@ -1,6 +1,10 @@
- Вы можете использовать шаблоны, например, 'module/dist/**/*.zip'. - Подробнее смотрите - @includes для наборов файлов Ant. - Базовой директорией для шаблонов является рабочая директория. + Вы можете использовать шаблоны, например, 'module/dist/**/*.zip'. Подробнее + смотрите + + @includes для наборов файлов Ant + + . Базовой директорией для шаблонов является + рабочая директория + .
diff --git a/core/src/main/resources/hudson/tasks/Fingerprinter/help-targets_zh_TW.html b/core/src/main/resources/hudson/tasks/Fingerprinter/help-targets_zh_TW.html index e5c76e5da2..edc619112d 100644 --- a/core/src/main/resources/hudson/tasks/Fingerprinter/help-targets_zh_TW.html +++ b/core/src/main/resources/hudson/tasks/Fingerprinter/help-targets_zh_TW.html @@ -1,5 +1,9 @@
- 可以像 "module/dist/**/*.zip" 這樣使用萬用字元。 - 確切格式可以參考 Ant fileset 的 @includes。 - 工作目錄就是工作區目錄。 + 可以像 "module/dist/**/*.zip" 這樣使用萬用字元。 確切格式可以參考 + + Ant fileset 的 @includes + + 。 工作目錄就是 + 工作區目錄 + 。
diff --git a/core/src/main/resources/hudson/tasks/Fingerprinter/help.html b/core/src/main/resources/hudson/tasks/Fingerprinter/help.html index f481348508..80d7c8d3d8 100644 --- a/core/src/main/resources/hudson/tasks/Fingerprinter/help.html +++ b/core/src/main/resources/hudson/tasks/Fingerprinter/help.html @@ -1,31 +1,45 @@
- Jenkins can record the 'fingerprint' of files (most often jar files) to keep track - of where/when those files are produced and used. When you have inter-dependent - projects on Jenkins, this allows you to quickly find out answers to questions like: + Jenkins can record the 'fingerprint' of files (most often jar files) to keep + track of where/when those files are produced and used. When you have + inter-dependent projects on Jenkins, this allows you to quickly find out + answers to questions like:
  • - I have foo.jar on my HDD but which build number of FOO did it come from? + I have + foo.jar + on my HDD but which build number of FOO did it come from?
  • - My BAR project depends on foo.jar from the FOO project. + My BAR project depends on + foo.jar + from the FOO project. +
    • +
  • +
      +
    • + Which build of + foo.jar + is used in BAR #51? +
      • +
    • + Which build of BAR contains my bug fix to + foo.jar + #32? +
      • +
    • -
    • -
    • - Which build of foo.jar is used in BAR #51? -
      • -
    • - Which build of BAR contains my bug fix to foo.jar #32? -
      • -

- To use this feature, all of the involved projects (not just the project - in which a file is produced, but also the projects in which the file - is used) need to use this and record fingerprints. + To use this feature, all of the involved projects (not just the project in + which a file is produced, but also the projects in which the file is used) + need to use this and record fingerprints. +

- See this document - for more details. + See + this document + for more details. +

diff --git a/core/src/main/resources/hudson/tasks/Fingerprinter/help_bg.html b/core/src/main/resources/hudson/tasks/Fingerprinter/help_bg.html index fff280a981..f6736d0c96 100644 --- a/core/src/main/resources/hudson/tasks/Fingerprinter/help_bg.html +++ b/core/src/main/resources/hudson/tasks/Fingerprinter/help_bg.html @@ -1,34 +1,46 @@
- Jenkins може да записва отпечатъка на файловете (най-често това са файлове jar) за - проследяване кога и къде тези файлове са създадени и използване. Това ви помага - да получите отговори на въпроси като следните, когато имате множество проекти, - зависими един от друг: + Jenkins може да записва отпечатъка на файловете (най-често това са файлове + jar) за проследяване кога и къде тези файлове са създадени и използване. Това + ви помага да получите отговори на въпроси като следните, когато имате + множество проекти, зависими един от друг:
  • - На диска ми има файл foo.jar, но от кое точно изграждане идва? + На диска ми има файл + foo.jar + , но от кое точно изграждане идва?
  • - Ако проектът BAR зависи от файла foo.jar, който е от проекта FOO: + Ако проектът BAR зависи от файла + foo.jar + , който е от проекта FOO: +
    • +
  • +
      +
    • + От кое изграждане идва версията на + foo.jar + , която се ползва в изграждане на №51 на BAR? +
      • +
    • + Кое изграждане на BAR ще ползва поправката на грешката, която е + включена в изграждане №32 на + foo.jar + ? +
      • +
    • -
    • -
    • - От кое изграждане идва версията на foo.jar, която се ползва в - изграждане на №51 на BAR? -
      • -
    • - Кое изграждане на BAR ще ползва поправката на грешката, която е включена - в изграждане №32 на foo.jar? -
      • -

- За да се възползвате от това, трябва всички участващи проекти да използват отпечатъци - на файлове — не само проектите, от които файловете произхождат, но и тези, в които се - ползват. + За да се възползвате от това, трябва всички участващи проекти да използват + отпечатъци на файлове — не само проектите, от които файловете произхождат, + но и тези, в които се ползват. +

- За повече информация вижте - документацията. + За повече информация вижте + документацията + . +

diff --git a/core/src/main/resources/hudson/tasks/Fingerprinter/help_de.html b/core/src/main/resources/hudson/tasks/Fingerprinter/help_de.html index 8639b9919f..8e67124e49 100644 --- a/core/src/main/resources/hudson/tasks/Fingerprinter/help_de.html +++ b/core/src/main/resources/hudson/tasks/Fingerprinter/help_de.html @@ -1,31 +1,46 @@ -
- Jenkins kann "Fingerabdrücke" von Dateien aufzeichnen (in den meisten Fällen von - JAR-Dateien), um nachzuvollziehen, wann in welchen Builds diese Dateien - erstellt oder verwendet wurden. Wenn Sie untereinander abhängige Projekte in - Jenkins bauen, können Sie dadurch schnell Antworten finden auf Fragen wie: +
+ Jenkins kann "Fingerabdrücke" von Dateien aufzeichnen (in den + meisten Fällen von JAR-Dateien), um nachzuvollziehen, wann in welchen + Builds diese Dateien erstellt oder verwendet wurden. Wenn Sie untereinander + abhängige Projekte in Jenkins bauen, können Sie dadurch schnell + Antworten finden auf Fragen wie:
  • - Ich habe foo.jar auf meiner Festplatte - aber aus welchem Build - des Projekts FOO stammt es? + Ich habe + foo.jar + auf meiner Festplatte - aber aus welchem Build des Projekts FOO stammt es?
  • - Mein Projekt BAR hängt von foo.jar des Projekts FOO ab. + Mein Projekt BAR hängt von + foo.jar + des Projekts FOO ab. +
    • +
  • +
      +
    • + Welcher Build von + foo.jar + wurde in BAR #51 verwendet? +
      • +
    • + Welcher Build von BAR beinhaltet meine Fehlerkorrektur für + foo.jar + #32? +
      • +
    • -
    • -
    • - Welcher Build von foo.jar wurde in BAR #51 verwendet? -
      • -
    • - Welcher Build von BAR beinhaltet meine Fehlerkorrektur für - foo.jar #32? -
      • -
-

- Um dieses Merkmal zu nützen, müssen alle Projekte (also nicht nur das - Projekt, in dem eine Datei produziert wird, sondern alle Projekte, welche - die Datei verwenden) diese Funktion verwenden und Fingerabdrücke aufzeichnen.

- Weitere Informationen (auf Englisch) + Um dieses Merkmal zu nützen, müssen alle Projekte (also nicht nur + das Projekt, in dem eine Datei produziert wird, sondern alle Projekte, + welche die Datei verwenden) diese Funktion verwenden und Fingerabdrücke + aufzeichnen. +

+ +

+ + Weitere Informationen (auf Englisch) + +

diff --git a/core/src/main/resources/hudson/tasks/Fingerprinter/help_fr.html b/core/src/main/resources/hudson/tasks/Fingerprinter/help_fr.html index affa947537..0334ab5d09 100644 --- a/core/src/main/resources/hudson/tasks/Fingerprinter/help_fr.html +++ b/core/src/main/resources/hudson/tasks/Fingerprinter/help_fr.html @@ -1,38 +1,47 @@ 
Jenkins est capable d'enregistrer une empreinte numérique unique, ou - 'fingerprint', des fichiers (généralement des fichiers jar) pour - conserver la trace de quand et où ces fichiers - sont produits et utilisés. Quand vous avez des projets - inter-dépendants avec Jenkins, cela vous permet de répondre facilement - à des questions telles que : + 'fingerprint', des fichiers (généralement des fichiers jar) pour conserver la + trace de quand et où ces fichiers sont produits et utilisés. Quand vous avez + des projets inter-dépendants avec Jenkins, cela vous permet de répondre + facilement à des questions telles que :
  • - J'ai toto.jar sur mon disque dur, mais de quel numéro de - build provient-il? + J'ai + toto.jar + sur mon disque dur, mais de quel numéro de build provient-il?
  • - Mon projet TITI dépend de toto.jar du projet TOTO. + Mon projet TITI dépend de + toto.jar + du projet TOTO. +
    • +
  • +
      +
    • + Quel build de + toto.jar + est utilisé dans TUTU #51? +
      • +
    • + Quel build de TATA contient ma correction de bug reporté sur + toto.jar + #32? +
      • +
    • -
    • -
    • - Quel build de toto.jar est utilisé dans TUTU #51? -
      • -
    • - Quel build de TATA contient ma correction de bug reporté sur - toto.jar #32? -
      • -

- Pour utiliser cette fonctionnalité, tous les projets concernés (pas - seulement le projet d'où provient un fichier, mais aussi tous les - projets qui l'utilisent) doivent activer cette option et - enregistrer les empreintes numériques. + Pour utiliser cette fonctionnalité, tous les projets concernés (pas + seulement le projet d'où provient un fichier, mais aussi tous les projets + qui l'utilisent) doivent activer cette option et enregistrer les empreintes + numériques. +

- Voir - ce document - pour plus de details. + Voir + ce document + pour plus de details. +

diff --git a/core/src/main/resources/hudson/tasks/Fingerprinter/help_it.html b/core/src/main/resources/hudson/tasks/Fingerprinter/help_it.html index 40155152ca..6d2fabfca5 100644 --- a/core/src/main/resources/hudson/tasks/Fingerprinter/help_it.html +++ b/core/src/main/resources/hudson/tasks/Fingerprinter/help_it.html @@ -6,27 +6,41 @@
  • - Ho pippo.jar salvato su disco, ma da quale compilazione di PIPPO proviene? + Ho + pippo.jar + salvato su disco, ma da quale compilazione di PIPPO proviene?
  • - Il progetto PLUTO dipende da pippo.jar proveniente dal progetto PIPPO. + Il progetto PLUTO dipende da + pippo.jar + proveniente dal progetto PIPPO. +
    • +
  • +
      +
    • + Quale compilazione di + pippo.jar + è utilizzata nella compilazione 51 di PLUTO? +
      • +
    • + Quale compilazione di PLUTO contiene la correzione che ho introdotto + nella compilazione 32 di + pippo.jar + ? +
      • +
    • -
    • -
    • - Quale compilazione di pippo.jar è utilizzata nella compilazione 51 di PLUTO? -
      • -
    • - Quale compilazione di PLUTO contiene la correzione che ho introdotto nella compilazione 32 di pippo.jar? -
      • -

- Per utilizzare questa funzionalità, tutti i progetti coinvolti (non solo il - progetto in cui viene prodotto un file, ma anche quelli in cui è utilizzato - il file) devono utilizzarla e registrare le impronte digitali. + Per utilizzare questa funzionalità, tutti i progetti coinvolti (non solo il + progetto in cui viene prodotto un file, ma anche quelli in cui è utilizzato + il file) devono utilizzarla e registrare le impronte digitali. +

- Si veda questo documento - per ulteriori dettagli. + Si veda + questo documento + per ulteriori dettagli. +

diff --git a/core/src/main/resources/hudson/tasks/Fingerprinter/help_ja.html b/core/src/main/resources/hudson/tasks/Fingerprinter/help_ja.html index 663cab2fbc..70396a9022 100644 --- a/core/src/main/resources/hudson/tasks/Fingerprinter/help_ja.html +++ b/core/src/main/resources/hudson/tasks/Fingerprinter/help_ja.html @@ -6,27 +6,39 @@ すばやく解決する事ができます。
  • - ハードディスクにある foo.jar は，FOOプロジェクトのどのビルド番号で作られたのか？ + ハードディスクにある + foo.jar + は，FOOプロジェクトのどのビルド番号で作られたのか？
  • - BARプロジェクトが，FOOプロジェクトの foo.jar に依存している場合 + BARプロジェクトが，FOOプロジェクトの + foo.jar + に依存している場合 +
    • +
  • +
      +
    • + BAR プロジェクトのビルド #51 で使われている + foo.jar + のビルドはどれか？ +
      • +
    • + #32でバグフィックスした + foo.jar + を含んでいる BARプロジェクトのビルド はどれか？ +
      • +
    • -
    • -
    • - BAR プロジェクトのビルド #51 で使われている foo.jarのビルドはどれか？ -
      • -
    • - #32でバグフィックスした foo.jar を含んでいる BARプロジェクトのビルド はどれか？ -
      • -

- この機能を使用するには，関連するプロジェクト（ファイルを生成するプロジェクトだけではなく， - ファイルを利用するプロジェクト）すべてで，ファイル指紋を記録する必要があります。 + この機能を使用するには，関連するプロジェクト（ファイルを生成するプロジェクトだけではなく， + ファイルを利用するプロジェクト）すべてで，ファイル指紋を記録する必要があります。 +

+

- より詳しくは - このドキュメントを - 参照してください。 - + より詳しくは + このドキュメント + を 参照してください。 +

diff --git a/core/src/main/resources/hudson/tasks/Fingerprinter/help_pt_BR.html b/core/src/main/resources/hudson/tasks/Fingerprinter/help_pt_BR.html index 3509624b3e..95f07ec565 100644 --- a/core/src/main/resources/hudson/tasks/Fingerprinter/help_pt_BR.html +++ b/core/src/main/resources/hudson/tasks/Fingerprinter/help_pt_BR.html @@ -1,31 +1,49 @@
- Jenkins pode gravar o 'fingerprint' dos arquivos (mais frequentemente do arquivos jar) para manter registro - de onde/quando estes arquivos são produzidos e usados. Quando você tiver projetos - inter-dependêntes no Jenkins, isto permite que você rapidamente encontre respostas para questões como: + Jenkins pode gravar o 'fingerprint' dos arquivos (mais frequentemente do + arquivos jar) para manter registro de onde/quando estes arquivos são + produzidos e usados. Quando você tiver projetos inter-dependêntes no + Jenkins, isto permite que você rapidamente encontre respostas para + questões como:
  • - Eu tenho um foo.jar no meu HD mas qual o número da construção de FOO que gerou ele? + Eu tenho um + foo.jar + no meu HD mas qual o número da construção de FOO que gerou + ele?
  • - Meu projeto BAR depende de foo.jar do projeto FOO. + Meu projeto BAR depende de + foo.jar + do projeto FOO.
    • - Qual construção de foo.jar é usada na construção de BAR número 51? + Qual construção de + foo.jar + é usada na construção de BAR número 51?
    • - Qual construção de BAR contém minha correção de bug para o foo.jar de número 32? + Qual construção de BAR contém minha correção de + bug para o + foo.jar + de número 32?

- Para usar esta característica, todos os projetos envolvidos (não apenas o projeto - no qual um arquivo é produzido, mas também os projetos nos quais o arquivo - é usado) necessitam usar isto e gravar os fingerprints. + Para usar esta característica, todos os projetos envolvidos (não + apenas o projeto no qual um arquivo é produzido, mas também os + projetos nos quais o arquivo é usado) necessitam usar isto e gravar os + fingerprints. +

- Veja esta documentação - para mais detalhes. + Veja + + esta documentação + + para mais detalhes. +

diff --git a/core/src/main/resources/hudson/tasks/Fingerprinter/help_ru.html b/core/src/main/resources/hudson/tasks/Fingerprinter/help_ru.html index 925d55507f..d6dd2085a5 100644 --- a/core/src/main/resources/hudson/tasks/Fingerprinter/help_ru.html +++ b/core/src/main/resources/hudson/tasks/Fingerprinter/help_ru.html @@ -1,31 +1,45 @@ 
- Jenkins может сохранять отпечаток 'fingerprint' файлов (обычно файлов jar) для - отслеживания где/кем был собран и использован этот файл. Если у вас есть - взаимно-зависимые проекты в Jenkins? это дас вам возможность быстро найти ответы на следующие вопросы: + Jenkins может сохранять отпечаток 'fingerprint' файлов (обычно файлов jar) для + отслеживания где/кем был собран и использован этот файл. Если у вас есть + взаимно-зависимые проекты в Jenkins? это дас вам возможность быстро найти + ответы на следующие вопросы:
  • - У меня есть foo.jar на диске, но каков его номер сборки в проекте FOO? + У меня есть + foo.jar + на диске, но каков его номер сборки в проекте FOO?
  • - Проект BAR зависит от foo.jar из проекта FOO. + Проект BAR зависит от + foo.jar + из проекта FOO. +
    • +
  • +
      +
    • + Какой номер сборки + foo.jar + использован в BAR #51? +
      • +
    • + Какая сборка BAR содержит мой багфикс из + foo.jar + сборки #32? +
      • +
    • -
    • -
    • - Какой номер сборки foo.jar использован в BAR #51? -
      • -
    • - Какая сборка BAR содержит мой багфикс из foo.jar сборки #32? -
      • -

- Чтобы использовать эту функцию все вовлеченные проекты (не только тот проект, - файлы которого индексируются, но также проекты, в которых файл используется) - должны также включить эту опцию и сохранять свои отпечатки. + Чтобы использовать эту функцию все вовлеченные проекты (не только тот + проект, файлы которого индексируются, но также проекты, в которых файл + используется) должны также включить эту опцию и сохранять свои отпечатки. +

- Прочтите этот документ - если вы хотите узнать больше. + Прочтите + этот документ + если вы хотите узнать больше. +

diff --git a/core/src/main/resources/hudson/tasks/Fingerprinter/help_tr.html b/core/src/main/resources/hudson/tasks/Fingerprinter/help_tr.html index 5c411940db..80631f1a6e 100644 --- a/core/src/main/resources/hudson/tasks/Fingerprinter/help_tr.html +++ b/core/src/main/resources/hudson/tasks/Fingerprinter/help_tr.html @@ -1,29 +1,49 @@
- Jenkins, dosyaların (çoğunlukta jar dosyası) ne zaman üretildiğini ve nerelerde kullanıldığını takip edebilmek - amacıyla 'parmakizlerini' kaydeder. Eğer karşılıklı bağımlı projeleriniz var ise, bu yöntemle - aşağıdaki sorulara çabucak cevap bulabilirsiniz. + Jenkins, dosyaların (çoğunlukta jar dosyası) ne zaman + üretildiğini ve nerelerde kullanıldığını + takip edebilmek amacıyla 'parmakizlerini' kaydeder. Eğer + karşılıklı bağımlı projeleriniz var ise, bu + yöntemle aşağıdaki sorulara çabucak cevap + bulabilirsiniz.
  • - Sabit diskimde foo.jar dosyam var, fakat FOO projesinin hangi sürüm numarasında üretildi? + Sabit diskimde + foo.jar + dosyam var, fakat FOO projesinin hangi sürüm numarasında + üretildi?
  • - BAR projesi FOO projesinin foo.jar dosyasına bağımlıdır. + BAR projesi FOO projesinin + foo.jar + dosyasına bağımlıdır. +
    • +
  • +
      +
    • + BAR'ın 51 numaralı sürümünde + foo.jar + 'ın hangi yapılandırması kullanıldı. +
      • +
    • + Hangi BAR projesi, + foo.jar + 'ın 32 numaralı sürümüne + uyguladığım çözümü içerir? +
      • +
    • -
    • -
    • - BAR'ın 51 numaralı sürümünde foo.jar'ın hangi yapılandırması kullanıldı. -
      • -
    • - Hangi BAR projesi, foo.jar'ın 32 numaralı sürümüne uyguladığım çözümü içerir? -
      • -

- Bu özelliği kullanabilmek için, dahil olan tüm projelerin (sadece dosyayı üreten proje değil, - aynı zamanda bu dosyayı kullanan projelerin de) bunu kullanması ve - parmakizlerini kaydetmesi gereklidir. + Bu özelliği kullanabilmek için, dahil olan tüm + projelerin (sadece dosyayı üreten proje değil, aynı + zamanda bu dosyayı kullanan projelerin de) bunu kullanması ve + parmakizlerini kaydetmesi gereklidir. +

+

- Daha fazla bilgi için lütfen tıklayın + Daha fazla bilgi için lütfen + tıklayın +

diff --git a/core/src/main/resources/hudson/tasks/Fingerprinter/help_zh_TW.html b/core/src/main/resources/hudson/tasks/Fingerprinter/help_zh_TW.html index 26dd3875c0..7535146498 100644 --- a/core/src/main/resources/hudson/tasks/Fingerprinter/help_zh_TW.html +++ b/core/src/main/resources/hudson/tasks/Fingerprinter/help_zh_TW.html @@ -4,25 +4,39 @@
  • - 我硬碟裡有一個叫做 foo.jar 的檔案，它是哪一次建置 FOO 的成品呢? + 我硬碟裡有一個叫做 + foo.jar + 的檔案，它是哪一次建置 FOO 的成品呢?
  • - 我家的 BAR 專案相依於 FOO 專案產出的 foo.jar。 + 我家的 BAR 專案相依於 FOO 專案產出的 + foo.jar + 。 +
    • +
  • +
      +
    • + 在 BAR 的第 51 建置裡用到的是什麼時候建置出來的 + foo.jar + 呢? +
      • +
    • + 哪一版的 BAR 包到我幹掉 Bug 後的 + foo.jar + #32 呢? +
      • +
    • -
    • -
    • - 在 BAR 的第 51 建置裡用到的是什麼時候建置出來的 foo.jar 呢? -
      • -
    • - 哪一版的 BAR 包到我幹掉 Bug 後的 foo.jar #32 呢? -
      • -

- 要使用這項功能，每一個有關聯的專案 (不只產出檔案的專案，還要包含那些使用到檔案的專案) - 都要開啟指紋記錄功能。 + 要使用這項功能，每一個有關聯的專案 + (不只產出檔案的專案，還要包含那些使用到檔案的專案) 都要開啟指紋記錄功能。 +

- 詳情請參考這份文件。 + 詳情請參考 + 這份文件 + 。 +

diff --git a/core/src/main/resources/hudson/tasks/Maven/help-injectBuildVariables.html b/core/src/main/resources/hudson/tasks/Maven/help-injectBuildVariables.html index b36371b2ce..14b020cb55 100644 --- a/core/src/main/resources/hudson/tasks/Maven/help-injectBuildVariables.html +++ b/core/src/main/resources/hudson/tasks/Maven/help-injectBuildVariables.html @@ -1,5 +1,10 @@
- Pass all build variables into maven process in form of java properties. This is seldom needed as Jenkins provides it as - environment variables anyway. Preferred way to access Jenkins build variables is to explicitly map it to property in - Properties section (MY_VAR=${MY_VAR}). + Pass all build variables into maven process in form of java properties. This + is seldom needed as Jenkins provides it as environment variables anyway. + Preferred way to access Jenkins build variables is to explicitly map it to + property in + Properties + section ( + MY_VAR=${MY_VAR} + ).
diff --git a/core/src/main/resources/hudson/tasks/Maven/help-injectBuildVariables_bg.html b/core/src/main/resources/hudson/tasks/Maven/help-injectBuildVariables_bg.html index b51de2cdc9..e3291ab8d5 100644 --- a/core/src/main/resources/hudson/tasks/Maven/help-injectBuildVariables_bg.html +++ b/core/src/main/resources/hudson/tasks/Maven/help-injectBuildVariables_bg.html @@ -1,6 +1,11 @@
- Подаване на всички променливи от изграждането към процеса на maven като свойства на Java. - Рядко има нужда от това, защото променливите така или иначе са изнесени към средата. - Предпочитаният начин за достъп до тях е изрично подаване на отделните променливи от - изграждането като свойства на Java в раздела Свойства (MY_VAR=${MY_VAR}). + Подаване на всички променливи от изграждането към процеса на maven като + свойства на Java. Рядко има нужда от това, защото променливите така или иначе + са изнесени към средата. Предпочитаният начин за достъп до тях е изрично + подаване на отделните променливи от изграждането като свойства на Java в + раздела + Свойства + ( + MY_VAR=${MY_VAR} + ).
diff --git a/core/src/main/resources/hudson/tasks/Maven/help-injectBuildVariables_it.html b/core/src/main/resources/hudson/tasks/Maven/help-injectBuildVariables_it.html index f8d4b09dbe..205a6e7796 100644 --- a/core/src/main/resources/hudson/tasks/Maven/help-injectBuildVariables_it.html +++ b/core/src/main/resources/hudson/tasks/Maven/help-injectBuildVariables_it.html @@ -1,8 +1,11 @@
Passa tutte le variabili di compilazione al processo Maven sotto forma di - proprietà Java. Ciò è richiesto raramente perché Jenkins le fornisce - comunque sotto forma di variabili d'ambiente. La modalità preferita di - accesso alle variabili di compilazione di Jenkins è la loro mappatura in - proprietà specificate nella sezione Proprietà - (VARIABILE=${VARIABILE}). + proprietà Java. Ciò è richiesto raramente perché Jenkins le fornisce comunque + sotto forma di variabili d'ambiente. La modalità preferita di accesso alle + variabili di compilazione di Jenkins è la loro mappatura in proprietà + specificate nella sezione + Proprietà + ( + VARIABILE=${VARIABILE} + ).
diff --git a/core/src/main/resources/hudson/tasks/Maven/help-properties.html b/core/src/main/resources/hudson/tasks/Maven/help-properties.html index cb607eb5f4..9319d464d6 100644 --- a/core/src/main/resources/hudson/tasks/Maven/help-properties.html +++ b/core/src/main/resources/hudson/tasks/Maven/help-properties.html @@ -1,8 +1,12 @@
- Properties needed by your Maven build can be specified here (in the standard properties file format): - 
# comment
+  Properties needed by your Maven build can be specified here (in the standard
+  properties file format):
+  
+# comment
 name1=value1
 name2=value2
-

-  These are passed to Maven like "-Dname1=value1 -Dname2=value2"
+
+ These are passed to Maven like + "-Dname1=value1 -Dname2=value2"
diff --git a/core/src/main/resources/hudson/tasks/Maven/help-properties_bg.html b/core/src/main/resources/hudson/tasks/Maven/help-properties_bg.html index 3e1a7e9ab4..d368f99036 100644 --- a/core/src/main/resources/hudson/tasks/Maven/help-properties_bg.html +++ b/core/src/main/resources/hudson/tasks/Maven/help-properties_bg.html @@ -1,9 +1,13 @@
- Тук се задават свойствата, които се използват от изграждането на Maven, - в стандартен формат „.properties“: - 
# коментар
+  Тук се задават свойствата, които се използват от изграждането на Maven, в
+  стандартен формат „.properties“:
+  
+# коментар
 име1=стойност1
 име2=стойност2
-

-  Те се подават към Maven като „-Dиме1=стойност1 -Dиме2=стойност2“
+
+ Те се подават към Maven като „ + -Dиме1=стойност1 -Dиме2=стойност2 + “
diff --git a/core/src/main/resources/hudson/tasks/Maven/help-properties_de.html b/core/src/main/resources/hudson/tasks/Maven/help-properties_de.html index 7c824f1cf9..3c235dc51b 100644 --- a/core/src/main/resources/hudson/tasks/Maven/help-properties_de.html +++ b/core/src/main/resources/hudson/tasks/Maven/help-properties_de.html @@ -1,10 +1,15 @@
- Legen Sie hier Eigenschaften fest, die Ihr Maven-Build benötigt (im üblichen Properties-Dateiformat): + Legen Sie hier Eigenschaften fest, die Ihr Maven-Build benötigt (im üblichen + Properties-Dateiformat): - 
# comment
+  
+# comment
 name1=value1
 name2=value2
-

+
- Diese Eigenschaften werden an Maven wie "-Dname1=value1 -Dname2=value2" weitergegeben. + Diese Eigenschaften werden an Maven wie + "-Dname1=value1 -Dname2=value2" + weitergegeben.
diff --git a/core/src/main/resources/hudson/tasks/Maven/help-properties_fr.html b/core/src/main/resources/hudson/tasks/Maven/help-properties_fr.html index e65cc49d3f..42cb6a80a0 100644 --- a/core/src/main/resources/hudson/tasks/Maven/help-properties_fr.html +++ b/core/src/main/resources/hudson/tasks/Maven/help-properties_fr.html @@ -1,8 +1,12 @@ 
- Les propriétés nécessaires pour votre build Maven peuvent être spécifiées ici (avec le format standard des fichiers de propriétés): - 
# commentaire
+  Les propriétés nécessaires pour votre build Maven peuvent être spécifiées ici
+  (avec le format standard des fichiers de propriétés):
+  
+# commentaire
 nom1=valeur1
 nom2=valeur2
-

-  Ces propriétés sont passées à Maven ainsi: "-Dnom1=valeur1 -Dnom2=valeur2"
+
+ Ces propriétés sont passées à Maven ainsi: + "-Dnom1=valeur1 -Dnom2=valeur2"
diff --git a/core/src/main/resources/hudson/tasks/Maven/help-properties_it.html b/core/src/main/resources/hudson/tasks/Maven/help-properties_it.html index 91442c8de8..5612cb2e09 100644 --- a/core/src/main/resources/hudson/tasks/Maven/help-properties_it.html +++ b/core/src/main/resources/hudson/tasks/Maven/help-properties_it.html @@ -1,9 +1,12 @@
- Le proprietà richieste dalla compilazione Maven possono essere specificate - qui (nel formato di file standard delle proprietà): - 
# commento
+  Le proprietà richieste dalla compilazione Maven possono essere specificate qui
+  (nel formato di file standard delle proprietà):
+  
+# commento
 nome1=valore1
 nome2=valore2
-

-  Queste sono fornite a Maven come segue: "-Dnome1=valore1 -Dnome2=valore2"
+
+ Queste sono fornite a Maven come segue: + "-Dnome1=valore1 -Dnome2=valore2"
diff --git a/core/src/main/resources/hudson/tasks/Maven/help-properties_ja.html b/core/src/main/resources/hudson/tasks/Maven/help-properties_ja.html index d0020fb449..ad155053a8 100644 --- a/core/src/main/resources/hudson/tasks/Maven/help-properties_ja.html +++ b/core/src/main/resources/hudson/tasks/Maven/help-properties_ja.html @@ -1,8 +1,12 @@
Mavenでのビルドで必要となるプロパティをここに(標準のプロパティファイル形式で)指定します。: - 
# comment
+  
+# comment
 name1=value1
 name2=value2
-

-  これらのプロパティは、Mavenに"-Dname1=value1 -Dname2=value2"のように渡されます。
+
+ これらのプロパティは、Mavenに + "-Dname1=value1 -Dname2=value2" + のように渡されます。
diff --git a/core/src/main/resources/hudson/tasks/Maven/help-properties_zh_TW.html b/core/src/main/resources/hudson/tasks/Maven/help-properties_zh_TW.html index 476726dbf4..5c0d9e3fc5 100644 --- a/core/src/main/resources/hudson/tasks/Maven/help-properties_zh_TW.html +++ b/core/src/main/resources/hudson/tasks/Maven/help-properties_zh_TW.html @@ -1,9 +1,12 @@
Maven 建置需要的屬性可以設在這裡 (使用標準 properties 檔案格式): -
+  
 # 註解
 name1=value1
 name2=value2
-

-  會以 "-Dname1=value1 -Dname2=value2" 這種形式傳進 Maven。
+
+ 會以 + "-Dname1=value1 -Dname2=value2" + 這種形式傳進 Maven。
diff --git a/core/src/main/resources/hudson/tasks/Maven/help-settings.html b/core/src/main/resources/hudson/tasks/Maven/help-settings.html index 216e07a559..9d852851fd 100644 --- a/core/src/main/resources/hudson/tasks/Maven/help-settings.html +++ b/core/src/main/resources/hudson/tasks/Maven/help-settings.html @@ -1,20 +1,36 @@
- The settings element in the settings.xml file contains elements used - to define values which configure Maven execution in various ways, like the pom.xml, - but should not be bundled to any specific project, or distributed to an audience. - These include values such as the local repository location, alternate remote repository servers, - and authentication information. -
- There are two locations where a settings.xml file per default may live: + The settings element in the + settings.xml + file contains elements used to define values which configure Maven execution + in various ways, like the + pom.xml + , but should not be bundled to any specific project, or distributed to an + audience. These include values such as the local repository location, + alternate remote repository servers, and authentication information. +
+ There are two locations where a + settings.xml + file per default may live:
    -
  • The Maven install - default: $M2_HOME/conf/settings.xml
    • -
  • A user's install - default: ${user.home}/.m2/settings.xml
    • +
  • + The Maven install - default: + $M2_HOME/conf/settings.xml +
    • +
  • + A user's install - default: + ${user.home}/.m2/settings.xml +
- The former settings.xml are also called global settings, the latter settings.xml are - referred to as user settings. If both files exists, their contents gets merged, - with the user-specific settings.xml being dominant. + The former settings.xml are also called global settings, the latter + settings.xml are referred to as user settings. If both files exists, their + contents gets merged, with the user-specific settings.xml being dominant.

- see also: settings.xml reference -

\ No newline at end of file + see also: + + settings.xml + reference + +

+ diff --git a/core/src/main/resources/hudson/tasks/Maven/help-settings_bg.html b/core/src/main/resources/hudson/tasks/Maven/help-settings_bg.html index f0fdc5000a..485cc60f89 100644 --- a/core/src/main/resources/hudson/tasks/Maven/help-settings_bg.html +++ b/core/src/main/resources/hudson/tasks/Maven/help-settings_bg.html @@ -1,20 +1,38 @@ -
- Елементът за настройки във файла settings.xml съдържа стойности, които - влияят на изпълнението на Maven по различни начини, подобно на файла pom.xml, - но не принадлежат на никой проект поотделно и не следва да се разпространяват с тях. - Това включва местоположението на локалното хранилище, допълнителни отдалечени хранилища за - код и обекти и информация за идентификация. -
- Стандартно файлътsettings.xml се чете от следните места: +
+ Елементът за настройки във файла + settings.xml + съдържа стойности, които влияят на изпълнението на Maven по различни начини, + подобно на файла + pom.xml + , но не принадлежат на никой проект поотделно и не следва да се + разпространяват с тях. Това включва местоположението на локалното хранилище, + допълнителни отдалечени хранилища за код и обекти и информация за + идентификация. +
+ Стандартно файлът + settings.xml + се чете от следните места:
    -
  • системната инсталация на Maven — стандартно е $M2_HOME/conf/settings.xml
    • -
  • потребителската инсталация на Maven — стандартно е ${user.home}/.m2/settings.xml
    • +
  • + системната инсталация на Maven — стандартно е + $M2_HOME/conf/settings.xml +
    • +
  • + потребителската инсталация на Maven — стандартно е + ${user.home}/.m2/settings.xml +
- Първото е мястото на глобалните настройки, а второто са настройките за отделен потребител. Ако и двата - файла съществуват, те се четат и сливат, като потребителските настройки са с приоритет. + Първото е мястото на глобалните настройки, а второто са настройките за отделен + потребител. Ако и двата файла съществуват, те се четат и сливат, като + потребителските настройки са с приоритет.

- За повече информация вижте settings.xml - документацията. + За повече информация вижте + + settings.xml + документацията + + . +

diff --git a/core/src/main/resources/hudson/tasks/Maven/help-settings_it.html b/core/src/main/resources/hudson/tasks/Maven/help-settings_it.html index 40a907467b..bba5740aa4 100644 --- a/core/src/main/resources/hudson/tasks/Maven/help-settings_it.html +++ b/core/src/main/resources/hudson/tasks/Maven/help-settings_it.html @@ -1,25 +1,43 @@
- L'elemento settings nel file settings.xml contiene - degli elementi utilizzati per definire valori che configurano l'esecuzione - di Maven in vari modi, come accade per il file pom.xml, ma - non dovrebbe essere incorporato in un progetto specifico o distribuito + L'elemento + settings + nel file + settings.xml + contiene degli elementi utilizzati per definire valori che configurano + l'esecuzione di Maven in vari modi, come accade per il file + pom.xml + , ma non dovrebbe essere incorporato in un progetto specifico o distribuito pubblicamente. Questi elementi includono valori come il percorso del repository locale, server repository remoti alternativi e informazioni di autenticazione. -
- Ci sono due percorsi dove può essere collocato un file settings.xml +
+ Ci sono due percorsi dove può essere collocato un file + settings.xml per impostazione predefinita:
    -
  • Il percorso di installazione di Maven - impostazione predefinita: $M2_HOME/conf/settings.xml
    • -
  • Il percorso di installazione utente - impostazione predefinita: ${user.home}/.m2/settings.xml
    • +
  • + Il percorso di installazione di Maven - impostazione predefinita: + $M2_HOME/conf/settings.xml +
    • +
  • + Il percorso di installazione utente - impostazione predefinita: + ${user.home}/.m2/settings.xml +
- Il primo file settings.xml contiene quelle che vengono chiamate - impostazioni globali, il secondo quelle a cui si fa riferimento come - impostazioni utente. Se esistono entrambi i file, i loro contenuti vengono - uniti e prevarranno le impostazioni del file settings.xml + Il primo file + settings.xml + contiene quelle che vengono chiamate impostazioni globali, il secondo quelle a + cui si fa riferimento come impostazioni utente. Se esistono entrambi i file, i + loro contenuti vengono uniti e prevarranno le impostazioni del file + settings.xml dell'utente.

- Si veda anche: Informazioni di riferimento settings.xml + Si veda anche: + + Informazioni di riferimento + settings.xml + +

diff --git a/core/src/main/resources/hudson/tasks/Maven/help-settings_zh_TW.html b/core/src/main/resources/hudson/tasks/Maven/help-settings_zh_TW.html index 523dac44e5..43360a2b1f 100644 --- a/core/src/main/resources/hudson/tasks/Maven/help-settings_zh_TW.html +++ b/core/src/main/resources/hudson/tasks/Maven/help-settings_zh_TW.html @@ -1,17 +1,33 @@
- settings.xml 中的 settings 元素，就像 pom.xml一樣，包含可以定義 Maven 執行方式的各種元素。 + settings.xml + 中的 settings 元素，就像 + pom.xml + 一樣，包含可以定義 Maven 執行方式的各種元素。 裡面的內容都是不應該跟特定專案綁死，或是可以散佈出去的。 例如本地端儲存庫的位置、替代用遠端儲存庫伺服器以及驗證資訊。 -
- 預設有兩個地方會有 settings.xml 檔: +
+ 預設有兩個地方會有 + settings.xml + 檔:
    -
  • Maven 安裝目錄 - 預設位置: $M2_HOME/conf/settings.xml
    • -
  • 使用者各別設定 - 預設位置: ${user.home}/.m2/settings.xml
    • +
  • + Maven 安裝目錄 - 預設位置: + $M2_HOME/conf/settings.xml +
    • +
  • + 使用者各別設定 - 預設位置: + ${user.home}/.m2/settings.xml +
第一個 settings.xml 也叫做全域設定，後面那個叫做使用者設定。 兩者同時存在時，內容會合併，但以使用者自定的 settings.xml 為準。

- 請參考: settings.xml 參考資料 -

\ No newline at end of file + 請參考: + + settings.xml + 參考資料 + +

+
diff --git a/core/src/main/resources/hudson/tasks/Shell/help-shell.html b/core/src/main/resources/hudson/tasks/Shell/help-shell.html index b83343f6f4..143c3039a3 100644 --- a/core/src/main/resources/hudson/tasks/Shell/help-shell.html +++ b/core/src/main/resources/hudson/tasks/Shell/help-shell.html @@ -1,5 +1,10 @@
- Normally you should just leave this field empty and let Jenkins pick up the right shell executable. - If your sh (Windows) or /bin/sh binary exists outside your PATH, however, - specify the absolute path to the shell executable. + Normally you should just leave this field empty and let Jenkins pick up the + right shell executable. If your + sh + (Windows) or + /bin/sh + binary exists outside your + PATH + , however, specify the absolute path to the shell executable.
diff --git a/core/src/main/resources/hudson/tasks/Shell/help-shell_bg.html b/core/src/main/resources/hudson/tasks/Shell/help-shell_bg.html index 4586273f78..17d6b7a21a 100644 --- a/core/src/main/resources/hudson/tasks/Shell/help-shell_bg.html +++ b/core/src/main/resources/hudson/tasks/Shell/help-shell_bg.html @@ -1,5 +1,10 @@
- Обикновено това поле трябва да е празно, а Jenkins сам ще подбере правилния интерпретатор. - Ако обаче sh (под Windows) или /bin/sh е извън пътя сочен от PATH, - тук ще трябва да зададете пътя към изпълнимия файл на интерпретатора. + Обикновено това поле трябва да е празно, а Jenkins сам ще подбере правилния + интерпретатор. Ако обаче + sh + (под Windows) или + /bin/sh + е извън пътя сочен от + PATH + , тук ще трябва да зададете пътя към изпълнимия файл на интерпретатора.
diff --git a/core/src/main/resources/hudson/tasks/Shell/help-shell_de.html b/core/src/main/resources/hudson/tasks/Shell/help-shell_de.html index 495ab2d699..902f167346 100644 --- a/core/src/main/resources/hudson/tasks/Shell/help-shell_de.html +++ b/core/src/main/resources/hudson/tasks/Shell/help-shell_de.html @@ -1,6 +1,12 @@
- Im Regelfall sollten Sie dieses Feld leerlassen und Jenkins die richtige Shell-Installation - wählen lassen. Falls Ihre sh (Windows) oder /bin/sh Kommandozeilenanwendung - nicht über die PATH Umgebungsvariable gefunden werden kann, geben Sie den absoluten Pfad - zur sh Kommandozeilenanwendung an. + Im Regelfall sollten Sie dieses Feld leerlassen und Jenkins die richtige + Shell-Installation wählen lassen. Falls Ihre + sh + (Windows) oder + /bin/sh + Kommandozeilenanwendung nicht über die + PATH + Umgebungsvariable gefunden werden kann, geben Sie den absoluten Pfad zur + sh + Kommandozeilenanwendung an.
diff --git a/core/src/main/resources/hudson/tasks/Shell/help-shell_fr.html b/core/src/main/resources/hudson/tasks/Shell/help-shell_fr.html index faf53c672c..3b833206fb 100644 --- a/core/src/main/resources/hudson/tasks/Shell/help-shell_fr.html +++ b/core/src/main/resources/hudson/tasks/Shell/help-shell_fr.html @@ -1,6 +1,10 @@
- En général, ce champ peut rester vide pour laisser Jenkins - choisir le bon sh. - Néanmoins, si votre binaire sh (Windows) ou /bin/sh est placé hors de votre - PATH, spécifiez le chemin absolu vers l'exécutable sh. + En général, ce champ peut rester vide pour laisser Jenkins choisir le bon sh. + Néanmoins, si votre binaire + sh + (Windows) ou + /bin/sh + est placé hors de votre + PATH + , spécifiez le chemin absolu vers l'exécutable sh.
diff --git a/core/src/main/resources/hudson/tasks/Shell/help-shell_it.html b/core/src/main/resources/hudson/tasks/Shell/help-shell_it.html index 0c8c604499..fbe182fd0a 100644 --- a/core/src/main/resources/hudson/tasks/Shell/help-shell_it.html +++ b/core/src/main/resources/hudson/tasks/Shell/help-shell_it.html @@ -1,6 +1,10 @@
Normalmente si dovrebbe lasciare questo campo vuoto e far sì che Jenkins - scelga l'eseguibile shell corretto. Ciò nonostante, se i binari sh - (su Windows) o /bin/sh sono al di fuori del proprio PATH, - specificare il percorso assoluto all'eseguibile shell. + scelga l'eseguibile shell corretto. Ciò nonostante, se i binari + sh + (su Windows) o + /bin/sh + sono al di fuori del proprio + PATH + , specificare il percorso assoluto all'eseguibile shell.
diff --git a/core/src/main/resources/hudson/tasks/Shell/help-shell_ja.html b/core/src/main/resources/hudson/tasks/Shell/help-shell_ja.html index e57aae6ac7..d632558840 100644 --- a/core/src/main/resources/hudson/tasks/Shell/help-shell_ja.html +++ b/core/src/main/resources/hudson/tasks/Shell/help-shell_ja.html @@ -1,4 +1,9 @@
- 通常、この項目を空欄のままにしてJenkinsに正しいシェルを検出させます。 - もし、sh(Windows)や/bin/shがPATHに含まれていない場合、シェルの絶対パスを指定します。 + 通常、この項目を空欄のままにしてJenkinsに正しいシェルを検出させます。 もし、 + sh + (Windows)や + /bin/sh + が + PATH + に含まれていない場合、シェルの絶対パスを指定します。
diff --git a/core/src/main/resources/hudson/tasks/Shell/help-shell_nl.html b/core/src/main/resources/hudson/tasks/Shell/help-shell_nl.html index 3dd30fd2b3..eb2c19e192 100644 --- a/core/src/main/resources/hudson/tasks/Shell/help-shell_nl.html +++ b/core/src/main/resources/hudson/tasks/Shell/help-shell_nl.html @@ -1,5 +1,10 @@
-Normaal dient u dit veld leeg te laten. Jenkins pikt dan zelf het juiste shell programma op. -Indien het sh (Windows) of /bin/sh programma dat u wenst te gebruiken echter buiten het -PATH ligt, dan kunt u hier het absolute pad naar uw shell programma invullen. + Normaal dient u dit veld leeg te laten. Jenkins pikt dan zelf het juiste shell + programma op. Indien het + sh + (Windows) of + /bin/sh + programma dat u wenst te gebruiken echter buiten het + PATH + ligt, dan kunt u hier het absolute pad naar uw shell programma invullen.
diff --git a/core/src/main/resources/hudson/tasks/Shell/help-shell_pt_BR.html b/core/src/main/resources/hudson/tasks/Shell/help-shell_pt_BR.html index 1aff49d4b7..6acd0cf0e5 100644 --- a/core/src/main/resources/hudson/tasks/Shell/help-shell_pt_BR.html +++ b/core/src/main/resources/hudson/tasks/Shell/help-shell_pt_BR.html @@ -1,5 +1,10 @@
- Normalmente você deveria apenas deixar este campo vazio e deixar que o Jenkins escolha o sh correto. - Se seu binário sh (Windows) ou /bin/sh está fora de seu PATH, entretanto, especifique o caminho - absoluto para o executável sh. + Normalmente você deveria apenas deixar este campo vazio e deixar que o + Jenkins escolha o sh correto. Se seu binário + sh + (Windows) ou + /bin/sh + está fora de seu + PATH + , entretanto, especifique o caminho absoluto para o executável sh.
diff --git a/core/src/main/resources/hudson/tasks/Shell/help-shell_zh_TW.html b/core/src/main/resources/hudson/tasks/Shell/help-shell_zh_TW.html index 3bbdb267da..ab4a621f1b 100644 --- a/core/src/main/resources/hudson/tasks/Shell/help-shell_zh_TW.html +++ b/core/src/main/resources/hudson/tasks/Shell/help-shell_zh_TW.html @@ -1,5 +1,10 @@
- 一般情況下您應該不會在這個欄位裡填任何東西，Jenkins 會自動挑選合適的 Shell 執行檔。 - 然而，如果您的 sh (Windows) 或 /bin/sh 執行檔不在 - PATH 路徑裡，可以在此指定該 Shell 執行檔的絕對路徑。 -
\ No newline at end of file + 一般情況下您應該不會在這個欄位裡填任何東西，Jenkins 會自動挑選合適的 Shell + 執行檔。 然而，如果您的 + sh + (Windows) 或 + /bin/sh + 執行檔不在 + PATH + 路徑裡，可以在此指定該 Shell 執行檔的絕對路徑。 + diff --git a/core/src/main/resources/hudson/tasks/Shell/help-unstableReturn.html b/core/src/main/resources/hudson/tasks/Shell/help-unstableReturn.html index bc6426fa3d..3dcc56216d 100644 --- a/core/src/main/resources/hudson/tasks/Shell/help-unstableReturn.html +++ b/core/src/main/resources/hudson/tasks/Shell/help-unstableReturn.html @@ -1,5 +1,7 @@
- If set, the shell exit code that will be interpreted as an unstable build result. If the exit code matches the value, - the build results will be set to 'unstable' and next steps will be continued. On Unix-like it is a value between 0-255. - The value 0 is ignored and does not make the build unstable to keep the default behaviour consistent. + If set, the shell exit code that will be interpreted as an unstable build + result. If the exit code matches the value, the build results will be set to + 'unstable' and next steps will be continued. On Unix-like it is a value + between 0-255. The value 0 is ignored and does not make the build unstable to + keep the default behaviour consistent.
diff --git a/core/src/main/resources/hudson/tasks/Shell/help-unstableReturn_bg.html b/core/src/main/resources/hudson/tasks/Shell/help-unstableReturn_bg.html index 15d9c0fd79..3ed5eca9d1 100644 --- a/core/src/main/resources/hudson/tasks/Shell/help-unstableReturn_bg.html +++ b/core/src/main/resources/hudson/tasks/Shell/help-unstableReturn_bg.html @@ -1,8 +1,9 @@
- Когато е зададена стойност, тя ще се интерпретира като изходния код, който указва нестабилно - изграждане. Ако изходният код за грешка съвпада с тази стойност, изграждането се приема за - нестабилно, но се продължава със следващите стъпки. Поддържа се най-широкия диапазон от - стойности за фамилията Windows. При Unix това е еднобайтова целочислена стойност - от 0 до 255. Стойност 0 се прескача и не води до обявяването на изграждането на нестабилно, - защото това е конвенцията. + Когато е зададена стойност, тя ще се интерпретира като изходния код, който + указва нестабилно изграждане. Ако изходният код за грешка съвпада с тази + стойност, изграждането се приема за нестабилно, но се продължава със + следващите стъпки. Поддържа се най-широкия диапазон от стойности за фамилията + Windows. При Unix това е еднобайтова целочислена стойност от 0 до 255. + Стойност 0 се прескача и не води до обявяването на изграждането на нестабилно, + защото това е конвенцията.
diff --git a/core/src/main/resources/hudson/tasks/Shell/help-unstableReturn_it.html b/core/src/main/resources/hudson/tasks/Shell/help-unstableReturn_it.html index 447d323263..12e52b4016 100644 --- a/core/src/main/resources/hudson/tasks/Shell/help-unstableReturn_it.html +++ b/core/src/main/resources/hudson/tasks/Shell/help-unstableReturn_it.html @@ -1,9 +1,9 @@
- Se quest'opzione è impostata, specifica il codice di uscita della shell - che sarà interpretato come risultato di una compilazione instabile. Se il - codice di uscita corrisponde al valore, il risultato della compilazione - sarà impostato a "instabile" e i passaggi successivi saranno eseguiti. - Sui sistemi UNIX-like è un valore compreso tra 0 e 255. Il valore 0 è - ignorato e non rende la compilazione instabile, in modo da mantenere il - comportamento predefinito consistente. + Se quest'opzione è impostata, specifica il codice di uscita della shell che + sarà interpretato come risultato di una compilazione instabile. Se il codice + di uscita corrisponde al valore, il risultato della compilazione sarà + impostato a "instabile" e i passaggi successivi saranno eseguiti. Sui sistemi + UNIX-like è un valore compreso tra 0 e 255. Il valore 0 è ignorato e non rende + la compilazione instabile, in modo da mantenere il comportamento predefinito + consistente.
diff --git a/core/src/main/resources/hudson/tasks/Shell/help.html b/core/src/main/resources/hudson/tasks/Shell/help.html index 0ab3beb6f2..7f2510f783 100644 --- a/core/src/main/resources/hudson/tasks/Shell/help.html +++ b/core/src/main/resources/hudson/tasks/Shell/help.html @@ -1,17 +1,29 @@
- Runs a shell script (defaults to sh, but this is configurable) for building the project. - The script will be run with the workspace as the current directory. Type in the contents of your shell - script. If your shell script has no header line like #!/bin/sh —, then the shell configured - system-wide will be used, but you can also use the header line to write script in another language - (like #!/bin/perl) or control the options that shell uses. + Runs a shell script (defaults to + sh + , but this is configurable) for building the project. The script will be run + with the workspace as the current directory. Type in the contents of your + shell script. If your shell script has no header line like + #!/bin/sh + —, then the shell configured system-wide will be used, but you can also + use the header line to write script in another language (like + #!/bin/perl + ) or control the options that shell uses.

- By default, the shell will be invoked with the "-ex" option. So all of the commands are printed before being executed, - and the build is considered a failure if any of the commands exits with a non-zero exit code. Again, add the - #!/bin/... line to change this behavior. + By default, the shell will be invoked with the "-ex" option. So all of the + commands are printed before being executed, and the build is considered a + failure if any of the commands exits with a non-zero exit code. Again, add + the + #!/bin/... + line to change this behavior. +

- As a best practice, try not to put a long shell script in here. Instead, consider adding the shell script - in SCM and simply call that shell script from Jenkins (via bash -ex myscript.sh or something like that), - so that you can track changes in your shell script. + As a best practice, try not to put a long shell script in here. Instead, + consider adding the shell script in SCM and simply call that shell script + from Jenkins (via + bash -ex myscript.sh + or something like that), so that you can track changes in your shell script. +

diff --git a/core/src/main/resources/hudson/tasks/Shell/help_bg.html b/core/src/main/resources/hudson/tasks/Shell/help_bg.html index 3eba4b7ab8..2ef01fb3a2 100644 --- a/core/src/main/resources/hudson/tasks/Shell/help_bg.html +++ b/core/src/main/resources/hudson/tasks/Shell/help_bg.html @@ -1,19 +1,33 @@
- Изпълнение на скрипт чрез интерпретатор за изграждането на проект (стандартно е sh, - но може да се настрои). Текущата директория за изпълнението на скрипта е директорията на - работното пространство. Попълнете тук съдържанието на скрипта. Ако в началото му - липсва заглавен ред от вида: #!/bin/sh, ще се използва системният интерпретатор. - Ако в началото на скрипта има ред от вида: #!/bin/perl, ще можете да използвате - произволен интерпретатор и ще можете изрично да задавате с какви опции ще се стартира. + Изпълнение на скрипт чрез интерпретатор за изграждането на проект (стандартно + е + sh + , но може да се настрои). Текущата директория за изпълнението на скрипта е + директорията на работното пространство. Попълнете тук съдържанието на скрипта. + Ако в началото му липсва заглавен ред от вида: + #!/bin/sh + , ще се използва системният интерпретатор. Ако в началото на скрипта има ред + от вида: + #!/bin/perl + , ще можете да използвате произволен интерпретатор и ще можете изрично да + задавате с какви опции ще се стартира.

- Стандартно интерпретаторът се извиква с опцията -ex. Така всички команди се - отпечатват преди изпълнение, а изграждането се счита за неуспешно, ако някоя от - командите завърши с код, различен от 0. Може да промените това поведение, - като зададете начален ред за указване на интерпретатора като #!/bin/…. + Стандартно интерпретаторът се извиква с опцията + -ex + . Така всички команди се отпечатват преди изпълнение, а изграждането се + счита за неуспешно, ако някоя от командите завърши с код, различен от + 0 + . Може да промените това поведение, като зададете начален ред за указване на + интерпретатора като + #!/bin/… + . +

- Добра практика е да не задавате голям скрипт тук. По-добре е да го сложите в системата - за контрол на версиите, а тук просто да го извикате чрез bash -ex myscript.sh - или нещо подобно. Така ще може да следите промените в скрипта. + Добра практика е да не задавате голям скрипт тук. По-добре е да го сложите в + системата за контрол на версиите, а тук просто да го извикате чрез + bash -ex myscript.sh + или нещо подобно. Така ще може да следите промените в скрипта. +

diff --git a/core/src/main/resources/hudson/tasks/Shell/help_de.html b/core/src/main/resources/hudson/tasks/Shell/help_de.html index b7821f6313..005abd7e2b 100644 --- a/core/src/main/resources/hudson/tasks/Shell/help_de.html +++ b/core/src/main/resources/hudson/tasks/Shell/help_de.html @@ -1,16 +1,20 @@ -
+
+ Führt ein Shell-Skript aus, um das Projekt zu bauen (Vorgabewert für die Shell ist - sh, aber dies ist konfigurierbar). Das Skript wird im Arbeitsbereich - als aktuelles Verzeichnis ausgeführt. Geben Sie den Inhalt Ihres - Shell-Skriptes direkt in die Textbox ein, jedoch ohne die Kopfzeile - #!/bin/sh — diese wird von Jenkins, entsprechend der - systemweiten Konfiguration, hinzugefügt. + sh + , aber dies ist konfigurierbar). Das Skript wird im Arbeitsbereich als + aktuelles Verzeichnis ausgeführt. Geben Sie den Inhalt Ihres Shell-Skriptes + direkt in die Textbox ein, jedoch ohne die Kopfzeile + #!/bin/sh + — diese wird von Jenkins, entsprechend der systemweiten Konfiguration, + hinzugefügt.

Die Shell wird mit der Option - -ex ausgeführt. Dadurch werden alle Kommandos ausgegeben, bevor sie - ausgeführt werden. Der Build gilt als fehlgeschlagen, wenn einer der - Kommandos in der Befehlszeile einen Ergebniscode ungleich 0 liefert. + -ex + ausgeführt. Dadurch werden alle Kommandos ausgegeben, bevor sie ausgeführt + werden. Der Build gilt als fehlgeschlagen, wenn einer der Kommandos in der + Befehlszeile einen Ergebniscode ungleich 0 liefert.

Es hat sich in der Praxis nicht bewährt, allzulange Skripte an dieser Stelle @@ -18,4 +22,5 @@ als Teil Ihres Codes unter Versionskontrolle zu stellen und lediglich von hier aus aufzurufen. Dadurch können Sie Änderungen in Ihrem Skript wesentlich leichter nachverfolgen. +

diff --git a/core/src/main/resources/hudson/tasks/Shell/help_fr.html b/core/src/main/resources/hudson/tasks/Shell/help_fr.html index 5460bb3ecc..d82c76740b 100644 --- a/core/src/main/resources/hudson/tasks/Shell/help_fr.html +++ b/core/src/main/resources/hudson/tasks/Shell/help_fr.html @@ -1,19 +1,29 @@
- Lance un script Shell (par défaut à l'aide de sh, mais cela est configurable) pour construire le projet. - Le script sera lancé avec le workspace comme répertoire courant. - Entrez le contenu de votre script shell. Si votre script n'a pas de ligne de titre du type #!/bin/sh, - alors le shell configuré pour l'ensemble du système sera utilisé. - Si votre script contient une telle ligne, vous pourrez utiliser un autre langage de script - (comme #!/bin/perl) ou contrôler les options que le shell utilise. + Lance un script Shell (par défaut à l'aide de + sh + , mais cela est configurable) pour construire le projet. Le script sera lancé + avec le workspace comme répertoire courant. Entrez le contenu de votre script + shell. Si votre script n'a pas de ligne de titre du type + #!/bin/sh + , alors le shell configuré pour l'ensemble du système sera utilisé. Si votre + script contient une telle ligne, vous pourrez utiliser un autre langage de + script (comme + #!/bin/perl + ) ou contrôler les options que le shell utilise.

- Par défaut, le shell sera invoqué avec l'option "-ex". Par conséquent, toutes les commandes seront - affichées avant d'être exécutées et le build sera considéré en èchec si l'une de ces commandes - renvoie un code de retour différent de zéro. - Encore une fois, vous pouvez ajouter la ligne #!/bin/... pour modifier ce comportement. + Par défaut, le shell sera invoqué avec l'option "-ex". Par conséquent, + toutes les commandes seront affichées avant d'être exécutées et le build + sera considéré en èchec si l'une de ces commandes renvoie un code de retour + différent de zéro. Encore une fois, vous pouvez ajouter la ligne + #!/bin/... + pour modifier ce comportement. +

- Une bonne pratique est de ne pas mettre un long script ici. A la place, pensez à ajouter le script shell - dans l'outil de gestion de configuration et appelez simplement ce script depuis Jenkins. - Ainsi, vous garderez trace des changements apportés à votre script. + Une bonne pratique est de ne pas mettre un long script ici. A la place, + pensez à ajouter le script shell dans l'outil de gestion de configuration et + appelez simplement ce script depuis Jenkins. Ainsi, vous garderez trace des + changements apportés à votre script. +

diff --git a/core/src/main/resources/hudson/tasks/Shell/help_it.html b/core/src/main/resources/hudson/tasks/Shell/help_it.html index 629e1010e8..1c0a75d99f 100644 --- a/core/src/main/resources/hudson/tasks/Shell/help_it.html +++ b/core/src/main/resources/hudson/tasks/Shell/help_it.html @@ -1,25 +1,34 @@
- Esegue uno script shell (per impostazione predefinita sh, ma il - parametro è configurabile) per compilare il progetto. Lo script sarà + Esegue uno script shell (per impostazione predefinita + sh + , ma il parametro è configurabile) per compilare il progetto. Lo script sarà eseguito impostando la directory dello spazio di lavoro come directory - corrente. Immettere i contenuti dello script shell. Se lo script shell non - ha una riga di intestazione come #!/bin/sh, sarà utilizzata la - shell configurata a livello di sistema, ma è anche possibile utilizzare la - riga di intestazione per scrivere lo script in un altro linguaggio (ad - esempio #!/bin/perl) o per controllare le opzioni utilizzate dalla - shell. + corrente. Immettere i contenuti dello script shell. Se lo script shell non ha + una riga di intestazione come + #!/bin/sh + , sarà utilizzata la shell configurata a livello di sistema, ma è anche + possibile utilizzare la riga di intestazione per scrivere lo script in un + altro linguaggio (ad esempio + #!/bin/perl + ) o per controllare le opzioni utilizzate dalla shell.

- Per impostazione predefinita, la shell sarà invocata con l'opzione "-ex". In - questo modo tutti i comandi saranno stampati prima di essere eseguiti e la - compilazione sarà considerata non riuscita se uno qualunque dei comandi esce - con un codice di uscita diverso da zero. Ancora una volta, si aggiunga la - riga #!/bin/... per modificare questo comportamento. + Per impostazione predefinita, la shell sarà invocata con l'opzione "-ex". In + questo modo tutti i comandi saranno stampati prima di essere eseguiti e la + compilazione sarà considerata non riuscita se uno qualunque dei comandi esce + con un codice di uscita diverso da zero. Ancora una volta, si aggiunga la + riga + #!/bin/... + per modificare questo comportamento. +

- Come procedura consigliata, non si tenti di immettere uno script shell - corposo qui. Si consideri piuttosto l'aggiunta dello script shell al sistema - di gestione del codice sorgente, quindi semplicemente lo si richiami da - Jenkins (tramite bash -ex mioscript.sh o un'invocazione simile), - in modo da poter tracciare le modifiche al proprio script shell. + Come procedura consigliata, non si tenti di immettere uno script shell + corposo qui. Si consideri piuttosto l'aggiunta dello script shell al sistema + di gestione del codice sorgente, quindi semplicemente lo si richiami da + Jenkins (tramite + bash -ex mioscript.sh + o un'invocazione simile), in modo da poter tracciare le modifiche al proprio + script shell. +

diff --git a/core/src/main/resources/hudson/tasks/Shell/help_ja.html b/core/src/main/resources/hudson/tasks/Shell/help_ja.html index 0b91f5857c..823dec344a 100644 --- a/core/src/main/resources/hudson/tasks/Shell/help_ja.html +++ b/core/src/main/resources/hudson/tasks/Shell/help_ja.html @@ -1,15 +1,25 @@ 
- プロジェクトのビルドに、シェルスクリプト(デフォルトはshですが、設定可能です)を起動します。 + プロジェクトのビルドに、シェルスクリプト(デフォルトは + sh + ですが、設定可能です)を起動します。 シェルスクリプトは、ワークスペースをカレントディレクトリとして起動します。 - シェルスクリプトを記述してください。もし、#!/bin/shのようなヘッダがなければ、システムの設定で設定したシェルを使用しますが、 - ヘッダを使用して、(#!/bin/perlのように)他の言語を使用したスクリプトを書いたり、シェルのオプションを制御できます。 + シェルスクリプトを記述してください。もし、 + #!/bin/sh + のようなヘッダがなければ、システムの設定で設定したシェルを使用しますが、 + ヘッダを使用して、( + #!/bin/perl + のように)他の言語を使用したスクリプトを書いたり、シェルのオプションを制御できます。

- デフォルトで、シェルは"-ex"オプションを付けて起動され、実行前に全てのコマンドが表示されます。 - そして、0以外の終了コードで終了した場合、ビルドが失敗したと判断します。これを変更するには、#!/bin/...を追加します。 + デフォルトで、シェルは"-ex"オプションを付けて起動され、実行前に全てのコマンドが表示されます。 + そして、0以外の終了コードで終了した場合、ビルドが失敗したと判断します。これを変更するには、 + #!/bin/... + を追加します。 +

- ベストプラクティスとして、ここに長いシェルを記述しようとはしないで、代わりに、 - シェルスクリプトをSCMに追加して、Jenkinsからそのシェルスクリプトを起動することを検討してください。 - そうすれば、シェルスクリプトの変更も管理できます。 + ベストプラクティスとして、ここに長いシェルを記述しようとはしないで、代わりに、 + シェルスクリプトをSCMに追加して、Jenkinsからそのシェルスクリプトを起動することを検討してください。 + そうすれば、シェルスクリプトの変更も管理できます。 +

diff --git a/core/src/main/resources/hudson/tasks/Shell/help_pt_BR.html b/core/src/main/resources/hudson/tasks/Shell/help_pt_BR.html index 05ca71bdb1..c3d51911e4 100644 --- a/core/src/main/resources/hudson/tasks/Shell/help_pt_BR.html +++ b/core/src/main/resources/hudson/tasks/Shell/help_pt_BR.html @@ -1,14 +1,25 @@ -
- Executa um script de shell (o padrão é o sh, mas isto é configurável) para construir o projeto. - O script será executado com o workspace como diretório atual. Informe no conteúdo de seu - script, mas sem um cabeçalho como #!/bin/sh — que é adicionado pelo Jenkins, onde - o caminho do shell está configurado globalmente. +
+ + Executa um script de shell (o padrão é o + sh + , mas isto é configurável) para construir o projeto. O script + será executado com o workspace como diretório atual. Informe no + conteúdo de seu script, mas sem um cabeçalho como + #!/bin/sh + — que é adicionado pelo Jenkins, onde o caminho do shell está + configurado globalmente.

- O shell será invocado com a opção "-ex". Assim todos os comandos são impressos antes ser executados, - e a construção é considerada uma falha se qualquer dos comandos sair com um código diferente de zero. + O shell será invocado com a opção "-ex". Assim todos os + comandos são impressos antes ser executados, e a construção + é considerada uma falha se qualquer dos comandos sair com um + código diferente de zero. +

- Como uma boa prática, tente não colocar um script muito longo aqui. Ao invés, considere adicionar o script - no SCM e simplesmente chamá-lo do Jenkins, desta forma você pode rastrear as mudanças em seu script. + Como uma boa prática, tente não colocar um script muito longo + aqui. Ao invés, considere adicionar o script no SCM e simplesmente + chamá-lo do Jenkins, desta forma você pode rastrear as + mudanças em seu script. +

diff --git a/core/src/main/resources/hudson/tasks/Shell/help_ru.html b/core/src/main/resources/hudson/tasks/Shell/help_ru.html index c8784e8f59..2d14a5c6d2 100644 --- a/core/src/main/resources/hudson/tasks/Shell/help_ru.html +++ b/core/src/main/resources/hudson/tasks/Shell/help_ru.html @@ -1,16 +1,24 @@ -
- Выполняет запуск сценария оболочки (по-умолчанию, sh, но это настраивается) для - сборки проекта. Сценарий будет запущен в сборочной директории проекта. Вы можете вставить - в это поле содержимое вашего сценария, убрав заголовок #!/bin/sh, он будет добавлен - автоматически в зависимости от глобальных настроек. +
+ + Выполняет запуск сценария оболочки (по-умолчанию, + sh + , но это настраивается) для сборки проекта. Сценарий будет запущен в сборочной + директории проекта. Вы можете вставить в это поле содержимое вашего сценария, + убрав заголовок + #!/bin/sh + , он будет добавлен автоматически в зависимости от глобальных настроек.

- Оболочка будет вызвана с опцией "-ex". Таким образом все команды будут выведены в лог - перед непосредственным выполнением. Сборка будет считаться провалившейся, если какая-либо - из команд сценария завершится с ненулевым кодом возврата. + Оболочка будет вызвана с опцией "-ex". Таким образом все команды будут + выведены в лог перед непосредственным выполнением. Сборка будет считаться + провалившейся, если какая-либо из команд сценария завершится с ненулевым + кодом возврата. +

- Опыт показывает, что длинные последовательности команд не следует указывать здесь. - Вместо этого, сохраните сценарий в SCM и просто оставьте здесь вызов этого сценария. - Таким образом сценарий будет надежно сохранен и вы сможете отслеживать изменения в нем. + Опыт показывает, что длинные последовательности команд не следует указывать + здесь. Вместо этого, сохраните сценарий в SCM и просто оставьте здесь вызов + этого сценария. Таким образом сценарий будет надежно сохранен и вы сможете + отслеживать изменения в нем. +

diff --git a/core/src/main/resources/hudson/tasks/Shell/help_tr.html b/core/src/main/resources/hudson/tasks/Shell/help_tr.html index 52281e506c..5b024c7eab 100644 --- a/core/src/main/resources/hudson/tasks/Shell/help_tr.html +++ b/core/src/main/resources/hudson/tasks/Shell/help_tr.html @@ -1,11 +1,20 @@
- Projeyi yapılandırmak için shell scripti (varsayılan sh'dır, fakat değiştirilebilir) çalıştırır. - Script, bulunduğu dizin, çalışma alanı olacak şekilde çalışır. - Eğer shell scriptinizin başında #!/bin/sh satırı yoksa, sistem seviyesinde ayarlanan shell kullanılacaktır. - Fakat yinede, başlık satırını, başka programlama dilinde shell yazmak (#!/bin/perl gibi) veya shell'in - kullandıgı seçenekleri kontrol etmek için kullanabilirsiniz. - - Shell "-ex" seçeneği ile çağırılır. Böylece tüm komutlar çalışmadan önce ekrana yazılır ve komutlardan herhangi - birisi, 0 olmayan bir çıkış kodu ile biterse yapılandırma başarısız olarak ilan edilir. + Projeyi yapılandırmak için shell scripti (varsayılan + sh + 'dır, fakat değiştirilebilir) + çalıştırır. Script, bulunduğu dizin, + çalışma alanı olacak şekilde + çalışır. Eğer shell scriptinizin başında + #!/bin/sh + satırı yoksa, sistem seviyesinde ayarlanan shell + kullanılacaktır. Fakat yinede, başlık + satırını, başka programlama dilinde shell yazmak ( + #!/bin/perl + gibi) veya shell'in kullandıgı seçenekleri kontrol etmek + için kullanabilirsiniz. Shell "-ex" seçeneği ile + çağırılır. Böylece tüm komutlar + çalışmadan önce ekrana yazılır ve komutlardan + herhangi birisi, 0 olmayan bir çıkış kodu ile biterse + yapılandırma başarısız olarak ilan edilir.
diff --git a/core/src/main/resources/hudson/tasks/Shell/help_zh_TW.html b/core/src/main/resources/hudson/tasks/Shell/help_zh_TW.html index df0c8441b0..0c0a00aef2 100644 --- a/core/src/main/resources/hudson/tasks/Shell/help_zh_TW.html +++ b/core/src/main/resources/hudson/tasks/Shell/help_zh_TW.html @@ -1,15 +1,25 @@
- 執行 Shell Script (預設使用 sh，不過可以設定) 建置專案，該 Script 會在工作區目錄中執行。 - 輸入您 Shell Script 的內容，如果您的 Shell Script 沒有 #!/bin/sh 這類標頭，就會使用系統設定的 Shell 執行。 - 您也可以使用標頭指定撰寫別種語言的 Script (例如 #!/bin/perl) 或是控制 Shell 使用的選項。 + 執行 Shell Script (預設使用 + sh + ，不過可以設定) 建置專案，該 Script 會在工作區目錄中執行。 輸入您 Shell Script + 的內容，如果您的 Shell Script 沒有 + #!/bin/sh + 這類標頭，就會使用系統設定的 Shell 執行。 您也可以使用標頭指定撰寫別種語言的 + Script (例如 + #!/bin/perl + ) 或是控制 Shell 使用的選項。

- 預設會以 "-ex" 選項執行 Shell，所以每個指令都會先印出來再執行。 - 如果任何指令結束時傳出 0 以外的結束代碼，我們就認定建置失敗。 - 重覆一次，加入 #!/bin/... 改變這項行為模式。 + 預設會以 "-ex" 選項執行 Shell，所以每個指令都會先印出來再執行。 + 如果任何指令結束時傳出 0 以外的結束代碼，我們就認定建置失敗。 重覆一次，加入 + #!/bin/... + 改變這項行為模式。 +

- 前人血淚的教訓指出: 千萬不要把複雜的 Shell Script 放在這裡。 - 應該把 Shell Script 放到 SCM 裡，再由 Jenkins 單純的呼叫它 (透過 bash -ex myscript.sh 之類的)。 - 這樣您也可以追溯 Shell Script 的版本異動。 + 前人血淚的教訓指出: 千萬不要把複雜的 Shell Script 放在這裡。 應該把 Shell + Script 放到 SCM 裡，再由 Jenkins 單純的呼叫它 (透過 + bash -ex myscript.sh + 之類的)。 這樣您也可以追溯 Shell Script 的版本異動。 +

diff --git a/core/src/main/resources/hudson/tools/AbstractCommandInstaller/help-command.html b/core/src/main/resources/hudson/tools/AbstractCommandInstaller/help-command.html index d84dbd5713..3ee0ffb12e 100644 --- a/core/src/main/resources/hudson/tools/AbstractCommandInstaller/help-command.html +++ b/core/src/main/resources/hudson/tools/AbstractCommandInstaller/help-command.html @@ -1,4 +1,4 @@
- Command to run on the agent node to install the tool. - The command will always be run, so it should be a quick no-op if the tool is already installed. + Command to run on the agent node to install the tool. The command will always + be run, so it should be a quick no-op if the tool is already installed.
diff --git a/core/src/main/resources/hudson/tools/AbstractCommandInstaller/help-command_bg.html b/core/src/main/resources/hudson/tools/AbstractCommandInstaller/help-command_bg.html index 7550b70ec1..4d0bad4f33 100644 --- a/core/src/main/resources/hudson/tools/AbstractCommandInstaller/help-command_bg.html +++ b/core/src/main/resources/hudson/tools/AbstractCommandInstaller/help-command_bg.html @@ -1,5 +1,5 @@
- Команда, която да се стартира всеки път на машината за инсталиране на този - инструмент. Затова, когато инструментът е вече инсталиран, тя трябва да се - изпълнява доста бързо и да не прави нищо. + Команда, която да се стартира всеки път на машината за инсталиране на този + инструмент. Затова, когато инструментът е вече инсталиран, тя трябва да се + изпълнява доста бързо и да не прави нищо.
diff --git a/core/src/main/resources/hudson/tools/AbstractCommandInstaller/help-command_it.html b/core/src/main/resources/hudson/tools/AbstractCommandInstaller/help-command_it.html index 2d8dd60c05..783dc34c56 100644 --- a/core/src/main/resources/hudson/tools/AbstractCommandInstaller/help-command_it.html +++ b/core/src/main/resources/hudson/tools/AbstractCommandInstaller/help-command_it.html @@ -1,5 +1,5 @@
- Il comando da eseguire sul nodo agente per installare lo strumento. - Il comando sarà sempre eseguito, quindi dovrebbe terminare velocemente - senza eseguire alcuna operazione se lo strumento è già installato. + Il comando da eseguire sul nodo agente per installare lo strumento. Il comando + sarà sempre eseguito, quindi dovrebbe terminare velocemente senza eseguire + alcuna operazione se lo strumento è già installato.
diff --git a/core/src/main/resources/hudson/tools/AbstractCommandInstaller/help-command_ja.html b/core/src/main/resources/hudson/tools/AbstractCommandInstaller/help-command_ja.html index b40b707cc7..f236f1b29e 100644 --- a/core/src/main/resources/hudson/tools/AbstractCommandInstaller/help-command_ja.html +++ b/core/src/main/resources/hudson/tools/AbstractCommandInstaller/help-command_ja.html @@ -1,4 +1,4 @@
- エージェント上でツールをインストールするコマンドです。 - コマンドは常に実行されるので、ツールがインストール済みであれば、コマンドは何もしないようにすべきです。 + エージェント上でツールをインストールするコマンドです。 + コマンドは常に実行されるので、ツールがインストール済みであれば、コマンドは何もしないようにすべきです。
diff --git a/core/src/main/resources/hudson/tools/AbstractCommandInstaller/help-toolHome.html b/core/src/main/resources/hudson/tools/AbstractCommandInstaller/help-toolHome.html index ef7538e320..5f857f26a3 100644 --- a/core/src/main/resources/hudson/tools/AbstractCommandInstaller/help-toolHome.html +++ b/core/src/main/resources/hudson/tools/AbstractCommandInstaller/help-toolHome.html @@ -1,4 +1,4 @@
- Resulting home directory of the tool. - (May be a relative path if the command unpacked a tool in place.) + Resulting home directory of the tool. (May be a relative path if the command + unpacked a tool in place.)
diff --git a/core/src/main/resources/hudson/tools/AbstractCommandInstaller/help-toolHome_bg.html b/core/src/main/resources/hudson/tools/AbstractCommandInstaller/help-toolHome_bg.html index 6ce1b7d20f..95235257bf 100644 --- a/core/src/main/resources/hudson/tools/AbstractCommandInstaller/help-toolHome_bg.html +++ b/core/src/main/resources/hudson/tools/AbstractCommandInstaller/help-toolHome_bg.html @@ -1,3 +1 @@ -
- Домашната директория на програмата. (Пътят може да е относителен.) -
+
Домашната директория на програмата. (Пътят може да е относителен.)
diff --git a/core/src/main/resources/hudson/tools/AbstractCommandInstaller/help-toolHome_de.html b/core/src/main/resources/hudson/tools/AbstractCommandInstaller/help-toolHome_de.html index 92cbc67af3..c79bba6308 100644 --- a/core/src/main/resources/hudson/tools/AbstractCommandInstaller/help-toolHome_de.html +++ b/core/src/main/resources/hudson/tools/AbstractCommandInstaller/help-toolHome_de.html @@ -1,5 +1,5 @@
- Stammverzeichnis des Hilfsprogrammes nach der Installation. - Kann auch ein relativer Pfad sein, z.B. wenn das Kommando das Hilfsprogramm - in seinem Arbeitsverzeichnis entpackt. + Stammverzeichnis des Hilfsprogrammes nach der Installation. Kann auch ein + relativer Pfad sein, z.B. wenn das Kommando das Hilfsprogramm in seinem + Arbeitsverzeichnis entpackt.
diff --git a/core/src/main/resources/hudson/tools/AbstractCommandInstaller/help-toolHome_it.html b/core/src/main/resources/hudson/tools/AbstractCommandInstaller/help-toolHome_it.html index d514a205af..f65381c316 100644 --- a/core/src/main/resources/hudson/tools/AbstractCommandInstaller/help-toolHome_it.html +++ b/core/src/main/resources/hudson/tools/AbstractCommandInstaller/help-toolHome_it.html @@ -1,4 +1,4 @@
- La directory home risultante dello strumento. (Può essere un percorso - relativo se il comando ha estratto uno strumento sul posto.) + La directory home risultante dello strumento. (Può essere un percorso relativo + se il comando ha estratto uno strumento sul posto.)
diff --git a/core/src/main/resources/hudson/tools/AbstractCommandInstaller/help-toolHome_zh_TW.html b/core/src/main/resources/hudson/tools/AbstractCommandInstaller/help-toolHome_zh_TW.html index db4ccfb763..d448739777 100644 --- a/core/src/main/resources/hudson/tools/AbstractCommandInstaller/help-toolHome_zh_TW.html +++ b/core/src/main/resources/hudson/tools/AbstractCommandInstaller/help-toolHome_zh_TW.html @@ -1,4 +1 @@ -
- 產出工具主目錄。 - (如果指令就地解開工具，那也可以使用相對路徑。) -
+
產出工具主目錄。 (如果指令就地解開工具，那也可以使用相對路徑。)
diff --git a/core/src/main/resources/hudson/tools/AbstractCommandInstaller/help.html b/core/src/main/resources/hudson/tools/AbstractCommandInstaller/help.html index eafaf9d84f..0b13dc9a0c 100644 --- a/core/src/main/resources/hudson/tools/AbstractCommandInstaller/help.html +++ b/core/src/main/resources/hudson/tools/AbstractCommandInstaller/help.html @@ -1,21 +1,31 @@

- Runs a shell command of your choice to install the tool. Ubuntu example, - assuming the Jenkins user is in /etc/sudoers: + Runs a shell command of your choice to install the tool. Ubuntu example, + assuming the Jenkins user is in + /etc/sudoers + : 

sudo apt-get --yes install openjdk-6-jdk

- (In this case specify e.g. /usr/lib/jvm/java-6-openjdk-i386 as the home directory.) + (In this case specify e.g. + /usr/lib/jvm/java-6-openjdk-i386 + as the home directory.)

- As another example, to install an older version of Sun JDK 6 for (x86) Linux, - you can use the obsolete DLJ: + As another example, to install an older version of Sun JDK 6 for (x86) Linux, + you can use the obsolete + DLJ + :

-
bin=jdk-6u13-dlj-linux-i586.bin
+
+bin=jdk-6u13-dlj-linux-i586.bin
 if [ \! -f $bin ]
 then
     wget --no-verbose http://download.java.net/dlj/binaries/$bin
     sh $bin --unpack --accept-license
-fi

+fi

- (In this case specify jdk1.6.0_13 as the home directory.) + (In this case specify + jdk1.6.0_13 + as the home directory.)

diff --git a/core/src/main/resources/hudson/tools/AbstractCommandInstaller/help_bg.html b/core/src/main/resources/hudson/tools/AbstractCommandInstaller/help_bg.html index b9a0d59f2b..e78d54dc56 100644 --- a/core/src/main/resources/hudson/tools/AbstractCommandInstaller/help_bg.html +++ b/core/src/main/resources/hudson/tools/AbstractCommandInstaller/help_bg.html @@ -1,23 +1,32 @@

- Изпълнение на произволна последователност от команди на обвивката, които - позволяват да инсталирате програмата. Пример с Ubuntu — - предполагаме, че потребителят за Jenkins има права в /etc/sudoers: + Изпълнение на произволна последователност от команди на обвивката, които + позволяват да инсталирате програмата. Пример с Ubuntu — предполагаме, че + потребителят за Jenkins има права в + /etc/sudoers + : 

sudo apt-get --yes install openjdk-6-jdk

- (В този случай задайте примерно /usr/lib/jvm/java-6-openjdk-i386 като - домашна директория.) + (В този случай задайте примерно + /usr/lib/jvm/java-6-openjdk-i386 + като домашна директория.)

- Друг пример с инсталиране на стара версия на Sun JDK 6 за x86 Linux, - от вече несъществуващия сайт DLJ: + Друг пример с инсталиране на стара версия на Sun JDK 6 за x86 Linux, от вече + несъществуващия сайт + DLJ + :

-
bin=jdk-6u13-dlj-linux-i586.bin
+
+bin=jdk-6u13-dlj-linux-i586.bin
 if [ \! -f $bin ]
 then
     wget --no-verbose http://download.java.net/dlj/binaries/$bin
     sh $bin --unpack --accept-license
-fi

+fi

- (За домашна директория укажете jdk1.6.0_13 в този случай.) + (За домашна директория укажете + jdk1.6.0_13 + в този случай.)

diff --git a/core/src/main/resources/hudson/tools/AbstractCommandInstaller/help_de.html b/core/src/main/resources/hudson/tools/AbstractCommandInstaller/help_de.html index da52cbe61d..23b3fd5e0d 100644 --- a/core/src/main/resources/hudson/tools/AbstractCommandInstaller/help_de.html +++ b/core/src/main/resources/hudson/tools/AbstractCommandInstaller/help_de.html @@ -1,25 +1,31 @@

- Startet ein Shell-Kommando Ihrer Wahl, um das Hilfsprogramm zu installieren. - Unter Ubuntu könnte das beispielsweise so aussehen (unter der Annahme, dass - der Jenkins-Benutzer in /etc/sudoers gelistet ist): - + Startet ein Shell-Kommando Ihrer Wahl, um das Hilfsprogramm zu installieren. + Unter Ubuntu könnte das beispielsweise so aussehen (unter der Annahme, dass + der Jenkins-Benutzer in + /etc/sudoers + gelistet ist): 

sudo apt-get --yes install openjdk-6-jdk

- (In diesem Fall geben Sie /usr/lib/jvm/java-6-openjdk als Stammverzeichnis - des Hilfsprogramms an.) + (In diesem Fall geben Sie + /usr/lib/jvm/java-6-openjdk + als Stammverzeichnis des Hilfsprogramms an.)

- Weiteres Beispiel: Um Sun JDK 6 für (x86) Linux zu installieren, können Sie - DLJ einsetzen: + Weiteres Beispiel: Um Sun JDK 6 für (x86) Linux zu installieren, können Sie + DLJ + einsetzen:

-
bin=jdk-6u13-dlj-linux-i586.bin
+
+bin=jdk-6u13-dlj-linux-i586.bin
 if [ \! -f $bin ]
 then
     wget --no-verbose http://download.java.net/dlj/binaries/$bin
     sh $bin --unpack --accept-license
-fi

+fi

- (In diesem Fall geben Sie jdk1.6.0_13 als Stammverzeichnis - des Hilfsprogramms an.) + (In diesem Fall geben Sie + jdk1.6.0_13 + als Stammverzeichnis des Hilfsprogramms an.)

diff --git a/core/src/main/resources/hudson/tools/AbstractCommandInstaller/help_it.html b/core/src/main/resources/hudson/tools/AbstractCommandInstaller/help_it.html index c24caeb6f9..e6518ca401 100644 --- a/core/src/main/resources/hudson/tools/AbstractCommandInstaller/help_it.html +++ b/core/src/main/resources/hudson/tools/AbstractCommandInstaller/help_it.html @@ -1,24 +1,31 @@

- Esegue un comando shell a scelta per installare lo strumento. Esempio su - Ubuntu, assumendo che l'utente Jenkins sia elencato in - /etc/sudoers: + Esegue un comando shell a scelta per installare lo strumento. Esempio su + Ubuntu, assumendo che l'utente Jenkins sia elencato in + /etc/sudoers + : 

sudo apt-get --yes install openjdk-6-jdk

- (In questo caso si specifichi ad es. /usr/lib/jvm/java-6-openjdk-i386 - come directory home.) + (In questo caso si specifichi ad es. + /usr/lib/jvm/java-6-openjdk-i386 + come directory home.)

- Come altro esempio, per installare una versione meno recente del Sun JDK 6 - per Linux (x86), è possibile utilizzare lo strumento obsoleto - DLJ: + Come altro esempio, per installare una versione meno recente del Sun JDK 6 per + Linux (x86), è possibile utilizzare lo strumento obsoleto + DLJ + :

-
bin=jdk-6u13-dlj-linux-i586.bin
+
+bin=jdk-6u13-dlj-linux-i586.bin
 if [ \! -f $bin ]
 then
     wget --no-verbose http://download.java.net/dlj/binaries/$bin
     sh $bin --unpack --accept-license
-fi

+fi

- (In questo caso si specifichi jdk1.6.0_13 come directory home.) + (In questo caso si specifichi + jdk1.6.0_13 + come directory home.)

diff --git a/core/src/main/resources/hudson/tools/AbstractCommandInstaller/help_ja.html b/core/src/main/resources/hudson/tools/AbstractCommandInstaller/help_ja.html index 82fbb60d78..51d57aa631 100644 --- a/core/src/main/resources/hudson/tools/AbstractCommandInstaller/help_ja.html +++ b/core/src/main/resources/hudson/tools/AbstractCommandInstaller/help_ja.html @@ -1,21 +1,30 @@

- 選択したシェルを起動してツールをインストールします。 - 例えば、UbuntuにおいてJenkinsのユーザーは/etc/sudoersに登録されているとすれば、 + 選択したシェルを起動してツールをインストールします。 + 例えば、UbuntuにおいてJenkinsのユーザーは + /etc/sudoers + に登録されているとすれば、 

sudo apt-get --yes install openjdk-6-jdk

- (この場合、ツールホームとして/usr/lib/jvm/java-6-openjdkを設定します) + (この場合、ツールホームとして + /usr/lib/jvm/java-6-openjdk + を設定します)

- 別の例として、Sun JDK 6 for (x86) Linuxをインストールする場合、 - DLJを使用することができます。 + 別の例として、Sun JDK 6 for (x86) Linuxをインストールする場合、 + DLJ + を使用することができます。

-
bin=jdk-6u13-dlj-linux-i586.bin
+
+bin=jdk-6u13-dlj-linux-i586.bin
 if [ \! -f $bin ]
 then
     wget --no-verbose http://download.java.net/dlj/binaries/$bin
     sh $bin --unpack --accept-license
-fi

+fi

- (この場合、ツールホームとしてjdk1.6.0_13を設定します) + (この場合、ツールホームとして + jdk1.6.0_13 + を設定します)

diff --git a/core/src/main/resources/hudson/tools/AbstractCommandInstaller/help_zh_TW.html b/core/src/main/resources/hudson/tools/AbstractCommandInstaller/help_zh_TW.html index 4886bc78cc..a3a42ad4e1 100644 --- a/core/src/main/resources/hudson/tools/AbstractCommandInstaller/help_zh_TW.html +++ b/core/src/main/resources/hudson/tools/AbstractCommandInstaller/help_zh_TW.html @@ -1,21 +1,29 @@

- 依據您的選擇執行 Shell 指令安裝工具。 - 以 Ubuntu 為例，假設 Jenkins 使用者在 /etc/sudoers: + 依據您的選擇執行 Shell 指令安裝工具。 以 Ubuntu 為例，假設 Jenkins 使用者在 + /etc/sudoers + : 

sudo apt-get --yes install openjdk-6-jdk

- (這個例子中用 /usr/lib/jvm/java-6-openjdk-i386 當作主目錄。) + (這個例子中用 + /usr/lib/jvm/java-6-openjdk-i386 + 當作主目錄。)

- 再舉一個例子，要在 (x86) Linus 上安裝舊版的 Sun JDK 6，您可以使用已經過時的 - DLJ: + 再舉一個例子，要在 (x86) Linus 上安裝舊版的 Sun JDK 6，您可以使用已經過時的 + DLJ + :

-
bin=jdk-6u13-dlj-linux-i586.bin
+
+bin=jdk-6u13-dlj-linux-i586.bin
 if [ \! -f $bin ]
 then
     wget --no-verbose http://download.java.net/dlj/binaries/$bin
     sh $bin --unpack --accept-license
-fi

+fi

- (這個例子中指定 jdk1.6.0_13 為主目錄。) + (這個例子中指定 + jdk1.6.0_13 + 為主目錄。)

diff --git a/core/src/main/resources/hudson/tools/InstallSourceProperty/help.html b/core/src/main/resources/hudson/tools/InstallSourceProperty/help.html index dc27c6c3e9..0a70aa1c48 100644 --- a/core/src/main/resources/hudson/tools/InstallSourceProperty/help.html +++ b/core/src/main/resources/hudson/tools/InstallSourceProperty/help.html @@ -1,14 +1,16 @@
- Choose this option to let Jenkins install this tool for you on demand. + Choose this option to let Jenkins install this tool for you on demand. -

- If you check this option, you'll then be asked to configure a series - of "installer"s for this tool, where each installer defines how - Jenkins will try to install this tool. +

+ If you check this option, you'll then be asked to configure a series of + "installer"s for this tool, where each installer defines how Jenkins will + try to install this tool. +

-

- For a platform-independent tool (such as Ant), configuring multiple installers - for a single tool does not make much sense, but for a platform dependent tool, - multiple installer configurations allow you to run a different set up script - depending on the agent environment. +

+ For a platform-independent tool (such as Ant), configuring multiple + installers for a single tool does not make much sense, but for a platform + dependent tool, multiple installer configurations allow you to run a + different set up script depending on the agent environment. +

diff --git a/core/src/main/resources/hudson/tools/InstallSourceProperty/help_bg.html b/core/src/main/resources/hudson/tools/InstallSourceProperty/help_bg.html index 645ddc9255..5c47b56ec2 100644 --- a/core/src/main/resources/hudson/tools/InstallSourceProperty/help_bg.html +++ b/core/src/main/resources/hudson/tools/InstallSourceProperty/help_bg.html @@ -1,13 +1,15 @@
- Избирането на тази опция позволява на Jenkins да инсталира инструмента при - нужда. + Избирането на тази опция позволява на Jenkins да инсталира инструмента при + нужда. -

- След като я изберете ще бъдете подканени да настроите серия от „инсталатори“, - които позволяват на Jenkins да инсталира инструмента. +

+ След като я изберете ще бъдете подканени да настроите серия от + „инсталатори“, които позволяват на Jenkins да инсталира инструмента. +

-

- Ако инструментът е платформено независим, като Ant, няма голяма полза. В +

+ Ако инструментът е платформено независим, като Ant, няма голяма полза. В обратния случай това ви позволява да инсталирате платформено зависим инструмент по различен начин — с различни скриптове, на различните среди. +

diff --git a/core/src/main/resources/hudson/tools/InstallSourceProperty/help_it.html b/core/src/main/resources/hudson/tools/InstallSourceProperty/help_it.html index d0f79bd938..f640ae3a4f 100644 --- a/core/src/main/resources/hudson/tools/InstallSourceProperty/help_it.html +++ b/core/src/main/resources/hudson/tools/InstallSourceProperty/help_it.html @@ -1,17 +1,19 @@
- Selezionare quest'opzione per far sì che Jenkins installi questo strumento - per proprio conto su richiesta. + Selezionare quest'opzione per far sì che Jenkins installi questo strumento per + proprio conto su richiesta. -

- Se si seleziona quest'opzione, verrà richiesto di configurare una serie - di "programmi di installazione" per questo strumento, dove ogni programma - di installazione definisce le modalità con cui Jenkins proverà ad - installare questo strumento. +

+ Se si seleziona quest'opzione, verrà richiesto di configurare una serie di + "programmi di installazione" per questo strumento, dove ogni programma di + installazione definisce le modalità con cui Jenkins proverà ad installare + questo strumento. +

-

- Per uno strumento indipendente dalla piattaforma (come Ant), configurare - più programmi di installazione per un singolo strumento non ha molto - senso, ma per uno strumento dipendente dalla piattaforma la presenza di - più configurazioni di installazione consente di eseguire uno script di +

+ Per uno strumento indipendente dalla piattaforma (come Ant), configurare più + programmi di installazione per un singolo strumento non ha molto senso, ma + per uno strumento dipendente dalla piattaforma la presenza di più + configurazioni di installazione consente di eseguire uno script di installazione diverso a seconda dell'ambiente dell'agente. +

diff --git a/core/src/main/resources/hudson/tools/InstallSourceProperty/help_ja.html b/core/src/main/resources/hudson/tools/InstallSourceProperty/help_ja.html index a1d05fbb8e..b6a5f60fa2 100644 --- a/core/src/main/resources/hudson/tools/InstallSourceProperty/help_ja.html +++ b/core/src/main/resources/hudson/tools/InstallSourceProperty/help_ja.html @@ -1,12 +1,14 @@
- このオプションを選択すると、ツールを上記で設定した場所に必要に応じてインストールします。 + このオプションを選択すると、ツールを上記で設定した場所に必要に応じてインストールします。 -

+

このオプションを選択すると、このツールの一連の"インストーラ"を設定することができます。 各インストーラではどのようにツールのインストールを試みるかを定義します。 +

-

+

Antのようなプラットフォームに依存していないツールでは、複数のインストーラを設定してもあまり意味がありません。 しかし、プラットフォーム依存のツールでは、複数のインストーラを設定することで、 エージェントの環境に応じた異なるセットアップスクリプトを実行することができます。 -

\ No newline at end of file +

+
diff --git a/core/src/main/resources/hudson/tools/ZipExtractionInstaller/help-subdir.html b/core/src/main/resources/hudson/tools/ZipExtractionInstaller/help-subdir.html index 6806da2621..0bf157d8c9 100644 --- a/core/src/main/resources/hudson/tools/ZipExtractionInstaller/help-subdir.html +++ b/core/src/main/resources/hudson/tools/ZipExtractionInstaller/help-subdir.html @@ -1,3 +1,4 @@
- Optional subdirectory of the downloaded and unpacked archive to use as the tool's home directory. + Optional subdirectory of the downloaded and unpacked archive to use as the + tool's home directory.
diff --git a/core/src/main/resources/hudson/tools/ZipExtractionInstaller/help-subdir_bg.html b/core/src/main/resources/hudson/tools/ZipExtractionInstaller/help-subdir_bg.html index e95ffbedb8..2fb0ef7d70 100644 --- a/core/src/main/resources/hudson/tools/ZipExtractionInstaller/help-subdir_bg.html +++ b/core/src/main/resources/hudson/tools/ZipExtractionInstaller/help-subdir_bg.html @@ -1,4 +1,4 @@
- Незадължителна поддиректория от изтегления и разпакетиран архив, която да се ползва - като основна директория за програмата. + Незадължителна поддиректория от изтегления и разпакетиран архив, която да се + ползва като основна директория за програмата.
diff --git a/core/src/main/resources/hudson/tools/ZipExtractionInstaller/help-subdir_de.html b/core/src/main/resources/hudson/tools/ZipExtractionInstaller/help-subdir_de.html index 27960d4f64..fe10e0abc7 100644 --- a/core/src/main/resources/hudson/tools/ZipExtractionInstaller/help-subdir_de.html +++ b/core/src/main/resources/hudson/tools/ZipExtractionInstaller/help-subdir_de.html @@ -1,4 +1,4 @@
- Optionale Angabe eines Unterverzeichnisses des heruntergeladenen und entpackten Archives, das - als Stammverzeichnis des Hilfsprogrammes dient. + Optionale Angabe eines Unterverzeichnisses des heruntergeladenen und + entpackten Archives, das als Stammverzeichnis des Hilfsprogrammes dient.
diff --git a/core/src/main/resources/hudson/tools/ZipExtractionInstaller/help-subdir_it.html b/core/src/main/resources/hudson/tools/ZipExtractionInstaller/help-subdir_it.html index a9989f9e4e..13f1c38e4f 100644 --- a/core/src/main/resources/hudson/tools/ZipExtractionInstaller/help-subdir_it.html +++ b/core/src/main/resources/hudson/tools/ZipExtractionInstaller/help-subdir_it.html @@ -1,4 +1,4 @@
- Sottodirectory (facoltativa) dell'archivio scaricato ed estratto da - utilizzare come directory home dello strumento. + Sottodirectory (facoltativa) dell'archivio scaricato ed estratto da utilizzare + come directory home dello strumento.
diff --git a/core/src/main/resources/hudson/tools/ZipExtractionInstaller/help-subdir_ja.html b/core/src/main/resources/hudson/tools/ZipExtractionInstaller/help-subdir_ja.html index 78cbdc1740..cc73766708 100644 --- a/core/src/main/resources/hudson/tools/ZipExtractionInstaller/help-subdir_ja.html +++ b/core/src/main/resources/hudson/tools/ZipExtractionInstaller/help-subdir_ja.html @@ -1,3 +1,3 @@
- ツールのホームディレクトリとして使用する、アーカイブをダウンロードして展開するサブディレクトリです(オプション)。 + ツールのホームディレクトリとして使用する、アーカイブをダウンロードして展開するサブディレクトリです(オプション)。
diff --git a/core/src/main/resources/hudson/tools/ZipExtractionInstaller/help-subdir_zh_TW.html b/core/src/main/resources/hudson/tools/ZipExtractionInstaller/help-subdir_zh_TW.html index 95afd335cc..76792724c2 100644 --- a/core/src/main/resources/hudson/tools/ZipExtractionInstaller/help-subdir_zh_TW.html +++ b/core/src/main/resources/hudson/tools/ZipExtractionInstaller/help-subdir_zh_TW.html @@ -1,3 +1 @@ -
- 壓縮檔下載解開後，要當作工具主目錄的子目錄。 -
+
壓縮檔下載解開後，要當作工具主目錄的子目錄。
diff --git a/core/src/main/resources/hudson/tools/ZipExtractionInstaller/help-url.html b/core/src/main/resources/hudson/tools/ZipExtractionInstaller/help-url.html index f22666f219..0170578477 100644 --- a/core/src/main/resources/hudson/tools/ZipExtractionInstaller/help-url.html +++ b/core/src/main/resources/hudson/tools/ZipExtractionInstaller/help-url.html @@ -1,7 +1,6 @@
- URL from which to download the tool in binary form. - Should be either a ZIP or a GZip-compressed TAR file. - The timestamp on the server will be compared to the local version (if any) - so you can publish updates easily. - The URL must be accessible from the Jenkins controller but need not be accessible from agents. + URL from which to download the tool in binary form. Should be either a ZIP or + a GZip-compressed TAR file. The timestamp on the server will be compared to + the local version (if any) so you can publish updates easily. The URL must be + accessible from the Jenkins controller but need not be accessible from agents.
diff --git a/core/src/main/resources/hudson/tools/ZipExtractionInstaller/help-url_bg.html b/core/src/main/resources/hudson/tools/ZipExtractionInstaller/help-url_bg.html index 5bf99bd535..c2a5129281 100644 --- a/core/src/main/resources/hudson/tools/ZipExtractionInstaller/help-url_bg.html +++ b/core/src/main/resources/hudson/tools/ZipExtractionInstaller/help-url_bg.html @@ -1,7 +1,7 @@
- Адрес, от който да се изтегли програмата в компилиран вид. Трябва да е - архив във формат zip или tar.gz. Ако вече е изтеглена предишна версия, - се сравняват времената им, за да може по-лесно да се публикуват обновления. - Адресът трябва да е достижим от командния компютър на Jenkins, няма нужда да - се вижда от подчинените машини. + Адрес, от който да се изтегли програмата в компилиран вид. Трябва да е архив + във формат zip или tar.gz. Ако вече е изтеглена предишна версия, се сравняват + времената им, за да може по-лесно да се публикуват обновления. Адресът трябва + да е достижим от командния компютър на Jenkins, няма нужда да се вижда от + подчинените машини.
diff --git a/core/src/main/resources/hudson/tools/ZipExtractionInstaller/help-url_it.html b/core/src/main/resources/hudson/tools/ZipExtractionInstaller/help-url_it.html index b10f12808c..1230e00cd4 100644 --- a/core/src/main/resources/hudson/tools/ZipExtractionInstaller/help-url_it.html +++ b/core/src/main/resources/hudson/tools/ZipExtractionInstaller/help-url_it.html @@ -1,8 +1,7 @@
- URL da cui scaricare lo strumento in forma binaria. Dovrebbe essere un - file TAR compresso con ZIP o con gzip. Il timestamp sul server sarà - confrontato con quello della versione locale (se presente) in modo da - consentire una facile pubblicazione degli aggiornamenti. L'URL dev'essere - accessibile dal master Jenkins, ma non è necessario che sia accessibile - dagli agenti. + URL da cui scaricare lo strumento in forma binaria. Dovrebbe essere un file + TAR compresso con ZIP o con gzip. Il timestamp sul server sarà confrontato con + quello della versione locale (se presente) in modo da consentire una facile + pubblicazione degli aggiornamenti. L'URL dev'essere accessibile dal master + Jenkins, ma non è necessario che sia accessibile dagli agenti.
diff --git a/core/src/main/resources/hudson/tools/ZipExtractionInstaller/help-url_ja.html b/core/src/main/resources/hudson/tools/ZipExtractionInstaller/help-url_ja.html index f4fb14f826..18054feb30 100644 --- a/core/src/main/resources/hudson/tools/ZipExtractionInstaller/help-url_ja.html +++ b/core/src/main/resources/hudson/tools/ZipExtractionInstaller/help-url_ja.html @@ -1,7 +1,7 @@
- バイナリ形式でツールをダウンロードするURLです。 - ZIPかGzipで圧縮したTARファイルのいずれかの形式である必要があります。 - サーバーにあるアーカイブのタイムスタンプと、(もしあれば)ローカルのファイルのタイムスタンプを比較するので、 - 容易にアップデートを配布できます。 - URLはマスターからアクセス可能でなければなりませんが、エージェントからはアクセス可能である必要はありません。 + バイナリ形式でツールをダウンロードするURLです。 + ZIPかGzipで圧縮したTARファイルのいずれかの形式である必要があります。 + サーバーにあるアーカイブのタイムスタンプと、(もしあれば)ローカルのファイルのタイムスタンプを比較するので、 + 容易にアップデートを配布できます。 + URLはマスターからアクセス可能でなければなりませんが、エージェントからはアクセス可能である必要はありません。
diff --git a/core/src/main/resources/hudson/tools/ZipExtractionInstaller/help.html b/core/src/main/resources/hudson/tools/ZipExtractionInstaller/help.html index d36d72d8c1..890e4ab46f 100644 --- a/core/src/main/resources/hudson/tools/ZipExtractionInstaller/help.html +++ b/core/src/main/resources/hudson/tools/ZipExtractionInstaller/help.html @@ -1,5 +1,10 @@
- Downloads a tool archive and installs it within Jenkins's working directory. - Example: https://downloads.apache.org/ant/binaries/apache-ant-1.10.12-bin.zip - and specify a subdir of apache-ant-1.10.12. + Downloads a tool archive and installs it within Jenkins's working directory. + Example: + + https://downloads.apache.org/ant/binaries/apache-ant-1.10.12-bin.zip + + and specify a subdir of + apache-ant-1.10.12 + .
diff --git a/core/src/main/resources/hudson/tools/ZipExtractionInstaller/help_bg.html b/core/src/main/resources/hudson/tools/ZipExtractionInstaller/help_bg.html index 5885e35c97..9fa8cd4493 100644 --- a/core/src/main/resources/hudson/tools/ZipExtractionInstaller/help_bg.html +++ b/core/src/main/resources/hudson/tools/ZipExtractionInstaller/help_bg.html @@ -1,5 +1,11 @@ --
- Изтегляне на архив с програма и инсталирането ѝ в работната директория на Jenkins. - Примерно: https://downloads.apache.org/ant/binaries/apache-ant-1.10.12-bin.zip - и укажете поддиректория на apache-ant-1.10.12. +- +
+ Изтегляне на архив с програма и инсталирането ѝ в работната директория на + Jenkins. Примерно: + + https://downloads.apache.org/ant/binaries/apache-ant-1.10.12-bin.zip + + и укажете поддиректория на + apache-ant-1.10.12 + .
diff --git a/core/src/main/resources/hudson/tools/ZipExtractionInstaller/help_de.html b/core/src/main/resources/hudson/tools/ZipExtractionInstaller/help_de.html index 3b0c19163a..e89d537fcb 100644 --- a/core/src/main/resources/hudson/tools/ZipExtractionInstaller/help_de.html +++ b/core/src/main/resources/hudson/tools/ZipExtractionInstaller/help_de.html @@ -1,6 +1,10 @@
- Lädt ein Hilfsprogramm als gepacktes Archiv herunter und installiert es innerhalb - des Jenkins-Arbeitsverzeichnisses. - Beispiel: https://downloads.apache.org/ant/binaries/apache-ant-1.10.12-bin.zip - mit der Angabe eines Unterverzeichnisses von apache-ant-1.10.12. + Lädt ein Hilfsprogramm als gepacktes Archiv herunter und installiert es + innerhalb des Jenkins-Arbeitsverzeichnisses. Beispiel: + + https://downloads.apache.org/ant/binaries/apache-ant-1.10.12-bin.zip + + mit der Angabe eines Unterverzeichnisses von + apache-ant-1.10.12 + .
diff --git a/core/src/main/resources/hudson/tools/ZipExtractionInstaller/help_it.html b/core/src/main/resources/hudson/tools/ZipExtractionInstaller/help_it.html index f55d1370d4..f6590b3c0e 100644 --- a/core/src/main/resources/hudson/tools/ZipExtractionInstaller/help_it.html +++ b/core/src/main/resources/hudson/tools/ZipExtractionInstaller/help_it.html @@ -1,6 +1,10 @@
- Scarica un archivio contenente uno strumento e lo installa all'interno - della directory di lavoro di Jenkins. Ad esempio: - https://downloads.apache.org/ant/binaries/apache-ant-1.10.12-bin.zip - e si specifichi una sottodirectory di apache-ant-1.10.12. + Scarica un archivio contenente uno strumento e lo installa all'interno della + directory di lavoro di Jenkins. Ad esempio: + + https://downloads.apache.org/ant/binaries/apache-ant-1.10.12-bin.zip + + e si specifichi una sottodirectory di + apache-ant-1.10.12 + .
diff --git a/core/src/main/resources/hudson/tools/ZipExtractionInstaller/help_ja.html b/core/src/main/resources/hudson/tools/ZipExtractionInstaller/help_ja.html index 9b80732de1..b89910e3cd 100644 --- a/core/src/main/resources/hudson/tools/ZipExtractionInstaller/help_ja.html +++ b/core/src/main/resources/hudson/tools/ZipExtractionInstaller/help_ja.html @@ -1,5 +1,10 @@
- ツールのアーカイブをダウンロードして、Jenkinsのワークディレクトリにインストールします。 - 例えば: https://downloads.apache.org/ant/binaries/apache-ant-1.10.12-bin.zip - そして、サブディレクトリにapache-ant-1.10.12を指定します。 + ツールのアーカイブをダウンロードして、Jenkinsのワークディレクトリにインストールします。 + 例えば: + + https://downloads.apache.org/ant/binaries/apache-ant-1.10.12-bin.zip + + そして、サブディレクトリに + apache-ant-1.10.12 + を指定します。
diff --git a/core/src/main/resources/hudson/tools/ZipExtractionInstaller/help_zh_TW.html b/core/src/main/resources/hudson/tools/ZipExtractionInstaller/help_zh_TW.html index 95af127631..346e40d950 100644 --- a/core/src/main/resources/hudson/tools/ZipExtractionInstaller/help_zh_TW.html +++ b/core/src/main/resources/hudson/tools/ZipExtractionInstaller/help_zh_TW.html @@ -1,5 +1,9 @@
- 下載工具壓縮檔，並安裝到 Jenkins 工作目錄中。 - 例如: https://downloads.apache.org/ant/binaries/apache-ant-1.10.12-bin.zip - 並指定子目錄 apache-ant-1.10.12。 + 下載工具壓縮檔，並安裝到 Jenkins 工作目錄中。 例如: + + https://downloads.apache.org/ant/binaries/apache-ant-1.10.12-bin.zip + + 並指定子目錄 + apache-ant-1.10.12 + 。
diff --git a/core/src/main/resources/hudson/triggers/SCMTrigger/help-ignorePostCommitHooks.html b/core/src/main/resources/hudson/triggers/SCMTrigger/help-ignorePostCommitHooks.html index 306716caa5..5c7e36e04f 100644 --- a/core/src/main/resources/hudson/triggers/SCMTrigger/help-ignorePostCommitHooks.html +++ b/core/src/main/resources/hudson/triggers/SCMTrigger/help-ignorePostCommitHooks.html @@ -1,8 +1,13 @@
Ignore changes notified by SCM post-commit hooks. -

- This can be useful if you want to prevent some long-running jobs (e.g. reports) starting because of every commit, but still want to - run them periodic if SCM changes have occurred. -

- Note that this option needs to be supported by the SCM plugin, too! The subversion-plugin supports this since version 1.44. -

\ No newline at end of file +

+ This can be useful if you want to prevent some long-running jobs (e.g. + reports) starting because of every commit, but still want to run them + periodic if SCM changes have occurred. +

+ +

+ Note that this option needs to be supported by the SCM plugin, too! The + subversion-plugin supports this since version 1.44. +

+
diff --git a/core/src/main/resources/hudson/triggers/SCMTrigger/help-ignorePostCommitHooks_bg.html b/core/src/main/resources/hudson/triggers/SCMTrigger/help-ignorePostCommitHooks_bg.html index 7d88134b2d..e743588393 100644 --- a/core/src/main/resources/hudson/triggers/SCMTrigger/help-ignorePostCommitHooks_bg.html +++ b/core/src/main/resources/hudson/triggers/SCMTrigger/help-ignorePostCommitHooks_bg.html @@ -1,13 +1,16 @@
Игнориране на известията за промяна от страна на системата за контрол на версиите. -

- Това е полезно да предотвратите постоянното стартиране на продължителни - задачи, като извлечения, обработка на данни и др. при всяка отделна - промяна в системата за контрол на версиите, но все пак искате да ги стартирате - от време на време, ако промени има. -

- За да сработи тази опция, тя трябва да се поддържа и от приставката за системата - за контрол на версиите. В случая на Subversion, приставката трябва да е поне - версия 1.44. +

+ Това е полезно да предотвратите постоянното стартиране на продължителни + задачи, като извлечения, обработка на данни и др. при всяка отделна промяна + в системата за контрол на версиите, но все пак искате да ги стартирате от + време на време, ако промени има. +

+ +

+ За да сработи тази опция, тя трябва да се поддържа и от приставката за + системата за контрол на версиите. В случая на Subversion, приставката трябва + да е поне версия 1.44. +

diff --git a/core/src/main/resources/hudson/triggers/SCMTrigger/help-ignorePostCommitHooks_it.html b/core/src/main/resources/hudson/triggers/SCMTrigger/help-ignorePostCommitHooks_it.html index 04e7dce3aa..acdbe39f28 100644 --- a/core/src/main/resources/hudson/triggers/SCMTrigger/help-ignorePostCommitHooks_it.html +++ b/core/src/main/resources/hudson/triggers/SCMTrigger/help-ignorePostCommitHooks_it.html @@ -1,13 +1,16 @@
Ignora le modifiche notificate dagli hook post-commit del sistema di gestione del codice sorgente. -

- Ciò può essere utile se si desidera impedire che alcuni processi dalla durata - lunga (ad es. report) partano dopo ogni commit, ma se si desidera comunque - eseguirli periodicamente se si sono verificate modifiche nel sistema di - gestione del codice sorgente. -

- Si noti che quest'opzione deve essere supportata anche dal componente - aggiuntivo del sistema di gestione del codice sorgente! Il componente - aggiuntivo Subversion la supporta dalla versione 1.44. +

+ Ciò può essere utile se si desidera impedire che alcuni processi dalla + durata lunga (ad es. report) partano dopo ogni commit, ma se si desidera + comunque eseguirli periodicamente se si sono verificate modifiche nel + sistema di gestione del codice sorgente. +

+ +

+ Si noti che quest'opzione deve essere supportata anche dal componente + aggiuntivo del sistema di gestione del codice sorgente! Il componente + aggiuntivo Subversion la supporta dalla versione 1.44. +

diff --git a/core/src/main/resources/hudson/triggers/SCMTrigger/help-ignorePostCommitHooks_zh_TW.html b/core/src/main/resources/hudson/triggers/SCMTrigger/help-ignorePostCommitHooks_zh_TW.html index 6e72571fd6..24275b21d9 100644 --- a/core/src/main/resources/hudson/triggers/SCMTrigger/help-ignorePostCommitHooks_zh_TW.html +++ b/core/src/main/resources/hudson/triggers/SCMTrigger/help-ignorePostCommitHooks_zh_TW.html @@ -1,7 +1,12 @@
忽略由 SCM Post-Commit Hook 通報的變更。 -

- 如果您想避免一些要跑很久的作業 (例如報表) 每次 Commit 就開始建置，又想要在 SCM 有變動時定期執行，這個選項就是為您設計的。 -

- 注意，這個功能要 SCM 外掛程式也支援才有作用! subversion-plugin 從 1.44 版後開始支援。 -

\ No newline at end of file +

+ 如果您想避免一些要跑很久的作業 (例如報表) 每次 Commit 就開始建置，又想要在 + SCM 有變動時定期執行，這個選項就是為您設計的。 +

+ +

+ 注意，這個功能要 SCM 外掛程式也支援才有作用! subversion-plugin 從 1.44 + 版後開始支援。 +

+
diff --git a/core/src/main/resources/hudson/triggers/SCMTrigger/help-pollingThreadCount.html b/core/src/main/resources/hudson/triggers/SCMTrigger/help-pollingThreadCount.html index 5d45a865d2..d32cd1e7cc 100644 --- a/core/src/main/resources/hudson/triggers/SCMTrigger/help-pollingThreadCount.html +++ b/core/src/main/resources/hudson/triggers/SCMTrigger/help-pollingThreadCount.html @@ -1,5 +1,9 @@
- This option configures the maximum number of concurrent threads that are used by Jenkins to poll for SCM changes. + This option configures the maximum number of concurrent threads that are used + by Jenkins to poll for SCM changes.

- Depending on your network connection, SCM service, and Jenkins configuration, you may need to increase or decrease the number of threads to achieve optimal results. -

\ No newline at end of file + Depending on your network connection, SCM service, and Jenkins + configuration, you may need to increase or decrease the number of threads to + achieve optimal results. +

+
diff --git a/core/src/main/resources/hudson/triggers/SCMTrigger/help-pollingThreadCount_it.html b/core/src/main/resources/hudson/triggers/SCMTrigger/help-pollingThreadCount_it.html index 54462abea0..f1ec2ffd27 100644 --- a/core/src/main/resources/hudson/triggers/SCMTrigger/help-pollingThreadCount_it.html +++ b/core/src/main/resources/hudson/triggers/SCMTrigger/help-pollingThreadCount_it.html @@ -1,10 +1,11 @@
Quest'opzione configura il numero massimo di thread concorrenti che sono - utilizzati da Jenkins per eseguire il polling delle modifiche nel - sistema di gestione del codice sorgente. + utilizzati da Jenkins per eseguire il polling delle modifiche nel sistema di + gestione del codice sorgente.

- A seconda della connessione di rete, del servizio del sistema di gestione del - codice sorgente e della configurazione di Jenkins potrebbe essere necessario - aumentare o diminuire il numero di thread per ottenere dei risultati - ottimali. + A seconda della connessione di rete, del servizio del sistema di gestione + del codice sorgente e della configurazione di Jenkins potrebbe essere + necessario aumentare o diminuire il numero di thread per ottenere dei + risultati ottimali. +

diff --git a/core/src/main/resources/hudson/triggers/SCMTrigger/help.html b/core/src/main/resources/hudson/triggers/SCMTrigger/help.html index 0b85e09d28..04a96c4d19 100644 --- a/core/src/main/resources/hudson/triggers/SCMTrigger/help.html +++ b/core/src/main/resources/hudson/triggers/SCMTrigger/help.html @@ -2,8 +2,12 @@ Configure Jenkins to poll changes in SCM.

- 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 + 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 + +

diff --git a/core/src/main/resources/hudson/triggers/SCMTrigger/help_bg.html b/core/src/main/resources/hudson/triggers/SCMTrigger/help_bg.html index 3714874fe5..5d25c09d0a 100644 --- a/core/src/main/resources/hudson/triggers/SCMTrigger/help_bg.html +++ b/core/src/main/resources/hudson/triggers/SCMTrigger/help_bg.html @@ -2,9 +2,13 @@ Настройване на Jenkins за пита системата за контрол на версиите за промени.

- При ползване на CVS това е ужасно скъпа операция, защото кара Jenkins да - обходи цялото работно пространство и да го синхронизира със сървъра. - По-добре е с помощта на автоматично действие от страна на CVS да известявате - Jenkins за промени. За повече информация погледнете - документацията. + При ползване на CVS това е ужасно скъпа операция, защото кара Jenkins да + обходи цялото работно пространство и да го синхронизира със сървъра. + По-добре е с помощта на автоматично действие от страна на CVS да известявате + Jenkins за промени. За повече информация погледнете + + документацията + + . +

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 898019c59e..17fb301c3e 100644 --- a/core/src/main/resources/hudson/triggers/SCMTrigger/help_de.html +++ b/core/src/main/resources/hudson/triggers/SCMTrigger/help_de.html @@ -3,10 +3,13 @@ (Source Code Management system, kurz: SCM).

- Bedenken Sie, dass dies für das Versionsverwaltungssystem CVS eine äußerst - ressourcenintensive Operation darstellt, da Jenkins bei jeder Abfrage den - kompletten Arbeitsbereich überprüfen und mit dem CVS-Server abgleichen muss. - Ziehen Sie daher alternativ einen "Push"-Auslöser in Betracht, wie er in - diesem Dokument beschrieben - wird. + Bedenken Sie, dass dies für das Versionsverwaltungssystem CVS eine äußerst + ressourcenintensive Operation darstellt, da Jenkins bei jeder Abfrage den + kompletten Arbeitsbereich überprüfen und mit dem CVS-Server abgleichen muss. + Ziehen Sie daher alternativ einen "Push"-Auslöser in Betracht, wie er in + + 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 c5770ad49f..2f1f75c7d5 100644 --- a/core/src/main/resources/hudson/triggers/SCMTrigger/help_fr.html +++ b/core/src/main/resources/hudson/triggers/SCMTrigger/help_fr.html @@ -3,10 +3,11 @@ version.

- Notez que cette opération est consommatrice de ressources pour le SCM, - 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. + Notez que cette opération est consommatrice de ressources pour le SCM, 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 + . +

diff --git a/core/src/main/resources/hudson/triggers/SCMTrigger/help_it.html b/core/src/main/resources/hudson/triggers/SCMTrigger/help_it.html index 0abb0be582..9e747d7c67 100644 --- a/core/src/main/resources/hudson/triggers/SCMTrigger/help_it.html +++ b/core/src/main/resources/hudson/triggers/SCMTrigger/help_it.html @@ -3,10 +3,14 @@ gestione del codice sorgente.

- Si noti che quest'operazione sarà molto onerosa per CVS, in quanto ogni - operazione di polling richiede a Jenkins di scansionare tutto lo spazio di - lavoro e di verificarlo con il server. Si prenda in considerazione - l'impostazione di un trigger "push" per evitare quest'onere, come descritto - in questo - documento. + Si noti che quest'operazione sarà molto onerosa per CVS, in quanto ogni + operazione di polling richiede a Jenkins di scansionare tutto lo spazio di + lavoro e di verificarlo con il server. Si prenda in considerazione + l'impostazione di un trigger "push" per evitare quest'onere, come descritto + in + + questo documento + + . +

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 9df6bb6a4e..0b1fd40457 100644 --- a/core/src/main/resources/hudson/triggers/SCMTrigger/help_ja.html +++ b/core/src/main/resources/hudson/triggers/SCMTrigger/help_ja.html @@ -2,9 +2,12 @@ SCMの変更を監視します。

- ポーリング毎に、Jenkinsはワークスペースをスキャンしてサーバーと検証する必要があるので、 - CVSにとって負荷の高い操作ということに注意してください。 - このオーバーヘッドを避けるために、 - このドキュメントにあるように、 - "push"トリガーの設定を検討してください。 + ポーリング毎に、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 8ea0273426..8a5370993a 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 @@ -2,8 +2,13 @@ Configura o Jenkins para consultar periodicamente mudanças no SCM.

- 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 + 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 + +

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 39a804fece..c37a1a649d 100644 --- a/core/src/main/resources/hudson/triggers/SCMTrigger/help_ru.html +++ b/core/src/main/resources/hudson/triggers/SCMTrigger/help_ru.html @@ -2,9 +2,14 @@ Насторить Jenkins на опрос изменений в вашей системе контроля версий (SCM).

- Обратите внимание, что эта операция вызывает достаточно высокую нагрузку - на SCM, так как каждый опрос представляет собой сканирование сборочной директории и - сверка содержимого с данными на сервере. Лучшим вариантом будет настройка - вашей SCM на инициацию сборки при внесении в неё изменений, как описано - в этом документе. + Обратите внимание, что эта операция вызывает достаточно высокую нагрузку на + 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 6c28b7cf9d..e6cfdaa444 100644 --- a/core/src/main/resources/hudson/triggers/SCMTrigger/help_tr.html +++ b/core/src/main/resources/hudson/triggers/SCMTrigger/help_tr.html @@ -1,9 +1,15 @@
- Jenkins'in konfigürasyonunu SCM'deki değişiklikleri kontrol edecek şekilde ayarla. + Jenkins'in konfigürasyonunu SCM'deki değişiklikleri kontrol + edecek şekilde ayarla.

- 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. + 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. +

diff --git a/core/src/main/resources/hudson/triggers/SCMTrigger/help_zh_TW.html b/core/src/main/resources/hudson/triggers/SCMTrigger/help_zh_TW.html index 6c65125f2c..3313843c20 100644 --- a/core/src/main/resources/hudson/triggers/SCMTrigger/help_zh_TW.html +++ b/core/src/main/resources/hudson/triggers/SCMTrigger/help_zh_TW.html @@ -2,7 +2,9 @@ 設定讓 Jenkins 持續檢查 (輪詢) SCM 異動。

- 請注意，這對 CVS 而言代價很高，每次輪詢 Jenkins 都要掃描整個工作區，並與伺服器比對。 - 建議參考這份文件設定 - "push" 觸發程序，避免額外負擔。 + 請注意，這對 CVS 而言代價很高，每次輪詢 Jenkins + 都要掃描整個工作區，並與伺服器比對。 建議參考 + 這份文件 + 設定 "push" 觸發程序，避免額外負擔。 +

diff --git a/core/src/main/resources/hudson/triggers/TimerTrigger/help-spec_bg.html b/core/src/main/resources/hudson/triggers/TimerTrigger/help-spec_bg.html index 7cea08ce5a..4d2db1ccf6 100644 --- a/core/src/main/resources/hudson/triggers/TimerTrigger/help-spec_bg.html +++ b/core/src/main/resources/hudson/triggers/TimerTrigger/help-spec_bg.html @@ -1,6 +1,6 @@
- Полето следва синтаксиса на cron (с малки различия). - Всеки ред се състои от 5 полета с разделител интервал или табулация: + Полето следва синтаксиса на cron (с малки различия). Всеки ред се състои от 5 + полета с разделител интервал или табулация: 
МИНУТА ЧАС ДЕН_ОТ_МЕСЕЦА МЕСЕЦ ДЕН_ОТ_СЕДМИЦАТА
@@ -29,49 +29,99 @@ Изброени от най-висок към най-нисък приоритет, това са:

    -
  • * всички възможни стойности
    • -
  • M-N интервал от стойности
    • -
  • M-N/X или */X стъпки от интервали от X единици в указания интервал или от всички възможни стойности
    • -
  • A,B,...,Z изброяване на множество от точни стойности
    • +
  • + * + всички възможни стойности +
    • +
  • + M-N + интервал от стойности +
    • +
  • + M-N/X + или + */X + стъпки от интервали от X единици в указания интервал или от всички + възможни стойности +
    • +
  • + A,B,...,Z + изброяване на множество от точни стойности +

- Със знака H включвате системата за равномерно натоварване, - използвайте го възможно най-често („H“ идва от „hash“). - Например: 0 0 * * * за много ежедневни задачи ще доведе до голямо - натоварване в полунощ. - Противоположно на това H H * * * също ще изпълнява задачите ежедневно, - но няма да стартира всички по едно и също време, което води до намаляване на - необходимите ресурси. -

- Знакът H може да се използва с интервал. - Например H H(0-7) * * * означава някой момент между 00:00 AM и 7:59. - С H може да ползвате е постъпкови изрази с или без интервали. -

- Може да мислите за H като случайна стойност от съответния интервал. - Истината е, че не е случайна стойност, а е базирана на хеша от името на задачата. - Така тази стойност е стабилна за всеки проект. + Със знака + H + включвате системата за равномерно натоварване, използвайте го възможно + най-често („H“ идва от „hash“). Например: + 0 0 * * * + за много ежедневни задачи ще доведе до голямо натоварване в полунощ. + Противоположно на това + H H * * * + също ще изпълнява задачите ежедневно, но няма да стартира всички по едно и + също време, което води до намаляване на необходимите ресурси.

- Кратки интервали като */3 или H/3 работят по-особено - в края на месеците поради различната дължина на месеците. - Например: */3 ще се стартира на 1-ви, 4-ти,… 31-ни и веднага отново на 1-ви следващия месец. - Хешовете за ден от месеца се избират от интервала 1-28. Възможно и H/3 да породи дупка - от 3 до 6 дни в края на месеца. - (Подобен ефект има и при по-дълги интервали, но там е относително по-малко забележим.) + Знакът + H + може да се използва с интервал. Например + H H(0-7) * * * + означава някой момент между 00:00 AM и 7:59. С + H + може да ползвате е постъпкови изрази с или без интервали.

- Празните редове, както и тези, които започват с # се считат за коментари. -

- Допълнително може да ползвате следните синоними: @yearly (ежегодно), @annually - (ежегодно), @monthly (ежемесечно), @weekly (ежеседмично), @daily - (ежедневно), @midnight (всяка нощ) и @hourly (всеки час). - Те използват системата за балансиране на натоварването. - Например, @hourly е същото като H * * * * и означава някой момент в часа. - @midnight означава някой момент между 00:00 AM и 2:59. -

- Примери: + Може да мислите за + H + като случайна стойност от съответния интервал. Истината е, че не е случайна + стойност, а е базирана на хеша от името на задачата. Така тази стойност е + стабилна за всеки проект.

-
+  

+    Кратки интервали като
+    */3
+    или
+    H/3
+    работят по-особено в края на месеците поради различната дължина на месеците.
+    Например:
+    */3
+    ще се стартира на 1-ви, 4-ти,… 31-ни и веднага отново на 1-ви следващия
+    месец. Хешовете за ден от месеца се избират от интервала 1-28. Възможно и
+    H/3
+    да породи дупка от 3 до 6 дни в края на месеца. (Подобен ефект има и при
+    по-дълги интервали, но там е относително по-малко забележим.)
+  

+  

+    Празните редове, както и тези, които започват с
+    #
+    се считат за коментари.
+  

+  

+    Допълнително може да ползвате следните синоними:
+    @yearly
+    (ежегодно),
+    @annually
+    (ежегодно),
+    @monthly
+    (ежемесечно),
+    @weekly
+    (ежеседмично),
+    @daily
+    (ежедневно),
+    @midnight
+    (всяка нощ) и
+    @hourly
+    (всеки час). Те използват системата за балансиране на натоварването.
+    Например,
+    @hourly
+    е същото като
+    H * * * *
+    и означава някой момент в часа.
+    @midnight
+    означава някой момент между 00:00 AM и 2:59.
+  

+  
Примери:

+  
 # на всеки 15 минути (примерно: и 7, и 22, и 37,  и 52)
 H/15 * * * *
 # на всеки 10 минути в първата половина на всеки час (3 пъти, примерно: и 4, и 14, и 24)
@@ -82,5 +132,6 @@ H(0-29)/10 * * * *
 H H(9-16)/2 * * 1-5
 # веднъж на ден - на всяко 1-во и 15-то число от всеки месец без декември
 H H 1,15 1-11 *
-

+
diff --git a/core/src/main/resources/hudson/triggers/TimerTrigger/help-spec_de.html b/core/src/main/resources/hudson/triggers/TimerTrigger/help-spec_de.html index ece0b30904..a1de2ec2b5 100644 --- a/core/src/main/resources/hudson/triggers/TimerTrigger/help-spec_de.html +++ b/core/src/main/resources/hudson/triggers/TimerTrigger/help-spec_de.html @@ -1,6 +1,6 @@
- Dieses Feld verwendet die Cron-Syntax (mit kleinen Unterschieden). - Jede Zeile besteht dabei aus 5 Feldern, getrennt durch Tabulator oder Leerzeichen: + Dieses Feld verwendet die Cron-Syntax (mit kleinen Unterschieden). Jede Zeile + besteht dabei aus 5 Feldern, getrennt durch Tabulator oder Leerzeichen: 
MINUTE STUNDE TAG MONAT WOCHENTAG
@@ -29,45 +29,74 @@ werden. In absteigender Priorität sind dies:

    -
  • * entspricht allen gültigen Werten
    • -
  • M-N gibt einen Bereich an, z.B. "1-5"
    • -
  • M-N/X oder */X unterteilt den angegebenen Bereich - bzw. den gültigen Bereich in X-er Schritte, z.B. "*/15" im Feld MINUTE für - "0,15,30,45" und "1-6/2" für "1,3,5"
    • -
  • A,B,...,Z entspricht direkt den angegebenen Werten, z.B. - "0,30" oder "1,3,5"
    • +
  • + * + entspricht allen gültigen Werten +
    • +
  • + M-N + gibt einen Bereich an, z.B. "1-5" +
    • +
  • + M-N/X + oder + */X + unterteilt den angegebenen Bereich bzw. den gültigen Bereich in X-er + Schritte, z.B. "*/15" im Feld MINUTE für "0,15,30,45" und "1-6/2" für + "1,3,5" +
    • +
  • + A,B,...,Z + entspricht direkt den angegebenen Werten, z.B. "0,30" oder "1,3,5" +

- Damit periodisch gestartete Jobs eine gleichmäßig verteilte Systemlast erzeugen, - sollte das Symbol H (für "Hash") so oft wie möglich verwendet werden. - So wird z.B. die Einstellung 0 0 * * * für ein Dutzend Jobs - zu einer großen Lastspitze um Mitternacht führen. - Im Gegensatz dazu werden die Jobs bei Verwendung von H H * * * - immer noch alle täglich ausgeführt, starten jedoch zeitversetzt, so dass beschränkte - Resourcen besser ausgenutzt werden. -

- H kann auch mit Bereichsangaben kombiniert werden. - Zum Beispiel bedeutet H H(0-7) * * * einen Zeitpunkt zwischen 0:00 und 7:59. - Sie können H auch mit Schrittangaben verwenden, mit oder ohne Bereichsangaben. -

- Sie können sich das H-Symbol als einen zufälligen Wert in einem Bereich - vorstellen. Tatsächlich wird statt eines echten Zufallswertes ein Hash über den Jobnamen - verwendet, so dass der Wert für ein gegebenes Projekt konstant bleibt. + Damit periodisch gestartete Jobs eine gleichmäßig verteilte Systemlast + erzeugen, sollte das Symbol + H + (für "Hash") so oft wie möglich verwendet werden. So wird z.B. die + Einstellung + 0 0 * * * + für ein Dutzend Jobs zu einer großen Lastspitze um Mitternacht führen. Im + Gegensatz dazu werden die Jobs bei Verwendung von + H H * * * + immer noch alle täglich ausgeführt, starten jedoch zeitversetzt, so dass + beschränkte Resourcen besser ausgenutzt werden. +

+

+ H + kann auch mit Bereichsangaben kombiniert werden. Zum Beispiel bedeutet + H H(0-7) * * * + einen Zeitpunkt zwischen 0:00 und 7:59. Sie können + H + auch mit Schrittangaben verwenden, mit oder ohne Bereichsangaben. +

+

+ Sie können sich das + H + -Symbol als einen zufälligen Wert in einem Bereich vorstellen. Tatsächlich + wird statt eines echten Zufallswertes ein Hash über den Jobnamen verwendet, + so dass der Wert für ein gegebenes Projekt konstant bleibt. +

+

Leere Zeilen und Zeilen, die mit '#' beginnen, werden als Kommentarzeilen ignoriert. -

- Zusätzlich werden '@yearly', '@annually', '@monthly', '@weekly', '@daily', '@midnight' - und '@hourly' unterstützt. - Diese verwenden das Hash-System zur automatischen Lastverteilung. - Zum Beispiel bedeutet @hourly das selbe wie H * * * * - und steht für eine beliebige Zeit in der Stunde. - @midnight bedeutet tatsächlich einen Zeitpunkt zwischen 00:00 und 2:59. -

- Beispiele:

-
+  

+    Zusätzlich werden '@yearly', '@annually', '@monthly', '@weekly', '@daily',
+    '@midnight' und '@hourly' unterstützt. Diese verwenden das Hash-System zur
+    automatischen Lastverteilung. Zum Beispiel bedeutet
+    @hourly
+    das selbe wie
+    H * * * *
+    und steht für eine beliebige Zeit in der Stunde.
+    @midnight
+    bedeutet tatsächlich einen Zeitpunkt zwischen 00:00 und 2:59.
+  

+  
Beispiele:

+  
 # Alle fünfzehn Minuten (z.B. um :07, :22, :37, :52)
 H/15 * * * *
 # Alle zehn Minuten in der ersten Hälfte jeder Stunde (drei mal, z.B. um :04, :14, :24)
@@ -76,5 +105,6 @@ H(0-29)/10 * * * *
 H 9-16/2 * * 1-5
 # Einmal täglich am 1. und 15. Tag jeden Monats außer Dezember
 H H 1,15 1-11 *
-

-
\ No newline at end of file
+
+ diff --git a/core/src/main/resources/hudson/triggers/TimerTrigger/help-spec_fr.html b/core/src/main/resources/hudson/triggers/TimerTrigger/help-spec_fr.html index ca6b1760c1..380efbd487 100644 --- a/core/src/main/resources/hudson/triggers/TimerTrigger/help-spec_fr.html +++ b/core/src/main/resources/hudson/triggers/TimerTrigger/help-spec_fr.html @@ -1,6 +1,6 @@ 
- Ce champ suit la syntaxe de cron (avec des différences mineures). - Chaque ligne consiste en 5 champs séparés par des TABs ou des espaces : + Ce champ suit la syntaxe de cron (avec des différences mineures). Chaque ligne + consiste en 5 champs séparés par des TABs ou des espaces : 
MINUTES HEURES JOURMOIS MOIS JOURSEMAINE
@@ -21,44 +21,46 @@ - +
JOURSEMAINELe jour de la semaine (0-7) où 0 et 7 représentent le dimanche - Le jour de la semaine (0-7) où 0 et 7 représentent le dimanche

- Pour spécifier des valeurs multiples pour un champ, utilisez les - opérateurs suivants. - Par ordre de précédence : + Pour spécifier des valeurs multiples pour un champ, utilisez les opérateurs + suivants. Par ordre de précédence :

  • '*' représente l'ensemble des valeurs possibles.
  • 'M-N' représente une liste bornée, telle que "1-5"
    • -
  • 'M-N/X' ou '*/X' permettent de spécifier des sauts de valeur X - dans la liste. - Par exemple, "*/15" dans le champ MINUTES est équivalent à - "0,15,30,45" et "1-6/2" à "1,3,5"
    • -
  • 'A,B,...,Z' permet de spécifier des valeurs multiples, comme - "0,30" ou "1,3,5"
    • +
  • + 'M-N/X' ou '*/X' permettent de spécifier des sauts de valeur X dans la + liste. Par exemple, "*/15" dans le champ MINUTES est équivalent à + "0,15,30,45" et "1-6/2" à "1,3,5" +
    • +
  • + 'A,B,...,Z' permet de spécifier des valeurs multiples, comme "0,30" ou + "1,3,5" +

- Les lignes vides et les lignes qui commencent par '#' seront - considérées comme des commentaires et ignorées. + Les lignes vides et les lignes qui commencent par '#' seront considérées + comme des commentaires et ignorées.

- Par ailleurs, les mots-clefs '@yearly', '@annually', '@monthly', - '@weekly', '@daily', '@midnight' et '@hourly' sont supportés. + Par ailleurs, les mots-clefs '@yearly', '@annually', '@monthly', '@weekly', + '@daily', '@midnight' et '@hourly' sont supportés.

Exemples -
+        
 # toutes les minutes
 * * * * *
 # toutes les 5 minutes après l'heure
 5 * * * *
-

+
-
\ No newline at end of file + diff --git a/core/src/main/resources/hudson/triggers/TimerTrigger/help-spec_ja.html b/core/src/main/resources/hudson/triggers/TimerTrigger/help-spec_ja.html index b0d84168fa..a5d9091d6e 100644 --- a/core/src/main/resources/hudson/triggers/TimerTrigger/help-spec_ja.html +++ b/core/src/main/resources/hudson/triggers/TimerTrigger/help-spec_ja.html @@ -30,28 +30,37 @@
  • '*'は、全ての有効な値を指定します。
  • 'M-N'は、"1-5"のような範囲を指定します。
    • -
  • 'M-N/X'や'*/X'は、例えば、分の項目で"0,15,30,45"の代わりに"*/15"を、 - "1,3,5"の代わりに"1-6/2"のように、その範囲内でXだけスキップします。
    • +
  • + 'M-N/X'や'*/X'は、例えば、分の項目で"0,15,30,45"の代わりに"*/15"を、 + "1,3,5"の代わりに"1-6/2"のように、その範囲内でXだけスキップします。 +
  • 'A,B,...,Z'は、"0,30"や"1,3,5"のように複数の値を指定します。

定期的にスケジュールされたタスクがシステムに負荷をかける場合に対応できるように、 - H (ハッシュを表す)を使用するべきです。 - 例えば、たくさんの日次ジョブに0 0 * * *を使用すると、真夜中にシステムへの負荷が急上昇します。 - それに対して、H H * * *を使用すると、1日1回各ジョブが実行されますが、 + H + (ハッシュを表す)を使用するべきです。 例えば、たくさんの日次ジョブに + 0 0 * * * + を使用すると、真夜中にシステムへの負荷が急上昇します。 それに対して、 + H H * * * + を使用すると、1日1回各ジョブが実行されますが、 すべてのジョブが同時に実行するのではなく、限られたリソースをより有効に使用します。 -

- H は範囲とともに使用することもできます。 - 例えば、H H(0-7) * * * はAM 00:00からAM 7:59までの間のいつかを表します。 +

+

+ H + は範囲とともに使用することもできます。 例えば、 + H H(0-7) * * * + はAM 00:00からAM 7:59までの間のいつかを表します。 また、インターバルとあわせて使用することもできます。 -

- H は、ある範囲におけるランダムな値と考えることもできますが、 +

+

+ H + は、ある範囲におけるランダムな値と考えることもできますが、 実際には、ランダム関数ではなく、ジョブ名のハッシュであり、特定のプロジェクトに対して一定の値を表すものです。

+

空行や'#'で始まる行はコメントとして無視されます。

- 空行や'#'で始まる行はコメントとして無視されます。 -

さらに、'@yearly'(年に1回)、'@annually'(年に1回)、'@monthly'(月に1回)、'@weekly'(週に1回)、'@daily'(日に1回)、 '@midnight'(日に1回)、および'@hourly'(時間に1回)をサポートします。

@@ -59,7 +68,7 @@ 例 -
+        
 # 15分ごと (おそらく、7分、22分、37分、52分）
 H/15 * * * *
 # 0-30分の間で10分ごと (おそらく、4分、14分、24分の3回）
@@ -68,8 +77,9 @@ H(0-29)/10 * * * *
 H 9-16/2 * * 1-5
 # 12月を除く毎月1日と15日に1回
 H H 1,15 1-11 *
-

+
- \ No newline at end of file + diff --git a/core/src/main/resources/hudson/triggers/TimerTrigger/help-spec_pt_BR.html b/core/src/main/resources/hudson/triggers/TimerTrigger/help-spec_pt_BR.html index 2de153b2bc..8988041c16 100644 --- a/core/src/main/resources/hudson/triggers/TimerTrigger/help-spec_pt_BR.html +++ b/core/src/main/resources/hudson/triggers/TimerTrigger/help-spec_pt_BR.html @@ -1,6 +1,7 @@
Este campo segue a sintaxe do cron (com poucas diferenças). - Especificamente, cada linha consite de 5 campos separados por tabulação (TAB) ou espeaço em branco: + Especificamente, cada linha consite de 5 campos separados por + tabulação (TAB) ou espeaço em branco: 
MINUTO HORA DM MES DS
@@ -25,32 +26,41 @@

- Para especificar múltiplos valores para um campo, os seguintes operadores estão - disponíveis. Em ordem de precedência, + Para especificar múltiplos valores para um campo, os seguintes + operadores estão disponíveis. Em ordem de precedência,

  • '*' pode ser usado para especificar todos os valores válidos.
  • 'M-N' pode ser usado para especificar um intervalo, tal como "1-5"
    • -
  • 'M-N/X' ou '*/X' pode ser usado para especificar saltos do valor de X entre o intervalo, - tal como "*/15" no campo MINUTO para "0,15,30,45" e "1-6/2" para "1,3,5"
    • -
  • 'A,B,...,Z' pode ser usado para especificar múltiplos valores, tal como "0,30" ou "1,3,5"
    • +
  • + 'M-N/X' ou '*/X' pode ser usado para especificar saltos do valor de X + entre o intervalo, tal como "*/15" no campo MINUTO para "0,15,30,45" e + "1-6/2" para "1,3,5" +
    • +
  • + 'A,B,...,Z' pode ser usado para especificar múltiplos valores, tal + como "0,30" ou "1,3,5" +

- Linhas vazias e linha que começam com '#' serão ignoradas como comentários. -

- Em adição, as constantes '@yearly', '@annually', '@monthly', '@weekly', '@daily', '@midnight', - e '@hourly' são suportadas. + Linhas vazias e linha que começam com '#' serão ignoradas como + comentários. +

+

+ Em adição, as constantes '@yearly', '@annually', '@monthly', + '@weekly', '@daily', '@midnight', e '@hourly' são suportadas.

Exemplos -
+        
 # todo minuto
 * * * * *
 # no minuto 5 de cada hora (ou seja '2:05,3:05,...') 
 5 * * * *
-

+
diff --git a/core/src/main/resources/hudson/triggers/TimerTrigger/help-spec_ru.html b/core/src/main/resources/hudson/triggers/TimerTrigger/help-spec_ru.html index 1670b5354a..6442832d56 100644 --- a/core/src/main/resources/hudson/triggers/TimerTrigger/help-spec_ru.html +++ b/core/src/main/resources/hudson/triggers/TimerTrigger/help-spec_ru.html @@ -1,6 +1,7 @@ 
Это поле следует принципам синтаксиса cron (с небольшими различиями). - Конкретнее, каждая строка состоит из 5 полей, разделенных пробелами или табуляцией: + Конкретнее, каждая строка состоит из 5 полей, разделенных пробелами или + табуляцией: 
МИНУТА ЧАС ДЕНЬ МЕСЯЦ ДЕНЬ_НЕДЕЛИ
@@ -25,33 +26,40 @@

- Для указания множественнх значений в одном поле, возможно использование следующих - операторов: + Для указания множественнх значений в одном поле, возможно использование + следующих операторов:

  • '*' для подстановки всех доступных значений.
  • 'M-N' для использования интервала, например "1-5"
    • -
  • 'M-N/X' или '*/X' используется для пропуска X значений из интервала, - например, "*/15" в поле МИНУТА означает "0,15,30,45", а "1-6/2" - "1,3,5"
    • -
  • 'A,B,...,Z' для указания списка значений, например, "0,30" или "1,3,5"
    • +
  • + 'M-N/X' или '*/X' используется для пропуска X значений из интервала, + например, "*/15" в поле МИНУТА означает "0,15,30,45", а "1-6/2" - "1,3,5" +
    • +
  • + 'A,B,...,Z' для указания списка значений, например, "0,30" или "1,3,5" +

- Пустые строки и строки начинающиеся с символа '#' считаются комментариями и пропускаются. -

- Вдобавок, поддерживаются макросы '@yearly', '@annually', '@monthly', '@weekly', - '@daily', '@midnight' и '@hourly'. + Пустые строки и строки начинающиеся с символа '#' считаются комментариями и + пропускаются. +

+

+ Вдобавок, поддерживаются макросы '@yearly', '@annually', '@monthly', + '@weekly', '@daily', '@midnight' и '@hourly'.

Примеры -
+        
 # каждую минуту
 * * * * *
 # каждый час в 5 минут (00:05, 01:05, 02:05 и т.д.)
 5 * * * *
-

+
-
\ No newline at end of file +
diff --git a/core/src/main/resources/hudson/triggers/TimerTrigger/help-spec_tr.html b/core/src/main/resources/hudson/triggers/TimerTrigger/help-spec_tr.html index 185a7402d0..7aa4b6642b 100644 --- a/core/src/main/resources/hudson/triggers/TimerTrigger/help-spec_tr.html +++ b/core/src/main/resources/hudson/triggers/TimerTrigger/help-spec_tr.html @@ -1,6 +1,7 @@
- Bu alan çok küçük farklar dışında cron sentaksını kullanır. - Her satır, TAB veya boşluk karakteri ile ayrılmış 5 kısımdan oluşur. + Bu alan çok küçük farklar dışında cron + sentaksını kullanır. Her satır, TAB veya boşluk + karakteri ile ayrılmış 5 kısımdan oluşur. 
MINUTE HOUR DOM MONTH DOW
@@ -25,33 +26,51 @@

- Bir kısıma birden fazla değer girmek için aşağıdakiler kullanılabilir. - Öncelik sırasına göre, + Bir kısıma birden fazla değer girmek için + aşağıdakiler kullanılabilir. Öncelik + sırasına göre,

    -
  • '*' tüm geçerli değerleri belirlemek için kullanılır.
    • -
  • 'M-N', "1-5" gibi aralıkları belirlemek için kullanılır
    • -
  • 'M-N/X' veya '*/X' verilen 'M-N' aralığında 'X' değeri kadar farklarla belirleme imkanı sağlar, - mesela MINUTE kısmına yazıalcak "*/15" değeri "0,15,30,45" anlamına gelir veya "1-6/2" ise "1,3,5" anlamındadır.
    • -
  • 'A,B,...,Z' birden fazla değerin belirlenmesine yardımcı olur, mesela "0,30" veya "1,3,5" gibi.
    • +
  • + '*' tüm geçerli değerleri belirlemek için + kullanılır. +
    • +
  • + 'M-N', "1-5" gibi aralıkları belirlemek için + kullanılır +
    • +
  • + 'M-N/X' veya '*/X' verilen 'M-N' aralığında 'X' değeri + kadar farklarla belirleme imkanı sağlar, mesela MINUTE + kısmına yazıalcak "*/15" değeri "0,15,30,45" + anlamına gelir veya "1-6/2" ise "1,3,5" anlamındadır. +
    • +
  • + 'A,B,...,Z' birden fazla değerin belirlenmesine yardımcı + olur, mesela "0,30" veya "1,3,5" gibi. +

- Boş satırlar ve '#' ile başlayan satırlar yorum olarak algılanır, ve es geçilir. -

- Bunların yanında, '@yearly', '@annually', '@monthly', '@weekly', '@daily', '@midnight', - ve '@hourly' değişkenleri de desteklenmektedir. + Boş satırlar ve '#' ile başlayan satırlar yorum olarak + algılanır, ve es geçilir. +

+

+ Bunların yanında, '@yearly', '@annually', '@monthly', '@weekly', + '@daily', '@midnight', ve '@hourly' değişkenleri de + desteklenmektedir.

Örnekler -
+        
 # her dakika için
 * * * * *
 # her saati 5 geçe
 5 * * * *
-

+
-
\ No newline at end of file + diff --git a/core/src/main/resources/hudson/triggers/TimerTrigger/help-spec_zh_TW.html b/core/src/main/resources/hudson/triggers/TimerTrigger/help-spec_zh_TW.html index c4b0601253..d082b406a9 100644 --- a/core/src/main/resources/hudson/triggers/TimerTrigger/help-spec_zh_TW.html +++ b/core/src/main/resources/hudson/triggers/TimerTrigger/help-spec_zh_TW.html @@ -24,42 +24,54 @@ 星期幾 (0-7)，0 跟 7 都代表星期日。 -

- 要在欄位裡指定多個值時，可以使用下列運算符號 (按照優先權排序): -

+

要在欄位裡指定多個值時，可以使用下列運算符號 (按照優先權排序):

  • '*' 代表所有可以用的數值。
  • 'M-N' 代表範圍區間，例如 "1-5"
    • -
  • 'M-N/X' 或 '*/X' 代表區間內每隔 X 的數值，例如在「分」欄位裡的 "*/15" 表示 "0,15,30,45"，而 "1-6/2" 則是 "1,3,5"
    • +
  • + 'M-N/X' 或 '*/X' 代表區間內每隔 X 的數值，例如在「分」欄位裡的 "*/15" 表示 + "0,15,30,45"，而 "1-6/2" 則是 "1,3,5" +
  • 'A,B,...,Z' 可以指定多個值，例如 "0,30" 或 "1,3,5"

- 為了在定期排程的時的系統負擔平均一點，可以使用 'H' 符號。 - 例如，大家常會把每天要執行的作業設成 "0 0 * * *"，可是這樣子會讓事情都擠到每天午夜時分去。 - 相較之下，設定成 "H H * * *" 也一樣每天都會跑一次，但是 Jenkins 會分散到不同時段執行。 -

- 'H' 符號也能指定範圍。就像 "H H(0-7) * * *" 代表子夜開始到早上 7:59 前的某個時間。 -

- 您可以把 'H' 符號想像成是在某個區間裡隨機挑出來的數值。 - 但事實上它只是作業名稱的 Hash 值，而不是隨機函式，所以對固定一個專案而言，這個數值是固定的。 + 為了在定期排程的時的系統負擔平均一點，可以使用 ' + H + ' 符號。 例如，大家常會把每天要執行的作業設成 " + 0 0 * * * + "，可是這樣子會讓事情都擠到每天午夜時分去。 相較之下，設定成 " + H H * * * + " 也一樣每天都會跑一次，但是 Jenkins 會分散到不同時段執行。 +

+

+ 'H' 符號也能指定範圍。就像 " + H H(0-7) * * * + " 代表子夜開始到早上 7:59 前的某個時間。 +

+

+ 您可以把 ' + H + ' 符號想像成是在某個區間裡隨機挑出來的數值。 但事實上它只是作業名稱的 Hash + 值，而不是隨機函式，所以對固定一個專案而言，這個數值是固定的。

+

空行，或是以 '#' 開頭的那幾行都會被當作註解忽略掉。

- 空行，或是以 '#' 開頭的那幾行都會被當作註解忽略掉。 -

- 另外也支援 "@yearly" (每年), "@annually" (每季), "@monthly" (每月), "@weekly" (每週), - "@daily" (每天), "@midnight" (半夜) 及 "@hourly" (每小時)。 + 另外也支援 "@yearly" (每年), "@annually" (每季), "@monthly" (每月), + "@weekly" (每週), "@daily" (每天), "@midnight" (半夜) 及 "@hourly" + (每小時)。

範例 -
+        
 # 每 1 分鐘
 * * * * *
 # 整點後第 5 分鐘
 5 * * * *
-

+
- \ No newline at end of file + diff --git a/core/src/main/resources/hudson/triggers/TimerTrigger/help.html b/core/src/main/resources/hudson/triggers/TimerTrigger/help.html index 03fa53f40e..d1a067e9a2 100644 --- a/core/src/main/resources/hudson/triggers/TimerTrigger/help.html +++ b/core/src/main/resources/hudson/triggers/TimerTrigger/help.html @@ -1,19 +1,24 @@
- Provides a cron-like feature - to periodically execute this project. + Provides a + cron + -like feature to periodically execute this project.

- 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 - the idea of regularly scheduled builds like nightly/weekly that they use - 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. + 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 + the idea of regularly scheduled builds like nightly/weekly that they use + 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 + + . +

- So, before using this feature, stop and ask yourself if this is really what you want. - + 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_bg.html b/core/src/main/resources/hudson/triggers/TimerTrigger/help_bg.html index f28073ae3f..246927ecef 100644 --- a/core/src/main/resources/hudson/triggers/TimerTrigger/help_bg.html +++ b/core/src/main/resources/hudson/triggers/TimerTrigger/help_bg.html @@ -1,22 +1,26 @@
- Възможност за периодично изпълнение на този проект на база време, - подобно но програмата cron. + Възможност за периодично изпълнение на този проект на база време, подобно но + програмата + cron + .

- Това дава възможност да ползвате Jenkins като заместител на cron. - Това рядко е правилен начин за непрекъснато изграждане на проекти. - - Често хората, когато започват да внедряват непрекъснато изграждане, си - мислят, че проектите просто трябва да се изграждат на определен период — - примерно всеки ден или всяка седмица, което обяснява най-честата - употреба на тази възможност. Идеята обаче е друга — при непрекъснатото - изграждане трябва да се реагира с появата на всяка промяна, за да се - получи възможно най-скоро обратна връзка. Това се постига с - автоматични - известия от системата за контрол на версиите към Jenkins. + Това дава възможност да ползвате Jenkins като заместител на cron. Това + рядко е правилен начин за непрекъснато изграждане на проекти + . Често хората, когато започват да внедряват непрекъснато изграждане, си + мислят, че проектите просто трябва да се изграждат на определен период — + примерно всеки ден или всяка седмица, което обяснява най-честата употреба на + тази възможност. Идеята обаче е друга — при непрекъснатото изграждане трябва + да се реагира с появата на всяка промяна, за да се получи възможно най-скоро + обратна връзка. Това се постига с + + автоматични известия от системата за контрол на версиите към Jenkins + + . +

- Преди да започнете да ползвате тази възможност (cron) се спрете и - хубаво си помислете дали искате точно това. - + Преди да започнете да ползвате тази възможност (cron) се спрете и хубаво си + помислете дали искате точно това. +

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 c4ba272158..bd62e09e94 100644 --- a/core/src/main/resources/hudson/triggers/TimerTrigger/help_de.html +++ b/core/src/main/resources/hudson/triggers/TimerTrigger/help_de.html @@ -1,21 +1,26 @@
Erlaubt eine Ausführung des Projekts in regelmäßigen Zeitintervallen, ähnlich - dem Cron-Befehl. + dem + Cron + -Befehl.

- Dieses Merkmal ist hauptsächlich als Cron-Ersatz gedacht und ist - nicht ideal für Software-Projekte mit kontinuierlicher Integration. - - Viele Entwickler, die auf kontinuierliche Integration umstellen, sind so - sehr an die Idee von zeitgesteuerten Builds gewöhnt (z.B. nächtliche oder - wöchentliche Builds), dass sie dieses Merkmal verwenden. Der Witz der - 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 - notification) in Jenkins einrichten. + Dieses Merkmal ist hauptsächlich als Cron-Ersatz gedacht und ist + nicht ideal für Software-Projekte mit kontinuierlicher Integration + . Viele Entwickler, die auf kontinuierliche Integration umstellen, sind so + sehr an die Idee von zeitgesteuerten Builds gewöhnt (z.B. nächtliche oder + wöchentliche Builds), dass sie dieses Merkmal verwenden. Der Witz der + 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 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. + Bevor Sie also dieses Merkmal nutzen, halten Sie kurz inne und fragen Sie + sich, ob dies wirklich das ist, was Sie eigentlich wollen. +

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 539776a666..0bdd8c092b 100644 --- a/core/src/main/resources/hudson/triggers/TimerTrigger/help_fr.html +++ b/core/src/main/resources/hudson/triggers/TimerTrigger/help_fr.html @@ -4,20 +4,26 @@ afin d'exécuter le projet périodiquement.

- Cette fonction est prévue principalement pour utiliser Jenkins en - remplacement de cron. Elle n'est pas faite pour la construction - continue de projets logiciel. - - Quand quelqu'un débute avec l'intégration continue, il est souvent - tellement habitué à l'idée d'un lancement de build toutes les nuits ou - toutes les semaines, qu'il préfère utiliser cette fonctionnalité. - Néanmoins, l'intérêt de l'intégration continue est de lancer un build à - 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.. + Cette fonction est prévue principalement pour utiliser Jenkins en + remplacement de cron. + + Elle n'est pas faite pour la construction continue de projets logiciel + + . Quand quelqu'un débute avec l'intégration continue, il est souvent + tellement habitué à l'idée d'un lancement de build toutes les nuits ou + toutes les semaines, qu'il préfère utiliser cette fonctionnalité. Néanmoins, + l'intérêt de l'intégration continue est de lancer un build à 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. + + . +

- Donc, avant d'utiliser cette fonctionnalité, demandez-vous si c'est bien - ce que vous voulez faire. + Donc, avant d'utiliser cette fonctionnalité, demandez-vous si c'est bien ce + que vous voulez faire. +

diff --git a/core/src/main/resources/hudson/triggers/TimerTrigger/help_it.html b/core/src/main/resources/hudson/triggers/TimerTrigger/help_it.html index 9e9b46f402..2e9b879236 100644 --- a/core/src/main/resources/hudson/triggers/TimerTrigger/help_it.html +++ b/core/src/main/resources/hudson/triggers/TimerTrigger/help_it.html @@ -1,24 +1,27 @@
- Fornisce una funzionalità simile a cron + Fornisce una funzionalità simile a + cron per eseguire periodicamente questo progetto.

- Questa funzionalità è utilizzata principalmente per utilizzare Jenkins come - sostituto di cron e non è ideale per compilare continuativamente progetti - software. - - Quando si inizia ad adottare la continuous integration, spesso si è così - abituati all'idea di eseguire regolarmente delle compilazioni (ad es. - ogni notte od ogni settimana) da utilizzare questa funzionalità. Lo scopo - della continuous integration, tuttavia, è quello di avviare una compilazione - non appena si introduce una modifica, per fornire rapidamente un feedback - in merito. Per farlo è necessario - integrare le - notifiche delle modifiche apportate nel sistema di gestione del codice - sorgente in Jenkins. + Questa funzionalità è utilizzata principalmente per utilizzare Jenkins come + sostituto di cron e + non è ideale per compilare continuativamente progetti software + . Quando si inizia ad adottare la continuous integration, spesso si è così + abituati all'idea di eseguire regolarmente delle compilazioni (ad es. ogni + notte od ogni settimana) da utilizzare questa funzionalità. Lo scopo della + continuous integration, tuttavia, è quello di avviare una compilazione non + appena si introduce una modifica, per fornire rapidamente un feedback in + merito. Per farlo è necessario + + integrare le notifiche delle modifiche apportate nel sistema di gestione + del codice sorgente in Jenkins + + . +

- Prima di utilizzare questa funzionalità, pertanto, ci si fermi e ci si - chieda se questo è veramente ciò che si vuole. - + Prima di utilizzare questa funzionalità, pertanto, ci si fermi e ci si + chieda se questo è veramente ciò che si vuole. +

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 7d117cf6ab..01e0dfb3e8 100644 --- a/core/src/main/resources/hudson/triggers/TimerTrigger/help_ja.html +++ b/core/src/main/resources/hudson/triggers/TimerTrigger/help_ja.html @@ -1,18 +1,25 @@
- このプロジェクトを定期的に実行するクーロンのような機能を提供します。 + このプロジェクトを定期的に実行する + クーロン + のような機能を提供します。

- この機能は、クーロンの代替品としてJenkinsを使用するのが第一なので、 - プロジェクトの継続的なビルドに使用するのは、望ましくありません。 + この機能は、クーロンの代替品としてJenkinsを使用するのが第一なので、 + プロジェクトの継続的なビルドに使用するのは、望ましくありません。 + + 継続的インテグレーションのやりはじめの頃は、 + ナイトリーやウィークリーのようにビルドを定期的にスケジュールすることを考えがちで、 + この機能を使用します。しかしながら、継続的インテグレーションのポイントは、 + 変更したらすぐにビルドを開始し、変更へのフィードバックをすばやくすることです。 + そうするには、 + + 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 23ea6fb2d5..ad3171acc3 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 @@ -1,19 +1,29 @@
- Fornece uma funcionalidade ao estilo do cron + Fornece uma funcionalidade ao estilo do + cron para periodicamente executar este projeto.

- 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 - a idéia de construções agendadas regularmente como toda noite/semanalmente e assim elas - 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.. + 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 a idéia de construções + agendadas regularmente como toda noite/semanalmente e assim elas 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. + + . +

- Assim, antes de usar esta funcionalidade, pare e pergunte a si mesmo se isto é o que realmente você quer. - + 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 3a3a32bdf7..dedf9f9d98 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,25 @@
- �।��⠢��� cron-like �㭪樮���쭮��� - ��� 㪠����� �ᯨᠭ�� ᡮப �஥��. + �।��⠢��� + cron + -like �㭪樮���쭮��� ��� 㪠����� �ᯨᠭ�� ᡮப �஥��.

- �� �㭪�� � �᭮���� �㦭� ��� �ᯮ�짮����� Jenkins � ����⢥ - ������ cron, � �� ��稬 ��ࠧ�� ���室�� ��� ��ਮ���᪮� ᡮન �஥�⮢. - - ����� ���짮��⥫� ����� �⠫�������� � ���楯樥� �����뢭�� ��⥣�樨 - (continuous integration), ���筮 ��� �㬠�� � ॣ��୮� ����᪥ ᡮப, �த� - ����� ��� ��������. - ������, ���祢�� ���� �����뢭�� ��⥣�樨 � ����᪠ ᡮப ���������� ��᫥ - ���ᥭ�� ��������� � ���, ��� ����ண� ����祭�� १���� �� ���������� - ࠧࠡ��稪��. - - �⮡� ��������� Jenkins �뫮 ������ ⠪��, ����ன� - �����饭�� �� ��஭� SCM. + �� �㭪�� � �᭮���� �㦭� ��� �ᯮ�짮����� Jenkins � ����⢥ ������ cron, � + �� ��稬 ��ࠧ�� ���室�� ��� ��ਮ���᪮� ᡮન �஥�⮢ + . ����� ���짮��⥫� ����� �⠫�������� � ���楯樥� �����뢭�� ��⥣�樨 (continuous + integration), ���筮 ��� �㬠�� � ॣ��୮� ����᪥ ᡮப, �த� ����� ��� ��������. + ������, ���祢�� ���� �����뢭�� ��⥣�樨 � ����᪠ ᡮப + ���������� + ��᫥ ���ᥭ�� ��������� � ���, ��� ����ண� ����祭�� १���� �� ���������� + ࠧࠡ��稪��. �⮡� ��������� 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 00193471c6..03d3d51dae 100644 --- a/core/src/main/resources/hudson/triggers/TimerTrigger/help_tr.html +++ b/core/src/main/resources/hudson/triggers/TimerTrigger/help_tr.html @@ -1,18 +1,30 @@
- Bu özellik, projeyi periyodik olarak cron + Bu özellik, projeyi periyodik olarak + cron gibi çalıştırabilmeyi sağlar.

- Jenkins'i 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. + Jenkins'i 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 Jenkins'e bildirecek mekanizmanın + + ayarlanması gerekir. +

- 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 Jenkins'e 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. - + Yani, bu özelliği kullanmadan önce yapmak istediğinizin + bu yöntem ile mi yapılması gerektiğini sorgulayın. +

diff --git a/core/src/main/resources/hudson/triggers/TimerTrigger/help_zh_TW.html b/core/src/main/resources/hudson/triggers/TimerTrigger/help_zh_TW.html index 11dc9ee2fe..1138b27bfd 100644 --- a/core/src/main/resources/hudson/triggers/TimerTrigger/help_zh_TW.html +++ b/core/src/main/resources/hudson/triggers/TimerTrigger/help_zh_TW.html @@ -1,14 +1,21 @@
- 提供類似 cron 的功能，定期執行專案。 + 提供類似 + cron + 的功能，定期執行專案。

- 這個功能主要是讓 Jenkins 取代 cron，而且持續建置軟體專案並不是理想選項。 - - 大家第一次接觸持續整合 (Continuous Integration; CI) 時，常會有 Nightly 或 Weekly 建置的刻板印象，認為就該用這個功能為建置挑個良辰吉時。 - 但是，CI 的中心思想是個仁...不是啦，CI 的中心思想是在異動後盡快建置，讓大家馬上就能知道這次變更所造成的影響。 - 要達到這個目的，可以讓 SCM 在異動後主動通知 Jenkins。 - -

- 所以，在使用這個功能前，先停下來問問自己: 「我到底想要幹嘛?」 + 這個功能主要是讓 Jenkins 取代 cron，而且 + 持續建置軟體專案並不是理想選項 + 。 大家第一次接觸持續整合 (Continuous Integration; CI) 時，常會有 Nightly 或 + Weekly 建置的刻板印象，認為就該用這個功能為建置挑個良辰吉時。 但是，CI + 的中心思想是個仁...不是啦，CI + 的中心思想是在異動後盡快建置，讓大家馬上就能知道這次變更所造成的影響。 + 要達到這個目的，可以 + + 讓 SCM 在異動後主動通知 Jenkins + + 。 +

+

所以，在使用這個功能前，先停下來問問自己: 「我到底想要幹嘛?」

diff --git a/core/src/main/resources/hudson/views/BuildButtonColumn/icon.js b/core/src/main/resources/hudson/views/BuildButtonColumn/icon.js index 58d836b6f2..04a374e62c 100644 --- a/core/src/main/resources/hudson/views/BuildButtonColumn/icon.js +++ b/core/src/main/resources/hudson/views/BuildButtonColumn/icon.js @@ -1,12 +1,17 @@ -Behaviour.specify(".build-button-column-icon-reference-holder", 'build-button-column', 0, function (e) { - var url = e.getAttribute('data-url'); - var message = e.getAttribute('data-notification') - var id = e.getAttribute('data-id'); +Behaviour.specify( + ".build-button-column-icon-reference-holder", + "build-button-column", + 0, + function (e) { + var url = e.getAttribute("data-url"); + var message = e.getAttribute("data-notification"); + var id = e.getAttribute("data-id"); var icon = document.getElementById(id); - icon.onclick = function(el) { - new Ajax.Request(url); - hoverNotification(message, this, -100); - return false; - } -}); + icon.onclick = function (el) { + new Ajax.Request(url); + hoverNotification(message, this, -100); + return false; + }; + } +); diff --git a/core/src/main/resources/hudson/views/MyViewsTabBar/GlobalConfigurationImpl/help-myViewsTabBar.html b/core/src/main/resources/hudson/views/MyViewsTabBar/GlobalConfigurationImpl/help-myViewsTabBar.html index e3893e8566..b661339953 100644 --- a/core/src/main/resources/hudson/views/MyViewsTabBar/GlobalConfigurationImpl/help-myViewsTabBar.html +++ b/core/src/main/resources/hudson/views/MyViewsTabBar/GlobalConfigurationImpl/help-myViewsTabBar.html @@ -1,6 +1,8 @@
- If you have multiple views defined in My Views, then the default My Views TabBar becomes too long. The MyViewsTabBar - Extension Point provides facility for plugins to provide their own implementation of My Views TabBar. - This DropDown, lists all the available My Views TabBar implementation. Only one TabBar implementation can - be active at a time for My Views. Select one from the DropDown list. -
\ No newline at end of file + If you have multiple views defined in My Views, then the default My Views + TabBar becomes too long. The MyViewsTabBar Extension Point provides facility + for plugins to provide their own implementation of My Views TabBar. This + DropDown, lists all the available My Views TabBar implementation. Only one + TabBar implementation can be active at a time for My Views. Select one from + the DropDown list. + diff --git a/core/src/main/resources/hudson/views/MyViewsTabBar/GlobalConfigurationImpl/help-myViewsTabBar_bg.html b/core/src/main/resources/hudson/views/MyViewsTabBar/GlobalConfigurationImpl/help-myViewsTabBar_bg.html index e37a61aa9b..62f4377b51 100644 --- a/core/src/main/resources/hudson/views/MyViewsTabBar/GlobalConfigurationImpl/help-myViewsTabBar_bg.html +++ b/core/src/main/resources/hudson/views/MyViewsTabBar/GlobalConfigurationImpl/help-myViewsTabBar_bg.html @@ -1,7 +1,7 @@
- Ако сте създали множество собствени изгледи в „Моите изгледи“, лентата за - изгледите става прекалено дълга. Точката за разширение „MyViewsTabBar“ дава - възможност на приставките да предоставят собствена реализация на лентата. - Това падащо меню съдържа наличните реализации за лентата. Само една от тях - може да е включена. Изберете я от падащия списък. -
\ No newline at end of file + Ако сте създали множество собствени изгледи в „Моите изгледи“, лентата за + изгледите става прекалено дълга. Точката за разширение „MyViewsTabBar“ дава + възможност на приставките да предоставят собствена реализация на лентата. Това + падащо меню съдържа наличните реализации за лентата. Само една от тях може да + е включена. Изберете я от падащия списък. + diff --git a/core/src/main/resources/hudson/views/MyViewsTabBar/GlobalConfigurationImpl/help-myViewsTabBar_it.html b/core/src/main/resources/hudson/views/MyViewsTabBar/GlobalConfigurationImpl/help-myViewsTabBar_it.html index 8aba97587d..ec382c9caf 100644 --- a/core/src/main/resources/hudson/views/MyViewsTabBar/GlobalConfigurationImpl/help-myViewsTabBar_it.html +++ b/core/src/main/resources/hudson/views/MyViewsTabBar/GlobalConfigurationImpl/help-myViewsTabBar_it.html @@ -1,9 +1,9 @@
- Se vi sono più viste definite in Le mie viste, la barra schede Le mie viste - predefinita diventa troppo lunga. Il punto di estensione MyViewsTabBar - mette a disposizione un modo per i componenti aggiuntivi di fornire la - loro implementazione della barra schede Le mie viste. Quest'elenco a - discesa elenca tutte le implementazioni della barra schede Le mie viste - disponibili. Per Le mie viste può essere attiva solo un'implementazione - della barra schede alla volta. Selezionarne una dall'elenco a discesa. + Se vi sono più viste definite in Le mie viste, la barra schede Le mie viste + predefinita diventa troppo lunga. Il punto di estensione MyViewsTabBar mette a + disposizione un modo per i componenti aggiuntivi di fornire la loro + implementazione della barra schede Le mie viste. Quest'elenco a discesa elenca + tutte le implementazioni della barra schede Le mie viste disponibili. Per Le + mie viste può essere attiva solo un'implementazione della barra schede alla + volta. Selezionarne una dall'elenco a discesa.
diff --git a/core/src/main/resources/hudson/views/MyViewsTabBar/GlobalConfigurationImpl/help-myViewsTabBar_zh_TW.html b/core/src/main/resources/hudson/views/MyViewsTabBar/GlobalConfigurationImpl/help-myViewsTabBar_zh_TW.html index c6174c5b4c..69817a2dd5 100644 --- a/core/src/main/resources/hudson/views/MyViewsTabBar/GlobalConfigurationImpl/help-myViewsTabBar_zh_TW.html +++ b/core/src/main/resources/hudson/views/MyViewsTabBar/GlobalConfigurationImpl/help-myViewsTabBar_zh_TW.html @@ -1,6 +1,6 @@
- 如果您「我的視景」裡有多個視景，預設的「我的視景索引標籤列」會太長。 - MyViewsTabBar 擴充點能讓外掛程式提供自己的「我的視景索引標籤列」實作。 - 這個下拉選單列出可以用的「我的視景索引標籤列」實作。 - 「我的視景」裡一次只能啟用一種「索引標籤列」實作，請由下拉選單中挑一個。 -
\ No newline at end of file + 如果您「我的視景」裡有多個視景，預設的「我的視景索引標籤列」會太長。 + MyViewsTabBar 擴充點能讓外掛程式提供自己的「我的視景索引標籤列」實作。 + 這個下拉選單列出可以用的「我的視景索引標籤列」實作。 + 「我的視景」裡一次只能啟用一種「索引標籤列」實作，請由下拉選單中挑一個。 + diff --git a/core/src/main/resources/hudson/views/ViewsTabBar/GlobalConfigurationImpl/help-viewsTabBar.html b/core/src/main/resources/hudson/views/ViewsTabBar/GlobalConfigurationImpl/help-viewsTabBar.html index 705298564f..b573c4f0ae 100644 --- a/core/src/main/resources/hudson/views/ViewsTabBar/GlobalConfigurationImpl/help-viewsTabBar.html +++ b/core/src/main/resources/hudson/views/ViewsTabBar/GlobalConfigurationImpl/help-viewsTabBar.html @@ -1,6 +1,7 @@
- If you have multiple views defined, then the default Views TabBar becomes too long. The ViewsToolBar - Extension Point provides facility for plugins to provide their own implementation of Views TabBar. - This DropDown, lists all the available Views TabBar implementation. Only one TabBar implementation can - be active at a time. Select one from the DropDown list. -
\ No newline at end of file + If you have multiple views defined, then the default Views TabBar becomes too + long. The ViewsToolBar Extension Point provides facility for plugins to + provide their own implementation of Views TabBar. This DropDown, lists all the + available Views TabBar implementation. Only one TabBar implementation can be + active at a time. Select one from the DropDown list. + diff --git a/core/src/main/resources/hudson/views/ViewsTabBar/GlobalConfigurationImpl/help-viewsTabBar_bg.html b/core/src/main/resources/hudson/views/ViewsTabBar/GlobalConfigurationImpl/help-viewsTabBar_bg.html index 2c4e9cc5a5..6fd1f3152e 100644 --- a/core/src/main/resources/hudson/views/ViewsTabBar/GlobalConfigurationImpl/help-viewsTabBar_bg.html +++ b/core/src/main/resources/hudson/views/ViewsTabBar/GlobalConfigurationImpl/help-viewsTabBar_bg.html @@ -1,8 +1,7 @@
- - Ако сте създали множество собствени изгледи, стандартната лента за изгледите - става прекалено дълга. Точката за разширение „ViewsToolBar“ дава възможност - на приставките да предоставят собствена реализация на лентата. Това падащо - меню съдържа наличните реализации за лентата. Само една от тях може да е - включена. Изберете я от падащия списък. -
\ No newline at end of file + Ако сте създали множество собствени изгледи, стандартната лента за изгледите + става прекалено дълга. Точката за разширение „ViewsToolBar“ дава възможност на + приставките да предоставят собствена реализация на лентата. Това падащо меню + съдържа наличните реализации за лентата. Само една от тях може да е включена. + Изберете я от падащия списък. + diff --git a/core/src/main/resources/hudson/views/ViewsTabBar/GlobalConfigurationImpl/help-viewsTabBar_it.html b/core/src/main/resources/hudson/views/ViewsTabBar/GlobalConfigurationImpl/help-viewsTabBar_it.html index 342623e289..6ee8f6e173 100644 --- a/core/src/main/resources/hudson/views/ViewsTabBar/GlobalConfigurationImpl/help-viewsTabBar_it.html +++ b/core/src/main/resources/hudson/views/ViewsTabBar/GlobalConfigurationImpl/help-viewsTabBar_it.html @@ -1,9 +1,8 @@
- Se sono state definite più viste, la barra schede Viste predefinita diventa - troppo lunga. Il punto di estensione ViewsTabBar mette a disposizione un - modo per i componenti aggiuntivi di fornire la loro implementazione della - barra schede Viste. Quest'elenco a discesa elenca tutte le implementazioni - della barra schede Viste disponibili. Puòò essere attiva solo - un'implementazione della barra schede alla volta. Selezionarne una - dall'elenco a discesa. + Se sono state definite più viste, la barra schede Viste predefinita diventa + troppo lunga. Il punto di estensione ViewsTabBar mette a disposizione un modo + per i componenti aggiuntivi di fornire la loro implementazione della barra + schede Viste. Quest'elenco a discesa elenca tutte le implementazioni della + barra schede Viste disponibili. Puòò essere attiva solo un'implementazione + della barra schede alla volta. Selezionarne una dall'elenco a discesa.
diff --git a/core/src/main/resources/hudson/views/ViewsTabBar/GlobalConfigurationImpl/help-viewsTabBar_zh_TW.html b/core/src/main/resources/hudson/views/ViewsTabBar/GlobalConfigurationImpl/help-viewsTabBar_zh_TW.html index 2a62dae361..792317807d 100644 --- a/core/src/main/resources/hudson/views/ViewsTabBar/GlobalConfigurationImpl/help-viewsTabBar_zh_TW.html +++ b/core/src/main/resources/hudson/views/ViewsTabBar/GlobalConfigurationImpl/help-viewsTabBar_zh_TW.html @@ -1,6 +1,6 @@
- 如果您有多個視景，預設的「視景索引標籤列」會太長。 - ViewsTabBar 擴充點能讓外掛程式提供自己的「視景索引標籤列」實作。 - 這個下拉選單列出可以用的「視景索引標籤列」實作。 - 只能啟用一種「索引標籤列」實作，請由下拉選單中挑一個。 -
\ No newline at end of file + 如果您有多個視景，預設的「視景索引標籤列」會太長。 ViewsTabBar + 擴充點能讓外掛程式提供自己的「視景索引標籤列」實作。 + 這個下拉選單列出可以用的「視景索引標籤列」實作。 + 只能啟用一種「索引標籤列」實作，請由下拉選單中挑一個。 + diff --git a/core/src/main/resources/jenkins/diagnostics/URICheckEncodingMonitor/adjunct.js b/core/src/main/resources/jenkins/diagnostics/URICheckEncodingMonitor/adjunct.js index 2d06c512ee..b07075e1e3 100644 --- a/core/src/main/resources/jenkins/diagnostics/URICheckEncodingMonitor/adjunct.js +++ b/core/src/main/resources/jenkins/diagnostics/URICheckEncodingMonitor/adjunct.js @@ -1,10 +1,13 @@ -Behaviour.specify('#URICheckEncodingMonitor-message', 'URICheckEncodingMonitor', 0, function(element) { - var url = element.getAttribute('data-url'); - var params = {value : '\u57f7\u4e8b'}; - var checkAjax = new Ajax.Updater( - 'URICheckEncodingMonitor-message', url, - { - method: 'get', parameters: params - } - ); -}); +Behaviour.specify( + "#URICheckEncodingMonitor-message", + "URICheckEncodingMonitor", + 0, + function (element) { + var url = element.getAttribute("data-url"); + var params = { value: "\u57f7\u4e8b" }; + var checkAjax = new Ajax.Updater("URICheckEncodingMonitor-message", url, { + method: "get", + parameters: params, + }); + } +); diff --git a/core/src/main/resources/jenkins/formelementpath/form-element-path.js b/core/src/main/resources/jenkins/formelementpath/form-element-path.js index 6c512faeea..0bb16e7a59 100644 --- a/core/src/main/resources/jenkins/formelementpath/form-element-path.js +++ b/core/src/main/resources/jenkins/formelementpath/form-element-path.js @@ -5,193 +5,208 @@ * Instead of selecting by xpath with something like div/span/input[text() = 'Name'] * You can use the path attribute: /org-jenkinsci-plugins-workflow-libs-FolderLibraries/libraries/name */ -document.addEventListener("DOMContentLoaded", function(){ - // most of this is copied from hudson-behaviour.js - function buildFormTree(form) { - form.formDom = {}; // root object - - var doms = []; // DOMs that we added 'formDom' for. - doms.push(form); - - function addProperty(parent, name, value) { - name = shortenName(name); - if (parent[name] != null) { - if (parent[name].push == null) // is this array? - parent[name] = [parent[name]]; - parent[name].push(value); - } else { - parent[name] = value; - } - } - - // find the grouping parent node, which will have @name. - // then return the corresponding object in the map - function findParent(e) { - var p = findFormParent(e, form); - if (p == null) return {}; - - var m = p.formDom; - if (m == null) { - // this is a new grouping node - doms.push(p); - p.formDom = m = {}; - addProperty(findParent(p), p.getAttribute("name"), p); - } - return m; - } +document.addEventListener("DOMContentLoaded", function () { + // most of this is copied from hudson-behaviour.js + function buildFormTree(form) { + form.formDom = {}; // root object + + var doms = []; // DOMs that we added 'formDom' for. + doms.push(form); + + function addProperty(parent, name, value) { + name = shortenName(name); + if (parent[name] != null) { + if (parent[name].push == null) + // is this array? + parent[name] = [parent[name]]; + parent[name].push(value); + } else { + parent[name] = value; + } + } - var jsonElement = null; + // find the grouping parent node, which will have @name. + // then return the corresponding object in the map + function findParent(e) { + var p = findFormParent(e, form); + if (p == null) return {}; + + var m = p.formDom; + if (m == null) { + // this is a new grouping node + doms.push(p); + p.formDom = m = {}; + addProperty(findParent(p), p.getAttribute("name"), p); + } + return m; + } - for (var i = 0; i < form.elements.length; i++) { - var e = form.elements[i]; - if (e.name == "json") { - jsonElement = e; - continue; + var jsonElement = null; + + for (var i = 0; i < form.elements.length; i++) { + var e = form.elements[i]; + if (e.name == "json") { + jsonElement = e; + continue; + } + if (e.tagName == "FIELDSET") continue; + if (e.tagName == "SELECT" && e.multiple) { + addProperty(findParent(e), e.name, e); + continue; + } + + var p; + var type = e.getAttribute("type"); + if (type == null) type = ""; + switch (type.toLowerCase()) { + case "button": + var element; + // modern buttons aren't wrapped in spans + if ( + e.classList.contains("jenkins-button") || + e.classList.contains("repeatable-delete") + ) { + p = findParent(e); + element = e; + } else { + p = findParent(e); + element = e.parentNode.parentNode; // YUI's surrounding that has interesting classes + } + var name = null; + [ + "repeatable-add", + "repeatable-delete", + "hetero-list-add", + "expand-button", + "advanced-button", + "apply-button", + "validate-button", + ].forEach(function (clazz) { + if (element.classList.contains(clazz)) { + name = clazz; } - if (e.tagName == "FIELDSET") - continue; - if (e.tagName == "SELECT" && e.multiple) { - addProperty(findParent(e), e.name, e); - continue; + }); + if (name == null) { + if (name == null) { + element = element.parentNode.previousSibling; + if ( + element != null && + element.classList && + element.classList.contains("repeatable-insertion-point") + ) { + name = "hetero-list-add"; + } } - - var p; - var type = e.getAttribute("type"); - if (type == null) type = ""; - switch (type.toLowerCase()) { - case "button": - var element - // modern buttons aren't wrapped in spans - if (e.classList.contains('jenkins-button') || e.classList.contains('repeatable-delete')) { - p = findParent(e); - element = e - } else { - p = findParent(e); - element = e.parentNode.parentNode; // YUI's surrounding that has interesting classes - } - var name = null; - ["repeatable-add", "repeatable-delete", "hetero-list-add", "expand-button", "advanced-button", "apply-button", "validate-button"] - .forEach(function (clazz) { - if (element.classList.contains(clazz)) { - name = clazz; - } - }); - if (name == null) { - if (name == null) { - element = element.parentNode.previousSibling; - if (element != null && element.classList && element.classList.contains('repeatable-insertion-point')) { - name = "hetero-list-add"; - } - } - } - if (name != null) { - addProperty(p, name, e); - } - break; - case "submit": - break; - case "checkbox": - case "radio": - p = findParent(e); - if (e.groupingNode) { - e.formDom = {}; - } - addProperty(p, e.name, e); - break; - case "file": - // to support structured form submission with file uploads, - // rename form field names to unique ones, and leave this name mapping information - // in JSON. this behavior is backward incompatible, so only do - // this when - p = findParent(e); - if (e.getAttribute("jsonAware") != null) { - var on = e.getAttribute("originalName"); - if (on != null) { - addProperty(p, on, e); - } else { - addProperty(p, e.name, e); - } - } - break; - // otherwise fall through - default: - p = findParent(e); - addProperty(p, e.name, e); - break; + } + if (name != null) { + addProperty(p, name, e); + } + break; + case "submit": + break; + case "checkbox": + case "radio": + p = findParent(e); + if (e.groupingNode) { + e.formDom = {}; + } + addProperty(p, e.name, e); + break; + case "file": + // to support structured form submission with file uploads, + // rename form field names to unique ones, and leave this name mapping information + // in JSON. this behavior is backward incompatible, so only do + // this when + p = findParent(e); + if (e.getAttribute("jsonAware") != null) { + var on = e.getAttribute("originalName"); + if (on != null) { + addProperty(p, on, e); + } else { + addProperty(p, e.name, e); } - } + } + break; + // otherwise fall through + default: + p = findParent(e); + addProperty(p, e.name, e); + break; + } + } - function annotate(e, path) { - e.setAttribute("path", path); - var o = e.formDom || {}; - for (var key in o) { - var v = o[key]; - - function child(v, i) { - var suffix = null; - var newKey = key; - if (v.parentNode.className && v.parentNode.className.indexOf("one-each") > -1 && v.parentNode.className.indexOf("honor-order") > -1) { - suffix = v.getAttribute("descriptorId").split(".").pop() - } else if (v.getAttribute("type") == "radio") { - suffix = v.value - while (newKey.substring(0, 8) == 'removeme') - newKey = newKey.substring(newKey.indexOf('_', 8) + 1); - } else if (v.getAttribute("suffix") != null) { - suffix = v.getAttribute("suffix") - } else { - if (i > 0) - suffix = i; - } - if (suffix == null) suffix = ""; - else suffix = '[' + suffix + ']'; - - annotate(v, path + "/" + newKey + suffix); - } - - if (v instanceof Array) { - var i = 0; - v.forEach(function (v) { - child(v, i++) - }) - } else { - child(v, 0) - } - } + function annotate(e, path) { + e.setAttribute("path", path); + var o = e.formDom || {}; + for (var key in o) { + var v = o[key]; + + function child(v, i) { + var suffix = null; + var newKey = key; + if ( + v.parentNode.className && + v.parentNode.className.indexOf("one-each") > -1 && + v.parentNode.className.indexOf("honor-order") > -1 + ) { + suffix = v.getAttribute("descriptorId").split(".").pop(); + } else if (v.getAttribute("type") == "radio") { + suffix = v.value; + while (newKey.substring(0, 8) == "removeme") + newKey = newKey.substring(newKey.indexOf("_", 8) + 1); + } else if (v.getAttribute("suffix") != null) { + suffix = v.getAttribute("suffix"); + } else { + if (i > 0) suffix = i; + } + if (suffix == null) suffix = ""; + else suffix = "[" + suffix + "]"; + + annotate(v, path + "/" + newKey + suffix); + } + if (v instanceof Array) { + var i = 0; + v.forEach(function (v) { + child(v, i++); + }); + } else { + child(v, 0); } + } + } - annotate(form, ""); + annotate(form, ""); - // clean up - for (i = 0; i < doms.length; i++) - doms[i].formDom = null; + // clean up + for (i = 0; i < doms.length; i++) doms[i].formDom = null; - return true; - } + return true; + } - function applyAll() { - document.querySelectorAll("FORM").forEach(function (e) { - buildFormTree(e); - }) - } + function applyAll() { + document.querySelectorAll("FORM").forEach(function (e) { + buildFormTree(e); + }); + } - /* JavaScript sometimes re-arranges the DOM and doesn't call layout callback - * known cases: YUI buttons, CodeMirror. - * We run apply twice to work around this, once immediately so that most cases work and the tests don't need to wait, - * and once to catch the edge cases. - */ - function hardenedApplyAll () { - applyAll(); - - setTimeout(function () { - applyAll(); - }, 1000); - } + /* JavaScript sometimes re-arranges the DOM and doesn't call layout callback + * known cases: YUI buttons, CodeMirror. + * We run apply twice to work around this, once immediately so that most cases work and the tests don't need to wait, + * and once to catch the edge cases. + */ + function hardenedApplyAll() { + applyAll(); + + setTimeout(function () { + applyAll(); + }, 1000); + } - hardenedApplyAll(); + hardenedApplyAll(); - layoutUpdateCallback.add(hardenedApplyAll) + layoutUpdateCallback.add(hardenedApplyAll); - // expose this globally so that Selenium can call it - window.recomputeFormElementPath = hardenedApplyAll; + // expose this globally so that Selenium can call it + window.recomputeFormElementPath = hardenedApplyAll; }); diff --git a/core/src/main/resources/jenkins/install/platform-plugins.json b/core/src/main/resources/jenkins/install/platform-plugins.json index 2cd2050bfc..aa3d62236a 100644 --- a/core/src/main/resources/jenkins/install/platform-plugins.json +++ b/core/src/main/resources/jenkins/install/platform-plugins.json @@ -1,107 +1,104 @@ [ - { - "category":"Organization and Administration", - "plugins": [ - { "name": "dashboard-view" }, - { "name": "cloudbees-folder", "suggested": true }, - { "name": "configuration-as-code" }, - { "name": "antisamy-markup-formatter", "suggested": true } - ] - }, - { - "category":"Build Features", - "description":"Add general purpose features to your jobs", - "plugins": [ - { "name": "build-name-setter" }, - { "name": "build-timeout", "suggested": true }, - { "name": "config-file-provider" }, - { "name": "credentials-binding", "suggested": true }, - { "name": "embeddable-build-status" }, - { "name": "rebuild" }, - { "name": "ssh-agent" }, - { "name": "throttle-concurrents" }, - { "name": "timestamper", "suggested": true }, - { "name": "ws-cleanup", "suggested": true } - ] - }, - { - "category":"Build Tools", - "plugins": [ - { "name": "ant", "suggested": true }, - { "name": "gradle", "suggested": true }, - { "name": "msbuild" }, - { "name": "nodejs" } - ] - }, - { - "category":"Build Analysis and Reporting", - "plugins": [ - { "name": "cobertura" }, - { "name": "htmlpublisher" }, - { "name": "junit" }, - { "name": "warnings-ng" }, - { "name": "xunit" } - ] - }, - { - "category":"Pipelines and Continuous Delivery", - "plugins": [ - { "name": "workflow-aggregator", "suggested": true, "added": "2.0" }, - { "name": "github-branch-source", "suggested": true, "added": "2.0" }, - { "name": "pipeline-github-lib", "suggested": true, "added": "2.0" }, - { "name": "pipeline-stage-view", "suggested": true, "added": "2.0" }, - { "name": "conditional-buildstep" }, - { "name": "jenkins-multijob-plugin" }, - { "name": "parameterized-trigger" }, - { "name": "copyartifact" } - ] - }, - { - "category":"Source Code Management", - "plugins": [ - { "name": "bitbucket" }, - { "name": "clearcase" }, - { "name": "cvs" }, - { "name": "git", "suggested": true }, - { "name": "git-parameter" }, - { "name": "github" }, - { "name": "gitlab-plugin" }, - { "name": "p4" }, - { "name": "repo" }, - { "name": "subversion" } - ] - }, - { - "category":"Distributed Builds", - "plugins": [ - { "name": "matrix-project" }, - { "name": "ssh-slaves", "suggested": true }, - { "name": "windows-slaves" } - ] - }, - { - "category":"User Management and Security", - "plugins": [ - { "name": "matrix-auth", "suggested": true }, - { "name": "pam-auth", "suggested": true }, - { "name": "ldap", "suggested": true }, - { "name": "role-strategy" }, - { "name": "active-directory" } - ] - }, - { - "category":"Notifications and Publishing", - "plugins": [ - { "name": "email-ext", "suggested": true }, - { "name": "emailext-template" }, - { "name": "mailer", "suggested": true } - ] - }, - { - "category":"Languages", - "plugins": [ - { "name": "locale"}, - { "name": "localization-zh-cn"} - ] - } + { + "category": "Organization and Administration", + "plugins": [ + { "name": "dashboard-view" }, + { "name": "cloudbees-folder", "suggested": true }, + { "name": "configuration-as-code" }, + { "name": "antisamy-markup-formatter", "suggested": true } + ] + }, + { + "category": "Build Features", + "description": "Add general purpose features to your jobs", + "plugins": [ + { "name": "build-name-setter" }, + { "name": "build-timeout", "suggested": true }, + { "name": "config-file-provider" }, + { "name": "credentials-binding", "suggested": true }, + { "name": "embeddable-build-status" }, + { "name": "rebuild" }, + { "name": "ssh-agent" }, + { "name": "throttle-concurrents" }, + { "name": "timestamper", "suggested": true }, + { "name": "ws-cleanup", "suggested": true } + ] + }, + { + "category": "Build Tools", + "plugins": [ + { "name": "ant", "suggested": true }, + { "name": "gradle", "suggested": true }, + { "name": "msbuild" }, + { "name": "nodejs" } + ] + }, + { + "category": "Build Analysis and Reporting", + "plugins": [ + { "name": "cobertura" }, + { "name": "htmlpublisher" }, + { "name": "junit" }, + { "name": "warnings-ng" }, + { "name": "xunit" } + ] + }, + { + "category": "Pipelines and Continuous Delivery", + "plugins": [ + { "name": "workflow-aggregator", "suggested": true, "added": "2.0" }, + { "name": "github-branch-source", "suggested": true, "added": "2.0" }, + { "name": "pipeline-github-lib", "suggested": true, "added": "2.0" }, + { "name": "pipeline-stage-view", "suggested": true, "added": "2.0" }, + { "name": "conditional-buildstep" }, + { "name": "jenkins-multijob-plugin" }, + { "name": "parameterized-trigger" }, + { "name": "copyartifact" } + ] + }, + { + "category": "Source Code Management", + "plugins": [ + { "name": "bitbucket" }, + { "name": "clearcase" }, + { "name": "cvs" }, + { "name": "git", "suggested": true }, + { "name": "git-parameter" }, + { "name": "github" }, + { "name": "gitlab-plugin" }, + { "name": "p4" }, + { "name": "repo" }, + { "name": "subversion" } + ] + }, + { + "category": "Distributed Builds", + "plugins": [ + { "name": "matrix-project" }, + { "name": "ssh-slaves", "suggested": true }, + { "name": "windows-slaves" } + ] + }, + { + "category": "User Management and Security", + "plugins": [ + { "name": "matrix-auth", "suggested": true }, + { "name": "pam-auth", "suggested": true }, + { "name": "ldap", "suggested": true }, + { "name": "role-strategy" }, + { "name": "active-directory" } + ] + }, + { + "category": "Notifications and Publishing", + "plugins": [ + { "name": "email-ext", "suggested": true }, + { "name": "emailext-template" }, + { "name": "mailer", "suggested": true } + ] + }, + { + "category": "Languages", + "plugins": [{ "name": "locale" }, { "name": "localization-zh-cn" }] + } ] diff --git a/core/src/main/resources/jenkins/management/AdministrativeMonitorsDecorator/resources.css b/core/src/main/resources/jenkins/management/AdministrativeMonitorsDecorator/resources.css index d84d74c962..4ba87376ae 100644 --- a/core/src/main/resources/jenkins/management/AdministrativeMonitorsDecorator/resources.css +++ b/core/src/main/resources/jenkins/management/AdministrativeMonitorsDecorator/resources.css @@ -1,179 +1,177 @@ .am-container { - height: 100%; + height: 100%; } .am-button { - position: relative; + position: relative; } .am-button .am-monitor__indicator-mobile { - display: none; - position: absolute; - top: .25rem; - right: .25rem; - border-radius: 50%; - width: .65rem; - height: .65rem; - background-color: #ff9800; + display: none; + position: absolute; + top: 0.25rem; + right: 0.25rem; + border-radius: 50%; + width: 0.65rem; + height: 0.65rem; + background-color: #ff9800; } .security-am .am-monitor__indicator-mobile { - background-color: #dc3545; + background-color: #dc3545; } .am-button .am-monitor__count { - display: inline-block; - display: inline-flex; - justify-content: center; - align-items: center; - height: 20px; - min-width: 20px; + display: inline-block; + display: inline-flex; + justify-content: center; + align-items: center; + height: 20px; + min-width: 20px; - color:#fff; - background-color: #ff9800; - font-weight: bold; + color: #fff; + background-color: #ff9800; + font-weight: bold; - border-radius: 4px; + border-radius: 4px; } .am-button.security-am .am-monitor__count { - color:#fff; - background-color: #dc3545; + color: #fff; + background-color: #dc3545; } .am-container div.am-list { - position: absolute; - top: 48px; - right: 2%; - height: auto; - z-index: 0; - padding: 2em; - text-align: left; - display: block; - background-color: #fff; - background-color: var(--background); - border-radius: 5px; - - /* Darken the box shadow to make the popup visible over the search box */ - box-shadow: 0 1px 7px 0 rgba(0,0,0,0.3); - - transition: all .15s cubic-bezier(.84,.03,.21,.96); - opacity: 0; - transform: scale(0); + position: absolute; + top: 48px; + right: 2%; + height: auto; + z-index: 0; + padding: 2em; + text-align: left; + display: block; + background-color: #fff; + background-color: var(--background); + border-radius: 5px; + + /* Darken the box shadow to make the popup visible over the search box */ + box-shadow: 0 1px 7px 0 rgba(0, 0, 0, 0.3); + + transition: all 0.15s cubic-bezier(0.84, 0.03, 0.21, 0.96); + opacity: 0; + transform: scale(0); } .am-container.visible div.am-list { - opacity: 1; - transform: scale(1); - z-index: 1000; + opacity: 1; + transform: scale(1); + z-index: 1000; } .am-container.visible .am-button { - background-color: #404040; - background-color: var(--header-link-bg-classic-active); - text-decoration: none; + background-color: #404040; + background-color: var(--header-link-bg-classic-active); + text-decoration: none; } .am-container .am-button:after { - content: ''; - display: inline-block; - position: absolute; - bottom: 0; - left: 32%; - width: 0; - height: 0; - border-left: 7px solid transparent; - border-right: 7px solid transparent; - border-bottom: 7px solid #fff; - opacity: 0; - transition: all .05s; - z-index: 1001; + content: ""; + display: inline-block; + position: absolute; + bottom: 0; + left: 32%; + width: 0; + height: 0; + border-left: 7px solid transparent; + border-right: 7px solid transparent; + border-bottom: 7px solid #fff; + opacity: 0; + transition: all 0.05s; + z-index: 1001; } .am-container.visible .am-button:after { - opacity: 1; - transition: all .25s; + opacity: 1; + transition: all 0.25s; } .am-container .am-message { - display: block; - line-height: 1.4em; - margin-bottom: 1.4em; + display: block; + line-height: 1.4em; + margin-bottom: 1.4em; } .am-message-list { - padding: 0; + padding: 0; } .am-container .am-message .alert form { - position: relative; - float: right; - margin: -6px 0 0 0 !important; - + position: relative; + float: right; + margin: -6px 0 0 0 !important; } .am-container .am-message .alert form span { - margin: 0 0 0 4px !important; + margin: 0 0 0 4px !important; } .am-container .am-message .alert { - margin-bottom: 0 !important; + margin-bottom: 0 !important; } .am-container .am-message dl dt::after { - content: ": "; + content: ": "; } /* Restore hyperlink style overriden by the page header */ .am-container .am-list a:link { - display: inline-block; - color: #204A87; - color: var(--link-color); - text-decoration: underline; - margin-right: 0; - padding: 0; - font-weight: 600; - font-weight: var(--link-font-weight); + display: inline-block; + color: #204a87; + color: var(--link-color); + text-decoration: underline; + margin-right: 0; + padding: 0; + font-weight: 600; + font-weight: var(--link-font-weight); } .am-container .am-list a:visited { - color: #5c3566; - color: var(--link-color); + color: #5c3566; + color: var(--link-color); } .am-container .am-list a:hover, .am-container .am-list a:focus, .am-container .am-list a:active { - color: #5c3566; - color: var(--link-color); - background-color: transparent; - text-decoration: underline; - text-decoration: var(--link-text-decoration--hover); + color: #5c3566; + color: var(--link-color); + background-color: transparent; + text-decoration: underline; + text-decoration: var(--link-text-decoration--hover); } .am-container .am-list .alert-success a { - color: #155724; - color: var(--alert-success-text-color); + color: #155724; + color: var(--alert-success-text-color); } - .am-container .am-list .alert-info a { - color: #31708f; - color: var(--alert-info-text-color); + color: #31708f; + color: var(--alert-info-text-color); } .am-container .am-list .alert-warning a { - color: #8a6d3b; - color: var(--alert-warning-text-color); + color: #8a6d3b; + color: var(--alert-warning-text-color); } .am-container .am-list .alert-danger a { - color: #a94442; - color: var(--alert-danger-text-color); + color: #a94442; + color: var(--alert-danger-text-color); } @media screen and (max-width: 576px) { - /* Hide non-security monitors on mobile view to avoid messing up the heading */ - #visible-am-container { - display: none; - } + /* Hide non-security monitors on mobile view to avoid messing up the heading */ + #visible-am-container { + display: none; + } } @media screen and (max-width: 768px) { - .am-button .am-monitor__indicator-mobile { - display: block; - } - .am-button .am-monitor__count { - display: none; - } + .am-button .am-monitor__indicator-mobile { + display: block; + } + .am-button .am-monitor__count { + display: none; + } } diff --git a/core/src/main/resources/jenkins/management/AdministrativeMonitorsDecorator/resources.js b/core/src/main/resources/jenkins/management/AdministrativeMonitorsDecorator/resources.js index b5e4caf338..6ada7b931e 100644 --- a/core/src/main/resources/jenkins/management/AdministrativeMonitorsDecorator/resources.js +++ b/core/src/main/resources/jenkins/management/AdministrativeMonitorsDecorator/resources.js @@ -1,95 +1,103 @@ (function () { - function initializeAmMonitor(amMonitorRoot, options) { - var button = amMonitorRoot.querySelector('.am-button'); - var amList = amMonitorRoot.querySelector('.am-list'); - if (button === null || amList === null) return null; + function initializeAmMonitor(amMonitorRoot, options) { + var button = amMonitorRoot.querySelector(".am-button"); + var amList = amMonitorRoot.querySelector(".am-list"); + if (button === null || amList === null) return null; - var url = button.getAttribute('data-href'); + var url = button.getAttribute("data-href"); - function onClose(e) { - var list = amList; - var el = e.target; - while (el) { - if (el === list) { - return; // clicked in the list - } - el = el.parentElement; - } - close(); + function onClose(e) { + var list = amList; + var el = e.target; + while (el) { + if (el === list) { + return; // clicked in the list } - function onEscClose(e) { - var escapeKeyCode = 27; - if (e.keyCode === escapeKeyCode) { - close(); - } - } - - function show() { - if (options.closeAll) options.closeAll(); + el = el.parentElement; + } + close(); + } + function onEscClose(e) { + var escapeKeyCode = 27; + if (e.keyCode === escapeKeyCode) { + close(); + } + } - new Ajax.Request(url, { - method: "GET", - onSuccess: function(rsp) { - var popupContent = rsp.responseText; - amList.innerHTML = popupContent; - amMonitorRoot.classList.add('visible'); - document.addEventListener('click', onClose); - document.addEventListener('keydown', onEscClose); + function show() { + if (options.closeAll) options.closeAll(); - // Applies all initialization code to the elements within the popup - // Among other things, this sets the CSRF crumb to the forms within - Behaviour.applySubtree(amList); - } - }); - } + new Ajax.Request(url, { + method: "GET", + onSuccess: function (rsp) { + var popupContent = rsp.responseText; + amList.innerHTML = popupContent; + amMonitorRoot.classList.add("visible"); + document.addEventListener("click", onClose); + document.addEventListener("keydown", onEscClose); - function close() { - amMonitorRoot.classList.remove('visible'); - amList.innerHTML = ''; - document.removeEventListener('click', onClose); - document.removeEventListener('keydown', onEscClose); - } + // Applies all initialization code to the elements within the popup + // Among other things, this sets the CSRF crumb to the forms within + Behaviour.applySubtree(amList); + }, + }); + } - function toggle(e) { - if (amMonitorRoot.classList.contains('visible')) { - close(); - } else { - show(); - } - e.preventDefault(); - } + function close() { + amMonitorRoot.classList.remove("visible"); + amList.innerHTML = ""; + document.removeEventListener("click", onClose); + document.removeEventListener("keydown", onEscClose); + } - function startListeners() { - button.addEventListener('click', toggle); - } + function toggle(e) { + if (amMonitorRoot.classList.contains("visible")) { + close(); + } else { + show(); + } + e.preventDefault(); + } - return { - close: close, - startListeners: startListeners, - } + function startListeners() { + button.addEventListener("click", toggle); } - document.addEventListener('DOMContentLoaded', function () { - var monitorWidgets; + return { + close: close, + startListeners: startListeners, + }; + } - function closeAll() { - monitorWidgets.forEach(function (widget) { - widget.close(); - }) - } + document.addEventListener("DOMContentLoaded", function () { + var monitorWidgets; + + function closeAll() { + monitorWidgets.forEach(function (widget) { + widget.close(); + }); + } - var normalMonitors = initializeAmMonitor(document.getElementById('visible-am-container'), { - closeAll: closeAll, - }); - var securityMonitors = initializeAmMonitor(document.getElementById('visible-sec-am-container'), { - closeAll: closeAll, - }); - monitorWidgets = [normalMonitors, securityMonitors].filter(function (widget) { - return widget !== null; - }); + var normalMonitors = initializeAmMonitor( + document.getElementById("visible-am-container"), + { + closeAll: closeAll, + } + ); + var securityMonitors = initializeAmMonitor( + document.getElementById("visible-sec-am-container"), + { + closeAll: closeAll, + } + ); + monitorWidgets = [normalMonitors, securityMonitors].filter(function ( + widget + ) { + return widget !== null; + }); - monitorWidgets.forEach(function (widget) { - widget.startListeners(); - }); + monitorWidgets.forEach(function (widget) { + widget.startListeners(); }); + }); })(); diff --git a/core/src/main/resources/jenkins/model/BuildDiscarderProperty/help.html b/core/src/main/resources/jenkins/model/BuildDiscarderProperty/help.html index 5557f117f6..421e648189 100644 --- a/core/src/main/resources/jenkins/model/BuildDiscarderProperty/help.html +++ b/core/src/main/resources/jenkins/model/BuildDiscarderProperty/help.html @@ -3,47 +3,65 @@ discarded. Build records include the console output, archived artifacts, and any other metadata related to a particular build.

- Keeping fewer builds means less disk space will be used in the Build Record - Root Directory, which is specified on the Configure System screen. + Keeping fewer builds means less disk space will be used in the + Build Record Root Directory + , which is specified on the + Configure System + screen. +

+

- - Jenkins offers two options for determining when builds should be discarded: + Jenkins offers two options for determining when builds should be discarded: +

+
  1. - Build age: discard builds when they reach a certain age; for example, seven - days old. + Build age: discard builds when they reach a certain age; for example, + seven days old. +
    2. +
  2. Build count: discard the oldest build when a certain number of builds already exist. +
+ These two options can be active at the same time, so you can keep builds for - 14 days, but only up to a limit of 50 builds, for example. If either limit is + 14 days, but only up to a limit of 50 builds, for example. If either limit is exceeded, then any builds beyond that limit will be discarded.

- You can also ensure that important builds are kept forever, regardless of the - setting here — click the Keep this build forever button on the - build page. -
- The last stable and last successful build are also excluded from these rules. - -

- - In the Advanced section, the same options can be specified, but - specifically for build artifacts. If enabled, build artifacts will be - discarded for any builds which exceed the defined limits. The builds - themselves will still be kept; only the associated artifacts, if any, will be - deleted. + You can also ensure that important builds are kept forever, regardless of + the setting here — click the + Keep this build forever + button on the build page. +
+ The last stable and last successful build are also excluded from these + rules. +

+ +
+ + In the + Advanced + section, the same options can be specified, but specifically for build + artifacts + . If enabled, build artifacts will be discarded for any builds which exceed + the defined limits. The builds themselves will still be kept; only the + associated artifacts, if any, will be deleted.

- For example, if a project builds some software and produces a large installer, - which is archived, you may wish to always keep the console log and information - about which source control commit was built, while for disk space reasons, you - may want to keep only the last three installers that were built. -
- This can make sense for projects where you can easily recreate the same - artifacts later by building the same source control commit again. - -

+ For example, if a project builds some software and produces a large + installer, which is archived, you may wish to always keep the console log + and information about which source control commit was built, while for disk + space reasons, you may want to keep only the last three installers that were + built. +
+ This can make sense for projects where you can easily recreate the same + artifacts later by building the same source control commit again. +

+ +
Note that Jenkins does not discard items immediately when this configuration is updated, or as soon as any of the configured values are exceeded; these diff --git a/core/src/main/resources/jenkins/model/BuildDiscarderProperty/help_bg.html b/core/src/main/resources/jenkins/model/BuildDiscarderProperty/help_bg.html index 5c689a85b9..0d91d80504 100644 --- a/core/src/main/resources/jenkins/model/BuildDiscarderProperty/help_bg.html +++ b/core/src/main/resources/jenkins/model/BuildDiscarderProperty/help_bg.html @@ -1,53 +1,68 @@
- Това определя, кога, ако изобщо някога, данните да изгражданията на този проект - ще се изтриват. Това включва изхода на конзолата, архивираните артефакти, както - и всички останали метаданни за съответното изграждане. + Това определя, кога, ако изобщо някога, данните да изгражданията на този + проект ще се изтриват. Това включва изхода на конзолата, архивираните + артефакти, както и всички останали метаданни за съответното изграждане.

- Съхраняването на по-малък брой изграждания означава, че ще се използва по-малко - дисково пространство в Build Record Root Directory, която се указва в - екрана за Системни настройки screen. + Съхраняването на по-малък брой изграждания означава, че ще се използва + по-малко дисково пространство в + Build Record Root Directory + , която се указва в екрана за + Системни настройки + screen. +

+

- - Jenkins предлага две възможности за определяне кога да се изтриват старите - изграждания: + Jenkins предлага две възможности за определяне кога да се изтриват старите + изграждания: +

+
  1. Възраст: изтриване на изгражданията след като стигнат определена възраст: примерно седем дни. -
  2. - Брой: изтриване на всички изграждания без последните няколко. +
    3. + +
  3. Брой: изтриване на всички изграждания без последните няколко.
+ Тези две възможности може да се зададат едновременно — например да се държат - изгражданията от последните 14 дни, но не повече от общо 50. Ако някое от + изгражданията от последните 14 дни, но не повече от общо 50. Ако някое от двете ограничения се надхвърли, се изтриват всички изграждания над тях.

- Можете да запазвате определени важни изграждания завинаги, независимо от - ограниченията дадени тук — натиснете бутона Запазване на изграденото - завинаги на страницата за изграждания. -
- Последното стабилно и последното успешно изграждане също се запазват, независимо - от тези ограничения. - -

- - В раздела Допълнителни могат да се указват същите тези ограничения, но - специално за артефактите от изгражданията. Ако те бъдат включени, - артефактите, надхвърлящи ограниченията, ще бъдат изтривани. Самите изграждания - и данните се пазят, само артефактите се трият. + Можете да запазвате определени важни изграждания завинаги, независимо от + ограниченията дадени тук — натиснете бутона + Запазване на изграденото завинаги + на страницата за изграждания. +
+ Последното стабилно и последното успешно изграждане също се запазват, + независимо от тези ограничения. +

+ +
+ + В раздела + Допълнителни + могат да се указват същите тези ограничения, но специално за + артефактите + от изгражданията. Ако те бъдат включени, артефактите, надхвърлящи + ограниченията, ще бъдат изтривани. Самите изграждания и данните се пазят, само + артефактите се трият.

- Например, ако проект изгражда голям инсталатор за определена програма, който - бива архивиран, а искате да запазите изхода на конзолата както и информацията - за подаването от системата за контрол на версиите, на което се базира самото - изграждане, като едновременно с това триете старите артефакти, за да не използвате - прекалено много дисково пространство. -
- Това е особено подходящо за проекти, в които лесно можете наново да изградите - артефактите наново. + Например, ако проект изгражда голям инсталатор за определена програма, който + бива архивиран, а искате да запазите изхода на конзолата както и + информацията за подаването от системата за контрол на версиите, на което се + базира самото изграждане, като едновременно с това триете старите артефакти, + за да не използвате прекалено много дисково пространство. +
+ Това е особено подходящо за проекти, в които лесно можете наново да + изградите артефактите наново. +

-
+
Забележка: Jenkins не оценя и не прилага тези правила мигновено, нито при - промяната на тези настройки, нито при надхвърлянето на ограниченията. Това + промяната на тези настройки, нито при надхвърлянето на ограниченията. Това става при завършването на изграждане на проекта.
diff --git a/core/src/main/resources/jenkins/model/BuildDiscarderProperty/help_de.html b/core/src/main/resources/jenkins/model/BuildDiscarderProperty/help_de.html index 535cbf3f2f..b39323f045 100644 --- a/core/src/main/resources/jenkins/model/BuildDiscarderProperty/help_de.html +++ b/core/src/main/resources/jenkins/model/BuildDiscarderProperty/help_de.html @@ -1,17 +1,20 @@
Steuert den Festplattenverbrauch von Jenkins, in dem verwaltet wird, wie lange - Sie Aufzeichnungen von Builds (wie z.B. die Konsolenausgabe, Buildartefakte usw.) - aufbewahrt werden. Jenkins bietet dazu zwei Strategien an: + Sie Aufzeichnungen von Builds (wie z.B. die Konsolenausgabe, Buildartefakte + usw.) aufbewahrt werden. Jenkins bietet dazu zwei Strategien an:
  1. Nach Alter. Jenkins löscht Aufzeichnungen, sobald sie ein bestimmtes Alter erreichen, z.B. 7 Tage alt sind. +
    2. +
  2. Nach Anzahl. Jenkins bewahrt nur die N neuesten Builds auf. Wenn ein neuer Build gestartet wird, löscht Jenkins den ältesten. +
Jenkins erlaubt zusätzlich, einzelne Builds mit dem Hinweis "Dieses Protokoll für immer aufbewahren" zu markieren. So können wichtige Builds von der automatischen Löschung ausgeschlossen werden. -
\ No newline at end of file + diff --git a/core/src/main/resources/jenkins/model/BuildDiscarderProperty/help_fr.html b/core/src/main/resources/jenkins/model/BuildDiscarderProperty/help_fr.html index 984be68f9d..d9a63434e7 100644 --- a/core/src/main/resources/jenkins/model/BuildDiscarderProperty/help_fr.html +++ b/core/src/main/resources/jenkins/model/BuildDiscarderProperty/help_fr.html @@ -1,21 +1,23 @@
- Contrôle la quantité d'espace disque utilisée par Jenkins en vous permettant de gérer - la durée de conservation des éléments créés par les builds (tels que la sortie - console, les artefacts des builds, etc.) - - Jenkins propose deux critères : + Contrôle la quantité d'espace disque utilisée par Jenkins en vous permettant + de gérer la durée de conservation des éléments créés par les builds (tels que + la sortie console, les artefacts des builds, etc.) Jenkins propose deux + critères :
  1. - Gestion par l'âge. Vous pouvez faire supprimer par Jenkins un élément - s'il a plus d'un certain âge (par exemple, plus de 7 jours). + Gestion par l'âge. Vous pouvez faire supprimer par Jenkins un élément s'il + a plus d'un certain âge (par exemple, plus de 7 jours). +
    2. +
  2. - Gestion par la quantité. Vous pouvez demander à Jenkins de maintenir - un maximum de N objets. Si un nouveau build est lancé, l'élément le - plus ancien sera supprimé. + Gestion par la quantité. Vous pouvez demander à Jenkins de maintenir un + maximum de N objets. Si un nouveau build est lancé, l'élément le plus + ancien sera supprimé. +
- Jenkins vous permet également de marquer un build particulier comme - 'A conserver de façon permanente', afin de vous assurer que des builds - importants ne sont pas supprimés automatiquement. - Le dernier build stable et le dernier build exécuté avec succès sont également toujours conservés. + Jenkins vous permet également de marquer un build particulier comme 'A + conserver de façon permanente', afin de vous assurer que des builds importants + ne sont pas supprimés automatiquement. Le dernier build stable et le dernier + build exécuté avec succès sont également toujours conservés.
diff --git a/core/src/main/resources/jenkins/model/BuildDiscarderProperty/help_it.html b/core/src/main/resources/jenkins/model/BuildDiscarderProperty/help_it.html index 0c8681cdc5..35a6dd2e11 100644 --- a/core/src/main/resources/jenkins/model/BuildDiscarderProperty/help_it.html +++ b/core/src/main/resources/jenkins/model/BuildDiscarderProperty/help_it.html @@ -4,54 +4,71 @@ compilazione includono l'output della console, gli artefatti archiviati e tutti gli altri metadati legati a una specifica compilazione.

- Mantenere meno compilazioni significa che verrà utilizzato meno spazio su - disco nella directory radice dei record di compilazione specificata - nella sezione Configura sistema. + Mantenere meno compilazioni significa che verrà utilizzato meno spazio su + disco nella + directory radice dei record di compilazione + specificata nella sezione + Configura sistema + . +

+

- Jenkins fornisce due modalità per determinare il momento in cui rimuovere le - compilazioni: + Jenkins fornisce due modalità per determinare il momento in cui rimuovere le + compilazioni: +

+
  1. - Età della compilazione: rimuove le compilazioni una volta che queste - hanno raggiunto una certa età; ad esempio, sette giorni. + Età della compilazione: rimuove le compilazioni una volta che queste hanno + raggiunto una certa età; ad esempio, sette giorni. +
    2. +
  2. - Numero compilazioni: rimuove la compilazione meno recente quando - esiste già un certo numero di compilazioni. + Numero compilazioni: rimuove la compilazione meno recente quando esiste + già un certo numero di compilazioni. +
- Queste due opzioni possono essere attive contemporaneamente, in modo da - poter, ad esempio, mantenere le compilazioni per 14 giorni, ma solo fino a - un limite massimo di 50 compilazioni. Se uno dei due limiti viene superato, - ogni compilazione che superi tali limiti sarà rimossa. + + Queste due opzioni possono essere attive contemporaneamente, in modo da poter, + ad esempio, mantenere le compilazioni per 14 giorni, ma solo fino a un limite + massimo di 50 compilazioni. Se uno dei due limiti viene superato, ogni + compilazione che superi tali limiti sarà rimossa.

- È possibile inoltre assicurarsi che le compilazioni importanti siano - mantenute per sempre, indipendentemente da queste impostazioni; si clicchi - sul pulsante Mantieni questa compilazione per sempre nella pagina - della compilazione. -
- Le ultime compilazioni stabile e completata con successo sono, inoltre, - escluse da queste regole. - -

- - Nella sezione Avanzate è possibile specificare le stesse opzioni, ma - in modo specifica per gli artefatti di compilazione. Se tali opzioni - sono abilitate, gli artefatti di compilazione saranno rimossi per tutte le - compilazioni che superano i limiti definiti. Le compilazioni in sé saranno - mantenute; solo gli artefatti associati saranno eliminati, se presenti. + È possibile inoltre assicurarsi che le compilazioni importanti siano + mantenute per sempre, indipendentemente da queste impostazioni; si clicchi + sul pulsante + Mantieni questa compilazione per sempre + nella pagina della compilazione. +
+ Le ultime compilazioni stabile e completata con successo sono, inoltre, + escluse da queste regole. +

+ +
+ + Nella sezione + Avanzate + è possibile specificare le stesse opzioni, ma in modo specifica per gli + artefatti + di compilazione. Se tali opzioni sono abilitate, gli artefatti di compilazione + saranno rimossi per tutte le compilazioni che superano i limiti definiti. Le + compilazioni in sé saranno mantenute; solo gli artefatti associati saranno + eliminati, se presenti.

- Ad esempio, se un progetto compila del software e produce un programma di - installazione di grandi dimensioni che viene archiviato, si potrebbe - desiderare di mantenere per sempre il log della console e le informazioni - riguardanti il commit del sistema di controllo del codice sorgente che è - stato compilato, mentre, per mantenere lo spazio su disco occupato basso, - si potrebbero voler mantenere solo gli ultimi tre programmi di installazione - creati. -
- Ciò può aver senso per i progetti per cui si possono creare nuovamente gli - stessi artefatti in un secondo momento ricompilando lo stesso commit del - sistema di controllo del codice sorgente. - -

+ Ad esempio, se un progetto compila del software e produce un programma di + installazione di grandi dimensioni che viene archiviato, si potrebbe + desiderare di mantenere per sempre il log della console e le informazioni + riguardanti il commit del sistema di controllo del codice sorgente che è + stato compilato, mentre, per mantenere lo spazio su disco occupato basso, si + potrebbero voler mantenere solo gli ultimi tre programmi di installazione + creati. +
+ Ciò può aver senso per i progetti per cui si possono creare nuovamente gli + stessi artefatti in un secondo momento ricompilando lo stesso commit del + sistema di controllo del codice sorgente. +

+ +
Si noti che Jenkins non rimuove gli elementi subito dopo l'aggiornamento di questa configurazione o non appena uno dei valori configurati venga superato; diff --git a/core/src/main/resources/jenkins/model/BuildDiscarderProperty/help_ja.html b/core/src/main/resources/jenkins/model/BuildDiscarderProperty/help_ja.html index 69d9dba87a..31f853bd9e 100644 --- a/core/src/main/resources/jenkins/model/BuildDiscarderProperty/help_ja.html +++ b/core/src/main/resources/jenkins/model/BuildDiscarderProperty/help_ja.html @@ -4,14 +4,15 @@ Jenkinsでは次の2つの条件を提供します。
    -
  1. - 期間による削除。一定の期間(例 7日間)になったら記録を削除します。 +
  2. 期間による削除。一定の期間(例 7日間)になったら記録を削除します。
    3. +
  3. 数量による削除。N個のビルドの記録のみ保持するようにします。 新規のビルドが開始したら、一番古い記録を削除します。 +
個々のビルドを、'このログをずっと保持する'としてマークすることで、 特定の重要なビルドを自動削除からはずすことができます。 最新の安定もしくは成功したビルドは常に保持します。 - \ No newline at end of file + diff --git a/core/src/main/resources/jenkins/model/BuildDiscarderProperty/help_pt_BR.html b/core/src/main/resources/jenkins/model/BuildDiscarderProperty/help_pt_BR.html index 211c3f44f7..3858a60c0c 100644 --- a/core/src/main/resources/jenkins/model/BuildDiscarderProperty/help_pt_BR.html +++ b/core/src/main/resources/jenkins/model/BuildDiscarderProperty/help_pt_BR.html @@ -1,18 +1,24 @@
- Controla o consumo de disco do Jenkins gerenciando quanto tempo você gostaria de manter - os registros das construções (tal como saída de console, artefatos de construção, e assim por diante.) - Jenkins oferece dois critérios: + Controla o consumo de disco do Jenkins gerenciando quanto tempo você + gostaria de manter os registros das construções (tal como saída + de console, artefatos de construção, e assim por diante.) Jenkins + oferece dois critérios:
  1. - Dirigio a idade. Você pode fazer o Jenkins apagar um registro se ele atingir uma certa idade - (Por exemplo, 7 dias de idade.) + Dirigio a idade. Você pode fazer o Jenkins apagar um registro se ele + atingir uma certa idade (Por exemplo, 7 dias de idade.) +
    2. +
  2. - Dirigido a número. Você pode fazer o Jenkins assegurar que ele vai manter apenas até - N registros de construção. Se uma nova construção for iniciada, o registro mais velho - será simplesmente removido. + Dirigido a número. Você pode fazer o Jenkins assegurar que ele + vai manter apenas até N registros de construção. Se uma + nova construção for iniciada, o registro mais velho será + simplesmente removido. +
- Jenkins também permite que você marque uma construção individual como 'Manter este log para sempre', - para evitar que certas construções importantes seja descartadas automaticamente. + Jenkins também permite que você marque uma construção + individual como 'Manter este log para sempre', para evitar que certas + construções importantes seja descartadas automaticamente.
diff --git a/core/src/main/resources/jenkins/model/BuildDiscarderProperty/help_ru.html b/core/src/main/resources/jenkins/model/BuildDiscarderProperty/help_ru.html index 2e1e14d855..6269074886 100644 --- a/core/src/main/resources/jenkins/model/BuildDiscarderProperty/help_ru.html +++ b/core/src/main/resources/jenkins/model/BuildDiscarderProperty/help_ru.html @@ -1,18 +1,22 @@ 
- Эта настройка управляет объемом занятого Jenkins места на диске, контролируя + Эта настройка управляет объемом занятого Jenkins места на диске, контролируя срок хранения информации о сборках (такой как логи консоли, артефакты и т.д.). Jenkins предлагает два варианта:
  1. - По возрасту. Вы можете указать Jenkins удалять сборки, достигшие определенного возраста - (например, 7 дней). + По возрасту. Вы можете указать Jenkins удалять сборки, достигшие + определенного возраста (например, 7 дней). +
    2. +
  2. - По количеству. Вы можете указать Jenkins хранить только указанное количество сборок. - Если хранится N сборок, и запускается новая, N + 1, старейшая из сборок будет - удалена. + По количеству. Вы можете указать Jenkins хранить только указанное + количество сборок. Если хранится N сборок, и запускается новая, N + 1, + старейшая из сборок будет удалена. +
- Jenkins также позволяет вам отметить какую-либо сборку на "вечное хранение", чтобы - обезопасить некоторые особо нужные вам сборки от автоматического удаления. -
\ No newline at end of file + Jenkins также позволяет вам отметить какую-либо сборку на "вечное хранение", + чтобы обезопасить некоторые особо нужные вам сборки от автоматического + удаления. + diff --git a/core/src/main/resources/jenkins/model/BuildDiscarderProperty/help_tr.html b/core/src/main/resources/jenkins/model/BuildDiscarderProperty/help_tr.html index fd68839b0f..0a3a46f5bc 100644 --- a/core/src/main/resources/jenkins/model/BuildDiscarderProperty/help_tr.html +++ b/core/src/main/resources/jenkins/model/BuildDiscarderProperty/help_tr.html @@ -1,18 +1,27 @@
- Bu kısım, yapılandırmaların kayıtlarını tutma sürelerinizi yöneterek Jenkins'in disk - kullanımını kontrol eder (konsol çıktısı, yapılandırma artefaktları gibi). -
+ Bu kısım, yapılandırmaların + kayıtlarını tutma sürelerinizi yöneterek Jenkins'in + disk kullanımını kontrol eder (konsol + çıktısı, yapılandırma artefaktları gibi). +
Jenkins bu yönetim için iki kriter sunar:
  1. - Tarih ile yönetme. Jenkins'in belli bir tarihe ulaşmış dosyaları silmesini sağlayabilirsiniz. - (mesela, 7 günlük olanlar) + Tarih ile yönetme. Jenkins'in belli bir tarihe ulaşmış + dosyaları silmesini sağlayabilirsiniz. (mesela, 7 + günlük olanlar) +
    2. +
  2. - Sayı ile yönetme. Jenkins'in N yapılandırmayı yönetmesini sağlayabilirsiniz. N sayısına ulaşıldığında, yeni bir yapılandırma, + Sayı ile yönetme. Jenkins'in N yapılandırmayı + yönetmesini sağlayabilirsiniz. N sayısına + ulaşıldığında, yeni bir yapılandırma, en eski yapılandırmanın kayıtlarını siler. +
- Ya da istediğiniz bir yapılandırmayı 'Bu logu sonsuza kadar tut' seçeneğini kullanarak - bu kuralın dışına alabilirsiniz. -
\ No newline at end of file + Ya da istediğiniz bir yapılandırmayı 'Bu logu sonsuza + kadar tut' seçeneğini kullanarak bu kuralın + dışına alabilirsiniz. + diff --git a/core/src/main/resources/jenkins/model/BuildDiscarderProperty/help_zh_TW.html b/core/src/main/resources/jenkins/model/BuildDiscarderProperty/help_zh_TW.html index e985c65aa1..160b2f1a80 100644 --- a/core/src/main/resources/jenkins/model/BuildDiscarderProperty/help_zh_TW.html +++ b/core/src/main/resources/jenkins/model/BuildDiscarderProperty/help_zh_TW.html @@ -1,12 +1,16 @@
- 管理要保留的建置記錄 (包含畫面輸出、建置成品等) 數，控制 Jenkins 的磁碟使用量。 - Jenkins 提供兩種準則: + 管理要保留的建置記錄 (包含畫面輸出、建置成品等) 數，控制 Jenkins + 的磁碟使用量。 Jenkins 提供兩種準則:
  1. 依新舊狀況處理。您可以要 Jenkins 刪除指定時間 (例如 7 天) 前的記錄。 +
    2. +
  2. - 依次數處理。您可以讓 Jenkins 只保留最近的 N 筆建置記錄。如果開始新的建置後，最早的記錄就會被刪掉。 + 依次數處理。您可以讓 Jenkins 只保留最近的 N + 筆建置記錄。如果開始新的建置後，最早的記錄就會被刪掉。 +
Jenkins 也允許您將某些建置標為「永久保存」，讓特定幾次重要建置不會被自動刪除。 diff --git a/core/src/main/resources/jenkins/model/GlobalQuietPeriodConfiguration/help-quietPeriod.html b/core/src/main/resources/jenkins/model/GlobalQuietPeriodConfiguration/help-quietPeriod.html index 41b656bb2c..1ce73100db 100644 --- a/core/src/main/resources/jenkins/model/GlobalQuietPeriodConfiguration/help-quietPeriod.html +++ b/core/src/main/resources/jenkins/model/GlobalQuietPeriodConfiguration/help-quietPeriod.html @@ -1,20 +1,23 @@
When this option is non-zero, newly triggered builds of this project will be - added to the queue, but Jenkins will wait for the specified period of time - (in seconds) before actually starting the build. + added to the queue, but Jenkins will wait for the specified period of time (in + seconds) before actually starting the build.

- For example, if your builds take a long time to execute, you may want to - prevent multiple source control commits that are made at approximately the - same time from triggering multiple builds. Enabling the quiet period would - prevent a build from being started as soon as Jenkins discovers the first - commit; this would give the developer the chance to push more commits which - would be included in the build when it starts. This reduces the size of the - queue, meaning that developers would get feedback faster for their series of - commits, and the load on the Jenkins system would be reduced. + For example, if your builds take a long time to execute, you may want to + prevent multiple source control commits that are made at approximately the + same time from triggering multiple builds. Enabling the quiet period would + prevent a build from being started as soon as Jenkins discovers the first + commit; this would give the developer the chance to push more commits which + would be included in the build when it starts. This reduces the size of the + queue, meaning that developers would get feedback faster for their series of + commits, and the load on the Jenkins system would be reduced. +

+

- If a new build of this project is triggered while a build is already sitting - in the queue, waiting for its quiet period to end, the quiet period will not - be reset. The newly triggered build will not be added to the queue, unless - this project is parameterized and the build has different parameters than the - build already in the queue. + If a new build of this project is triggered while a build is already sitting + in the queue, waiting for its quiet period to end, the quiet period will not + be reset. The newly triggered build will not be added to the queue, unless + this project is parameterized and the build has different parameters than + the build already in the queue. +

diff --git a/core/src/main/resources/jenkins/model/GlobalQuietPeriodConfiguration/help-quietPeriod_bg.html b/core/src/main/resources/jenkins/model/GlobalQuietPeriodConfiguration/help-quietPeriod_bg.html index c39432db11..bd3b2a6b4c 100644 --- a/core/src/main/resources/jenkins/model/GlobalQuietPeriodConfiguration/help-quietPeriod_bg.html +++ b/core/src/main/resources/jenkins/model/GlobalQuietPeriodConfiguration/help-quietPeriod_bg.html @@ -1,22 +1,28 @@
- Когато това е избрано, изгражданията, които са стартирани автоматично, ще - се добавят в опашката за изпълнение, но Jenkins ще изчаква определено време, + Когато това е избрано, изгражданията, които са стартирани автоматично, ще се + добавят в опашката за изпълнение, но Jenkins ще изчаква определено време, преди действително да стартира изграждането.

- Например, ако изгражданията отнемат много време, може да искате да - предотвратите стартирането на няколко изграждания от множество подавания в - системата за контрол на версиите, който са направени по едно и също време. - Задаването на период за изчакване ще предотврати стартирането на изграждане, - когато усети първото подаване. Това дава възможност да се съберат повече - подавания за включване в изграждането. Това намалява дължината на опашката - за изграждане, намалява натоварването върху Jenkins и като резултат - разработчиците получават по бързо обратна връзка за серията от подавания. + Например, ако изгражданията отнемат много време, може да искате да + предотвратите стартирането на няколко изграждания от множество подавания в + системата за контрол на версиите, който са направени по едно и също време. + Задаването на период за изчакване ще предотврати стартирането на изграждане, + когато усети първото подаване. Това дава възможност да се съберат повече + подавания за включване в изграждането. Това намалява дължината на опашката + за изграждане, намалява натоварването върху Jenkins и като резултат + разработчиците получават по бързо обратна връзка за серията от подавания. +

+

- Ако се получи заявка за ново изграждане, докато има изчакващо в опашката, - периодът му за чакане няма да се промени, а заявката няма да доведе до - ново изграждане, освен, ако изграждането е параметризирано и стойностите - на параметрите са различни от тези на изграждането в опашката. + Ако се получи заявка за ново изграждане, докато има изчакващо в опашката, + периодът му за чакане няма да се промени, а заявката няма да доведе до ново + изграждане, освен, ако изграждането е параметризирано и стойностите на + параметрите са различни от тези на изграждането в опашката. +

+

- Ако това не е избрано, се използва стандартната стойност, която е зададена - в Настройки на системата. -

+ Ако това не е избрано, се използва стандартната стойност, която е зададена в + Настройки на системата + . +

+
diff --git a/core/src/main/resources/jenkins/model/GlobalQuietPeriodConfiguration/help-quietPeriod_de.html b/core/src/main/resources/jenkins/model/GlobalQuietPeriodConfiguration/help-quietPeriod_de.html index 2d9143797d..fd34d8f061 100644 --- a/core/src/main/resources/jenkins/model/GlobalQuietPeriodConfiguration/help-quietPeriod_de.html +++ b/core/src/main/resources/jenkins/model/GlobalQuietPeriodConfiguration/help-quietPeriod_de.html @@ -3,21 +3,21 @@ Sekunden, bevor der eigentliche Build-Prozess startet. Dies ist nützlich wenn:
  • - Mehrere E-Mails zur Benachrichtigung über Änderungen im CVS zusammengefasst - werden sollen. Manche Skripte zur automatischen Erstellung von Änderungsprotokollen - erzeugen mehrere E-Mails in schneller Folge, wenn sich Änderungen über - mehrere Verzeichnisse erstrecken. + Mehrere E-Mails zur Benachrichtigung über Änderungen im CVS + zusammengefasst werden sollen. Manche Skripte zur automatischen Erstellung + von Änderungsprotokollen erzeugen mehrere E-Mails in schneller Folge, wenn + sich Änderungen über mehrere Verzeichnisse erstrecken.
  • Ihr Programmierstil es erfordert, eine logische Änderung in mehreren CVS/SVN-Operationen durchzuführen. Eine verlängerte Ruheperiode verhindert - in diesem Falle, dass Jenkins einen Build verfrüht startet und einen Fehlschlag - meldet. + in diesem Falle, dass Jenkins einen Build verfrüht startet und einen + Fehlschlag meldet.
  • - Builds begrenzt werden sollen. Wenn Ihre Jenkins-Installation mit zu vielen - Builds überlastet wird, kann eine verlängerte Ruheperiode die Anzahl der - Builds verringern. + Builds begrenzt werden sollen. Wenn Ihre Jenkins-Installation mit zu + vielen Builds überlastet wird, kann eine verlängerte Ruheperiode die + Anzahl der Builds verringern.
Ein systemweiter Vorgabewert wird verwendet, wenn nicht auf Projektebene ein diff --git a/core/src/main/resources/jenkins/model/GlobalQuietPeriodConfiguration/help-quietPeriod_fr.html b/core/src/main/resources/jenkins/model/GlobalQuietPeriodConfiguration/help-quietPeriod_fr.html index 222e4d3730..cb89262467 100644 --- a/core/src/main/resources/jenkins/model/GlobalQuietPeriodConfiguration/help-quietPeriod_fr.html +++ b/core/src/main/resources/jenkins/model/GlobalQuietPeriodConfiguration/help-quietPeriod_fr.html @@ -1,27 +1,25 @@ 
- Si cette option est activée, un build attendra le nombre de secondes - indiqué avant de réellement s'exécuter. - Cela est utile pour : + Si cette option est activée, un build attendra le nombre de secondes indiqué + avant de réellement s'exécuter. Cela est utile pour :
  • - Agréger de multiples emails de notification de changements CVS dans - un seul (certains scripts de génération d'email relatif aux - changements dans CVS génèrent de nombreux messages en rafale, - lorsqu'un commit concerne plusieurs répertoires). + Agréger de multiples emails de notification de changements CVS dans un + seul (certains scripts de génération d'email relatif aux changements dans + CVS génèrent de nombreux messages en rafale, lorsqu'un commit concerne + plusieurs répertoires).
  • Selon vos habitudes de codage, vous introduisez peut-être une erreur de logique dans certaines opérations cvs/svn. Dans ce cas, une période - d'attente plus longue évitera que Jenkins lance un build - prématurement et indique un échec. + d'attente plus longue évitera que Jenkins lance un build prématurement et + indique un échec.
  • - La gestion des ressources. Si votre installation de Jenkins est - surchargée par de nombreux builds, une période d'attente plus longue - pourra réduire ce nombre. + La gestion des ressources. Si votre installation de Jenkins est surchargée + par de nombreux builds, une période d'attente plus longue pourra réduire + ce nombre.
- Si cette valeur n'est pas positionnée explicitement au niveau du projet, - une valeur par défaut pour toute l'installation de Jenkins sera - utilisée. -
\ No newline at end of file + Si cette valeur n'est pas positionnée explicitement au niveau du projet, une + valeur par défaut pour toute l'installation de Jenkins sera utilisée. + diff --git a/core/src/main/resources/jenkins/model/GlobalQuietPeriodConfiguration/help-quietPeriod_it.html b/core/src/main/resources/jenkins/model/GlobalQuietPeriodConfiguration/help-quietPeriod_it.html index 6880eb02f2..795e7d5ed4 100644 --- a/core/src/main/resources/jenkins/model/GlobalQuietPeriodConfiguration/help-quietPeriod_it.html +++ b/core/src/main/resources/jenkins/model/GlobalQuietPeriodConfiguration/help-quietPeriod_it.html @@ -1,24 +1,27 @@
Quando quest'opzione è impostata a un valore diverso da zero, le nuove compilazioni di questo progetto saranno aggiunte alla coda, ma Jenkins - attenderà per il periodo di tempo specificato (in secondi) prima di avviare - la compilazione. + attenderà per il periodo di tempo specificato (in secondi) prima di avviare la + compilazione.

- Ad esempio, se le compilazioni richiedono molto tempo per essere eseguite, - si potrebbe voler far sì che più commit nel sistema di gestione del codice - sorgente, eseguiti più o meno nello stesso momento, scatenino più - compilazioni. L'abilitazione del periodo di quiete farebbe sì che una - compilazione non parta nel momento in cui Jenkins rileva il primo commit; - ciò darebbe allo sviluppatore la possibilità di eseguire il push di più - commit, che sarebbero inclusi nella compilazione al suo avvio. Ciò diminuisce - le dimensioni della coda, il che significa che gli sviluppatori otterrebbero - un feedback più velocemente per le loro serie di commit, e il carico di - lavoro su Jenkins sarebbe ridotto. + Ad esempio, se le compilazioni richiedono molto tempo per essere eseguite, + si potrebbe voler far sì che più commit nel sistema di gestione del codice + sorgente, eseguiti più o meno nello stesso momento, scatenino più + compilazioni. L'abilitazione del periodo di quiete farebbe sì che una + compilazione non parta nel momento in cui Jenkins rileva il primo commit; + ciò darebbe allo sviluppatore la possibilità di eseguire il push di più + commit, che sarebbero inclusi nella compilazione al suo avvio. Ciò + diminuisce le dimensioni della coda, il che significa che gli sviluppatori + otterrebbero un feedback più velocemente per le loro serie di commit, e il + carico di lavoro su Jenkins sarebbe ridotto. +

+

- Se viene scatenata una nuova compilazione di questo progetto finché una - compilazione è già in coda e in attesa che il suo periodo di quiete finisca, - il periodo di quiete non sarà reimpostato. La nuova compilazione scatenata - non sarà aggiunta alla coda, a meno che questo progetto non sia - parametrizzato e che la compilazione abbia dei parametri differenti da - quelli della compilazione già in coda. + Se viene scatenata una nuova compilazione di questo progetto finché una + compilazione è già in coda e in attesa che il suo periodo di quiete finisca, + il periodo di quiete non sarà reimpostato. La nuova compilazione scatenata + non sarà aggiunta alla coda, a meno che questo progetto non sia + parametrizzato e che la compilazione abbia dei parametri differenti da + quelli della compilazione già in coda. +

diff --git a/core/src/main/resources/jenkins/model/GlobalQuietPeriodConfiguration/help-quietPeriod_ja.html b/core/src/main/resources/jenkins/model/GlobalQuietPeriodConfiguration/help-quietPeriod_ja.html index 922af836c4..83cc4540c4 100644 --- a/core/src/main/resources/jenkins/model/GlobalQuietPeriodConfiguration/help-quietPeriod_ja.html +++ b/core/src/main/resources/jenkins/model/GlobalQuietPeriodConfiguration/help-quietPeriod_ja.html @@ -15,4 +15,4 @@ プロジェクトで設定されていなければ、システム全体でのデフォルト値を使用します。 - \ No newline at end of file + diff --git a/core/src/main/resources/jenkins/model/GlobalQuietPeriodConfiguration/help-quietPeriod_pt_BR.html b/core/src/main/resources/jenkins/model/GlobalQuietPeriodConfiguration/help-quietPeriod_pt_BR.html index 2bfc9c59a1..5d5ae4061e 100644 --- a/core/src/main/resources/jenkins/model/GlobalQuietPeriodConfiguration/help-quietPeriod_pt_BR.html +++ b/core/src/main/resources/jenkins/model/GlobalQuietPeriodConfiguration/help-quietPeriod_pt_BR.html @@ -1,22 +1,27 @@
- Se informado, uma nova construção agendada aguarda estes quantos segundos informado - antes de ser realmente construída. - Isto é útil para: + Se informado, uma nova construção agendada aguarda estes quantos + segundos informado antes de ser realmente construída. Isto é + útil para:
  • - Juntar múltiplos e-mails de notificação de mudanças no CVS em um (alguns scripts - de geração de e-mail de mudança no log de CVS geram múltiplos e-mails - em uma rápida sequência quam uma submissão atravessa pelos diretórios). + Juntar múltiplos e-mails de notificação de mudanças no + CVS em um (alguns scripts de geração de e-mail de mudança + no log de CVS geram múltiplos e-mails em uma rápida + sequência quam uma submissão atravessa pelos diretórios).
  • - Se seu estilo de codificação é tal que você submete uma mudança lógica em poucas - operação de cvs/svn, então informar um longo período de silêncio previniria o Jenkins de - construí-lo prematuramente e relatar uma falha. + Se seu estilo de codificação é tal que você submete + uma mudança lógica em poucas operação de cvs/svn, + então informar um longo período de silêncio previniria o + Jenkins de construí-lo prematuramente e relatar uma falha.
  • - Suprimir construções. Se sua intalação do Jenkins está muito ocupada com muitas construçõesi, - informar um longo período de silêncio pode reduzir o número de construções. + Suprimir construções. Se sua intalação do Jenkins + está muito ocupada com muitas construçõesi, informar um + longo período de silêncio pode reduzir o número de + construções.
- Se não explícitamente informado no nível de projeto, o valor padrão do sistema todo é usado. + Se não explícitamente informado no nível de projeto, o valor + padrão do sistema todo é usado.
diff --git a/core/src/main/resources/jenkins/model/GlobalQuietPeriodConfiguration/help-quietPeriod_ru.html b/core/src/main/resources/jenkins/model/GlobalQuietPeriodConfiguration/help-quietPeriod_ru.html index dc5f9b993d..eb5231925c 100644 --- a/core/src/main/resources/jenkins/model/GlobalQuietPeriodConfiguration/help-quietPeriod_ru.html +++ b/core/src/main/resources/jenkins/model/GlobalQuietPeriodConfiguration/help-quietPeriod_ru.html @@ -1,24 +1,24 @@ 
- Если указано ненулевое значение, инициированная сборка выдерживает паузу в указанное - количество секунд перед запуском сборочной команды. - Это бывает полезно в следующих случаях: + Если указано ненулевое значение, инициированная сборка выдерживает паузу в + указанное количество секунд перед запуском сборочной команды. Это бывает + полезно в следующих случаях:
  • - Объединение нескольких уведомлений от CVS в одно (некоторые скрипты уведомлений - создают несколько сообщений в том случае когда фиксирование (commit) происходит - в несколько директорий). + Объединение нескольких уведомлений от CVS в одно (некоторые скрипты + уведомлений создают несколько сообщений в том случае когда фиксирование + (commit) происходит в несколько директорий).
  • - Если ваш стиль разработки таков что вы фиксируете логически единое изменение кода - в несколько шагов, установка более долгого периода ожидания предотвратит - немедленный запуск обреченной на неудачу сборки. + Если ваш стиль разработки таков что вы фиксируете логически единое + изменение кода в несколько шагов, установка более долгого периода ожидания + предотвратит немедленный запуск обреченной на неудачу сборки.
  • - Объединение сборок. Если ваш Jenkins перегружен большим количеством сборок, - увеличьте период для поглощения излишне часто возникающих триггеров, - инициирующих сборки. + Объединение сборок. Если ваш Jenkins перегружен большим количеством + сборок, увеличьте период для поглощения излишне часто возникающих + триггеров, инициирующих сборки.
- Если явно не указан в настройках проекта, используется значение из глобальных + Если явно не указан в настройках проекта, используется значение из глобальных настроек Jenkins. -
\ No newline at end of file + diff --git a/core/src/main/resources/jenkins/model/GlobalQuietPeriodConfiguration/help-quietPeriod_tr.html b/core/src/main/resources/jenkins/model/GlobalQuietPeriodConfiguration/help-quietPeriod_tr.html index e124b298b6..55f0fe9d30 100644 --- a/core/src/main/resources/jenkins/model/GlobalQuietPeriodConfiguration/help-quietPeriod_tr.html +++ b/core/src/main/resources/jenkins/model/GlobalQuietPeriodConfiguration/help-quietPeriod_tr.html @@ -1,21 +1,27 @@
- Eğer ayarlanırsa, planlanan yapılandırma başlamadan önce belirlenen saniye kadar bekler. - Bu aşağıdaki durumlarda faydalıdır: -
-
    + Eğer ayarlanırsa, planlanan yapılandırma başlamadan + önce belirlenen saniye kadar bekler. Bu aşağıdaki + durumlarda faydalıdır: +
    +
    • - Birden fazla CVS değişikliğinin tek bir maile indirilmesinde (some CVS changelog - e-mail generation scripts generate multiple e-mails in quick succession when - a commit spans across directories). + Birden fazla CVS değişikliğinin tek bir maile + indirilmesinde (some CVS changelog e-mail generation scripts generate + multiple e-mails in quick succession when a commit spans across + directories).
    • - Eğer sürüm işlemi birden fazla CVS/SVN operasyonu gerektiriyorsa, sessiz periyot - süresini artırarak hatalı oluşabilecek yapılandırmaları engeller. + Eğer sürüm işlemi birden fazla CVS/SVN operasyonu + gerektiriyorsa, sessiz periyot süresini artırarak hatalı + oluşabilecek yapılandırmaları engeller.
    • - Eğer Jenkins, çok fazla yapılandırma ile uğraşıyorsa, sessiz periyodu uzatmak, - Jenkins'i yükünü ve yapılandırma sayısını azaltacaktır. + Eğer Jenkins, çok fazla yapılandırma ile + uğraşıyorsa, sessiz periyodu uzatmak, Jenkins'i + yükünü ve yapılandırma sayısını + azaltacaktır.
    - Proje-seviyesinde belirlenmez ise, sistemdeki varolan değer alınır. -
\ No newline at end of file + Proje-seviyesinde belirlenmez ise, sistemdeki varolan değer + alınır. + diff --git a/core/src/main/resources/jenkins/model/GlobalQuietPeriodConfiguration/help-quietPeriod_zh_TW.html b/core/src/main/resources/jenkins/model/GlobalQuietPeriodConfiguration/help-quietPeriod_zh_TW.html index e5544e9077..e59af079b2 100644 --- a/core/src/main/resources/jenkins/model/GlobalQuietPeriodConfiguration/help-quietPeriod_zh_TW.html +++ b/core/src/main/resources/jenkins/model/GlobalQuietPeriodConfiguration/help-quietPeriod_zh_TW.html @@ -1,16 +1,18 @@
- 設定後，新排進來的建置會等到指定的秒數過後才會真正開始執行。 - 用途有: + 設定後，新排進來的建置會等到指定的秒數過後才會真正開始執行。 用途有:
  • - 把多次 CVS 變更收斂成一個 (某些產生 CVS 變更記錄郵件的 Script 在跨目錄 Commit 時會連續發送信件)。 + 把多次 CVS 變更收斂成一個 (某些產生 CVS 變更記錄郵件的 Script 在跨目錄 + Commit 時會連續發送信件)。
  • - 如果您的開發風格是將不同邏輯單元的變更分次 Commit，靜候時間設長一點可以避免 Jenkins 因為太早建置而回報錯誤。 + 如果您的開發風格是將不同邏輯單元的變更分次 + Commit，靜候時間設長一點可以避免 Jenkins 因為太早建置而回報錯誤。
  • - 調節建置。如果您的 Jeknins 建置太多，一直忙不過來。靜候時間設長一點可以減少建置次數。 + 調節建置。如果您的 Jeknins + 建置太多，一直忙不過來。靜候時間設長一點可以減少建置次數。
如果沒有在專案中明確設定，就會用這個全系統預設值。 -
\ No newline at end of file + diff --git a/core/src/main/resources/jenkins/model/Jenkins/help-markupFormatter.html b/core/src/main/resources/jenkins/model/Jenkins/help-markupFormatter.html index 12621e2aa0..6f1cde576f 100644 --- a/core/src/main/resources/jenkins/model/Jenkins/help-markupFormatter.html +++ b/core/src/main/resources/jenkins/model/Jenkins/help-markupFormatter.html @@ -1,13 +1,17 @@
- In such places as project description, user description, view description, and build description, - Jenkins allows users to enter some free-form text that describes something. + In such places as project description, user description, view description, and + build description, Jenkins allows users to enter some free-form text that + describes something. This configuration determines how such free-form text is + converted to HTML. By default, Jenkins treats the text as HTML and use it + as-is unmodified (and this is default mainly because of the backward + compatibility.) - This configuration determines how such free-form text is converted to HTML. By default, Jenkins treats - the text as HTML and use it as-is unmodified (and this is default mainly because of the backward compatibility.) - -

- While this is convenient and people often use it to load <iframe>, <script>. and so on to - mash up data from other sources, this capability enables malicious users to mount - XSS attacks. - If the risk outweighs the benefit, install additional markup formatter plugins and use them. +

+ While this is convenient and people often use it to load <iframe>, + <script>. and so on to mash up data from other sources, this capability + enables malicious users to mount + XSS attacks + . If the risk outweighs the benefit, install additional markup formatter + plugins and use them. +

diff --git a/core/src/main/resources/jenkins/model/Jenkins/help-markupFormatter_bg.html b/core/src/main/resources/jenkins/model/Jenkins/help-markupFormatter_bg.html index e0cd7e418e..11956b33ba 100644 --- a/core/src/main/resources/jenkins/model/Jenkins/help-markupFormatter_bg.html +++ b/core/src/main/resources/jenkins/model/Jenkins/help-markupFormatter_bg.html @@ -1,16 +1,15 @@
- На места като описанията на проект, потребител, изглед или изграждане, - Jenkins ви позволява да въведете свободен, описателен текст. + На места като описанията на проект, потребител, изглед или изграждане, Jenkins + ви позволява да въведете свободен, описателен текст. Тази настройка определя + как този свободен текст се преобразува до HTML. Стандартно счита текста за + HTML и го ползва както е (това поведение е за съвместимост с предишни версии). - Тази настройка определя как този свободен текст се преобразува до HTML. - Стандартно счита текста за HTML и го ползва както е (това поведение е за - съвместимост с предишни версии). - -

+

Това е доста удобно и хората го ползват, за да зареждат <iframe>, <script> и т.н., това позволява на недобронамерените потребители да - извършат атаки чрез - XSS. - Ако рискът е прекомерно голям, инсталирайте допълнителна приставка за + извършат атаки чрез + XSS + . Ако рискът е прекомерно голям, инсталирайте допълнителна приставка за форматиране на текста и ползвайте нея. +

diff --git a/core/src/main/resources/jenkins/model/Jenkins/help-markupFormatter_it.html b/core/src/main/resources/jenkins/model/Jenkins/help-markupFormatter_it.html index 0447e9fada..031b6aded0 100644 --- a/core/src/main/resources/jenkins/model/Jenkins/help-markupFormatter_it.html +++ b/core/src/main/resources/jenkins/model/Jenkins/help-markupFormatter_it.html @@ -1,18 +1,19 @@
Jenkins, in campi come la descrizione di un progetto, di un utente, di una vista e di una compilazione, consente agli utenti di immettere del testo - libero che descriva qualcosa. - - Questa configurazione determina la modalità in cui tale testo libero viene - convertito in HTML. Per impostazione predefinita, Jenkins tratta il testo - come HTML e lo utilizza senza modifiche (questa è l'impostazione predefinita - principalmente per motivi di retrocompatibilità). + libero che descriva qualcosa. Questa configurazione determina la modalità in + cui tale testo libero viene convertito in HTML. Per impostazione predefinita, + Jenkins tratta il testo come HTML e lo utilizza senza modifiche (questa è + l'impostazione predefinita principalmente per motivi di retrocompatibilità).

- Quest'opzione è comoda e gli utenti spesso la utilizzano per caricare - <iframe>, <script> e altri tag per combinare dati da più sorgenti, ma - consente a utenti malevoli di portare a termine - attacchi XSS. - Se i rischi superano i benefici, si installino componenti aggiuntivi per la - formattazione del markup e li si usino. + Quest'opzione è comoda e gli utenti spesso la utilizzano per caricare + <iframe>, <script> e altri tag per combinare dati da più sorgenti, ma + consente a utenti malevoli di portare a termine + + attacchi XSS + + . Se i rischi superano i benefici, si installino componenti aggiuntivi per + la formattazione del markup e li si usino. +

diff --git a/core/src/main/resources/jenkins/model/Jenkins/help-markupFormatter_ja.html b/core/src/main/resources/jenkins/model/Jenkins/help-markupFormatter_ja.html index 8eca80f761..40ee45eecf 100644 --- a/core/src/main/resources/jenkins/model/Jenkins/help-markupFormatter_ja.html +++ b/core/src/main/resources/jenkins/model/Jenkins/help-markupFormatter_ja.html @@ -1,12 +1,18 @@
- プロジェクト、ユーザー、ビューそしてビルドの説明などのような入力箇所では、フリーフォーマットのテキストを入力することができます。 + プロジェクト、ユーザー、ビューそしてビルドの説明などのような入力箇所では、フリーフォーマットのテキストを入力することができます。 + この設定で、そのフリーフォーマットのテキストをどのようにHTMLに変換するかを決定します。 + デフォルトでは、テキストをHTMLとして扱い、変更することなくそのまま使用します(主に後方互換のためです)。 - この設定で、そのフリーフォーマットのテキストをどのようにHTMLに変換するかを決定します。 - デフォルトでは、テキストをHTMLとして扱い、変更することなくそのまま使用します(主に後方互換のためです)。 - -

- これはとても便利なので、<iframe>, <script>をロードするために、また他のソースからのデータを取り込むためによく使用しますが、 - 悪意のあるユーザーがクロスサイトスクリプティング +

+ これはとても便利なので、<iframe>, + <script>をロードするために、また他のソースからのデータを取り込むためによく使用しますが、 + 悪意のあるユーザーが + + クロスサイトスクリプティング + をしかけることを容易にしてしまいます。 便利さより危険性を重視するなら、他のフォーマッタープラグインをインストールして使用してください。 +

diff --git a/core/src/main/resources/jenkins/model/Jenkins/help-markupFormatter_zh_TW.html b/core/src/main/resources/jenkins/model/Jenkins/help-markupFormatter_zh_TW.html index 8753cb6fb4..6a737ac54f 100644 --- a/core/src/main/resources/jenkins/model/Jenkins/help-markupFormatter_zh_TW.html +++ b/core/src/main/resources/jenkins/model/Jenkins/help-markupFormatter_zh_TW.html @@ -1,12 +1,17 @@
- Jenkins 可以讓您自由輸入描述文字在專案說明、使用者說明、視景說明及建置說明...這些地方。 + Jenkins + 可以讓您自由輸入描述文字在專案說明、使用者說明、視景說明及建置說明...這些地方。 + 這個設定決定怎麼把您輸入的文字轉換成 HTML。Jenkins 預設把這些文字當做 HTML + 直接拿來顯示 (這個預設值主要是為了跟舊版相容)。 - 這個設定決定怎麼把您輸入的文字轉換成 HTML。Jenkins 預設把這些文字當做 HTML 直接拿來顯示 - (這個預設值主要是為了跟舊版相容)。 - -

+

這樣很方便，大家常用來載入 <iframe> 或 <script>，整合其他來源的資料。 但是也有可能被惡意使用者掛上 - XSS 攻擊。 - 如果您評估的風險大過好處，請另外安裝使用標記格式外掛程式。 + + XSS 攻擊 + + 。 如果您評估的風險大過好處，請另外安裝使用標記格式外掛程式。 +

diff --git a/core/src/main/resources/jenkins/model/JenkinsLocationConfiguration/help-adminAddress.html b/core/src/main/resources/jenkins/model/JenkinsLocationConfiguration/help-adminAddress.html index 99444f8bfa..3e29c51f95 100644 --- a/core/src/main/resources/jenkins/model/JenkinsLocationConfiguration/help-adminAddress.html +++ b/core/src/main/resources/jenkins/model/JenkinsLocationConfiguration/help-adminAddress.html @@ -1,5 +1,5 @@
- Notification e-mails from Jenkins to project owners will be sent - with this address in the from header. This can be just - "foo@acme.org" or it could be something like "Jenkins Daemon <foo@acme.org>" + Notification e-mails from Jenkins to project owners will be sent with this + address in the from header. This can be just "foo@acme.org" or it could be + something like "Jenkins Daemon <foo@acme.org>"
diff --git a/core/src/main/resources/jenkins/model/JenkinsLocationConfiguration/help-adminAddress_bg.html b/core/src/main/resources/jenkins/model/JenkinsLocationConfiguration/help-adminAddress_bg.html index 0d1a14d59a..9a9081a133 100644 --- a/core/src/main/resources/jenkins/model/JenkinsLocationConfiguration/help-adminAddress_bg.html +++ b/core/src/main/resources/jenkins/model/JenkinsLocationConfiguration/help-adminAddress_bg.html @@ -1,5 +1,5 @@
- Известията по е-поща от Jenkins към собствениците на проекти ще се - изпращат с този адрес на подател. Може да е само адрес като: - „jenkins@acme.org“ или „Сървър Jenkins <jenkins@acme.org>“. + Известията по е-поща от Jenkins към собствениците на проекти ще се изпращат с + този адрес на подател. Може да е само адрес като: „jenkins@acme.org“ или + „Сървър Jenkins <jenkins@acme.org>“.
diff --git a/core/src/main/resources/jenkins/model/JenkinsLocationConfiguration/help-adminAddress_de.html b/core/src/main/resources/jenkins/model/JenkinsLocationConfiguration/help-adminAddress_de.html index 50fe2009f0..d2a3ebcc60 100644 --- a/core/src/main/resources/jenkins/model/JenkinsLocationConfiguration/help-adminAddress_de.html +++ b/core/src/main/resources/jenkins/model/JenkinsLocationConfiguration/help-adminAddress_de.html @@ -1,7 +1,8 @@
- Jenkins schickt E-Mail-Benachrichtigungen an Projekteigner unter dieser Adresse - im "From"-Header. + Jenkins schickt E-Mail-Benachrichtigungen an Projekteigner unter dieser + Adresse im "From"-Header.

- Sie können einfach nur "foo@acme.org" angeben, aber auch etwas in - der Richtung wie "Jenkins Daemon <foo@acme.org>" + Sie können einfach nur "foo@acme.org" angeben, aber auch etwas in der + Richtung wie "Jenkins Daemon <foo@acme.org>" +

diff --git a/core/src/main/resources/jenkins/model/JenkinsLocationConfiguration/help-adminAddress_fr.html b/core/src/main/resources/jenkins/model/JenkinsLocationConfiguration/help-adminAddress_fr.html index 2ca7e654c1..81aef0955f 100644 --- a/core/src/main/resources/jenkins/model/JenkinsLocationConfiguration/help-adminAddress_fr.html +++ b/core/src/main/resources/jenkins/model/JenkinsLocationConfiguration/help-adminAddress_fr.html @@ -1,6 +1,6 @@ 
- Les emails de notification envoyés par Jenkins aux propriétaires des - projets seront envoyés avec cette adresse dans le champ expéditeur. - Cela peut être simplement "foo@acme.org" ou quelque chose comme - "Jenkins Daemon <foo@acme.org>" + Les emails de notification envoyés par Jenkins aux propriétaires des projets + seront envoyés avec cette adresse dans le champ expéditeur. Cela peut être + simplement "foo@acme.org" ou quelque chose comme "Jenkins Daemon + <foo@acme.org>"
diff --git a/core/src/main/resources/jenkins/model/JenkinsLocationConfiguration/help-adminAddress_it.html b/core/src/main/resources/jenkins/model/JenkinsLocationConfiguration/help-adminAddress_it.html index 404d25b189..a4483e18c1 100644 --- a/core/src/main/resources/jenkins/model/JenkinsLocationConfiguration/help-adminAddress_it.html +++ b/core/src/main/resources/jenkins/model/JenkinsLocationConfiguration/help-adminAddress_it.html @@ -1,6 +1,6 @@
I messaggi di posta elettronica di notifica inviati da Jenkins ai proprietari - dei progetti saranno inviati con quest'indirizzo nell'intestazione "Da". - Può essere semplicemente "pippo@pluto.org" o qualcosa del tipo "Demone - Jenkins <pippo@pluto.org>" + dei progetti saranno inviati con quest'indirizzo nell'intestazione "Da". Può + essere semplicemente "pippo@pluto.org" o qualcosa del tipo "Demone Jenkins + <pippo@pluto.org>"
diff --git a/core/src/main/resources/jenkins/model/JenkinsLocationConfiguration/help-adminAddress_ja.html b/core/src/main/resources/jenkins/model/JenkinsLocationConfiguration/help-adminAddress_ja.html index 3a2157c174..f076f8d271 100644 --- a/core/src/main/resources/jenkins/model/JenkinsLocationConfiguration/help-adminAddress_ja.html +++ b/core/src/main/resources/jenkins/model/JenkinsLocationConfiguration/help-adminAddress_ja.html @@ -1,4 +1,5 @@
- Jenkinsからプロジェクト管理者へのE-mail通知は、Fromヘッダにこのアドレスを設定して送信されます。
+ Jenkinsからプロジェクト管理者へのE-mail通知は、Fromヘッダにこのアドレスを設定して送信されます。 +
"foo@acme.org"や、"Jenkins Daemon <foo@acme.org>"のような形式で設定します。
diff --git a/core/src/main/resources/jenkins/model/JenkinsLocationConfiguration/help-adminAddress_nl.html b/core/src/main/resources/jenkins/model/JenkinsLocationConfiguration/help-adminAddress_nl.html index b11b281f8e..ded1befcd1 100644 --- a/core/src/main/resources/jenkins/model/JenkinsLocationConfiguration/help-adminAddress_nl.html +++ b/core/src/main/resources/jenkins/model/JenkinsLocationConfiguration/help-adminAddress_nl.html @@ -1,4 +1,5 @@
Notificatie e-mails van Jenkins zullen met dit "van" adres verstuurd worden. - Dit kan gewoon "foo@acme.org" of zelfs "Jenkins Daemon <foo@acme.org>" zijn. + Dit kan gewoon "foo@acme.org" of zelfs "Jenkins Daemon <foo@acme.org>" + zijn.
diff --git a/core/src/main/resources/jenkins/model/JenkinsLocationConfiguration/help-adminAddress_pt_BR.html b/core/src/main/resources/jenkins/model/JenkinsLocationConfiguration/help-adminAddress_pt_BR.html index e4b245a744..7b19a95cda 100644 --- a/core/src/main/resources/jenkins/model/JenkinsLocationConfiguration/help-adminAddress_pt_BR.html +++ b/core/src/main/resources/jenkins/model/JenkinsLocationConfiguration/help-adminAddress_pt_BR.html @@ -1,5 +1,6 @@
- E-mails de notificação do Jenkins para os proprietários do projeto serão enviados - com este endereço no remetente. Pode ser apenas - "foo@acme.org" ou poderia ser algo como "Servidor Jenkins <foo@acme.org>" + E-mails de notificação do Jenkins para os proprietários do + projeto serão enviados com este endereço no remetente. Pode ser + apenas "foo@acme.org" ou poderia ser algo como "Servidor Jenkins + <foo@acme.org>"
diff --git a/core/src/main/resources/jenkins/model/JenkinsLocationConfiguration/help-adminAddress_ru.html b/core/src/main/resources/jenkins/model/JenkinsLocationConfiguration/help-adminAddress_ru.html index 28eaeb1ac5..c6fa060aae 100644 --- a/core/src/main/resources/jenkins/model/JenkinsLocationConfiguration/help-adminAddress_ru.html +++ b/core/src/main/resources/jenkins/model/JenkinsLocationConfiguration/help-adminAddress_ru.html @@ -1,5 +1,6 @@ 
- Уведомления от Jenkins адресатам проекта будут отправлены с этим адресом в поле From. - Это может быть просто "user@domain.com" или что-то более осмысленное, например, - "Jenkins Daemon <daemon@myjenkinsserver.domain.org>". + Уведомления от Jenkins адресатам проекта будут отправлены с этим адресом в + поле From. Это может быть просто "user@domain.com" или что-то более + осмысленное, например, "Jenkins Daemon + <daemon@myjenkinsserver.domain.org>".
diff --git a/core/src/main/resources/jenkins/model/JenkinsLocationConfiguration/help-adminAddress_tr.html b/core/src/main/resources/jenkins/model/JenkinsLocationConfiguration/help-adminAddress_tr.html index a430e9783a..2db7bf8fd1 100644 --- a/core/src/main/resources/jenkins/model/JenkinsLocationConfiguration/help-adminAddress_tr.html +++ b/core/src/main/resources/jenkins/model/JenkinsLocationConfiguration/help-adminAddress_tr.html @@ -1,5 +1,5 @@
Proje sahiplerine, bilgilendirmeler burada yazan mail adresi ile - gönderilecektir. "foo@acme.org" veya "Jenkins Daemon <foo@acme.org>" - şeklinde adresler yazılabilir. + gönderilecektir. "foo@acme.org" veya "Jenkins Daemon + <foo@acme.org>" şeklinde adresler yazılabilir.
diff --git a/core/src/main/resources/jenkins/model/JenkinsLocationConfiguration/help-adminAddress_zh_TW.html b/core/src/main/resources/jenkins/model/JenkinsLocationConfiguration/help-adminAddress_zh_TW.html index 13322bafbb..8a0fead342 100644 --- a/core/src/main/resources/jenkins/model/JenkinsLocationConfiguration/help-adminAddress_zh_TW.html +++ b/core/src/main/resources/jenkins/model/JenkinsLocationConfiguration/help-adminAddress_zh_TW.html @@ -1,4 +1,4 @@
- 由 Jenkins 寄發給專案擁有者的通知郵件，會使用這個寄件者地址寄出。 - 可以是 "foo@acme.org" 或 "Jenkins Daemon <foo@acme.org>" 這種格式。 + 由 Jenkins 寄發給專案擁有者的通知郵件，會使用這個寄件者地址寄出。 可以是 + "foo@acme.org" 或 "Jenkins Daemon <foo@acme.org>" 這種格式。
diff --git a/core/src/main/resources/jenkins/model/JenkinsLocationConfiguration/help-url.html b/core/src/main/resources/jenkins/model/JenkinsLocationConfiguration/help-url.html index 1d468fe2a6..01b3cd1c7b 100644 --- a/core/src/main/resources/jenkins/model/JenkinsLocationConfiguration/help-url.html +++ b/core/src/main/resources/jenkins/model/JenkinsLocationConfiguration/help-url.html @@ -1,10 +1,11 @@
- Optionally specify the HTTP address of the Jenkins installation, such - as http://yourhost.yourdomain/jenkins/. This value is used to - let Jenkins know how to refer to itself, ie. to display images or to - create links in emails. + Optionally specify the HTTP address of the Jenkins installation, such as + http://yourhost.yourdomain/jenkins/ + . This value is used to let Jenkins know how to refer to itself, ie. to + display images or to create links in emails.

- This is necessary because Jenkins cannot reliably detect such a URL - from within itself. + This is necessary because Jenkins cannot reliably detect such a URL from + within itself. +

diff --git a/core/src/main/resources/jenkins/model/JenkinsLocationConfiguration/help-url_bg.html b/core/src/main/resources/jenkins/model/JenkinsLocationConfiguration/help-url_bg.html index 3fe8e8ef5d..c73127d20d 100644 --- a/core/src/main/resources/jenkins/model/JenkinsLocationConfiguration/help-url_bg.html +++ b/core/src/main/resources/jenkins/model/JenkinsLocationConfiguration/help-url_bg.html @@ -1,10 +1,11 @@
Възможност да зададете адреса по HTTP на инсталацията на Jenkins като: - http://yourhost.yourdomain/jenkins/. Стойността се ползва, - за да може Jenkins да сочи себе си, примерно при показването на - изображения или при генерирането на връзки в електронните писма. + http://yourhost.yourdomain/jenkins/ + . Стойността се ползва, за да може Jenkins да сочи себе си, примерно при + показването на изображения или при генерирането на връзки в електронните + писма.

- Това се налага, защото няма надежден начин Jenkins сам да открие този - адрес. + Това се налага, защото няма надежден начин Jenkins сам да открие този адрес. +

diff --git a/core/src/main/resources/jenkins/model/JenkinsLocationConfiguration/help-url_de.html b/core/src/main/resources/jenkins/model/JenkinsLocationConfiguration/help-url_de.html index 0e94aa2546..18e1571761 100644 --- a/core/src/main/resources/jenkins/model/JenkinsLocationConfiguration/help-url_de.html +++ b/core/src/main/resources/jenkins/model/JenkinsLocationConfiguration/help-url_de.html @@ -1,10 +1,11 @@
Optional: Geben Sie hier die HTTP-Adresse der Jenkins-Instanz an, z.B: - http://yourhost.yourdomain/jenkins/. Dieser Wert wird verwendet, - um Links in E-Mail-Benachrichtigungen einzufügen. + http://yourhost.yourdomain/jenkins/ + . Dieser Wert wird verwendet, um Links in E-Mail-Benachrichtigungen + einzufügen.

- - Dies ist notwendig, weil Jenkins nicht zuverlässig seine eigene URL - feststellen kann. + Dies ist notwendig, weil Jenkins nicht zuverlässig seine eigene URL + feststellen kann. +

diff --git a/core/src/main/resources/jenkins/model/JenkinsLocationConfiguration/help-url_fr.html b/core/src/main/resources/jenkins/model/JenkinsLocationConfiguration/help-url_fr.html index 1287c11b2f..a511209ad1 100644 --- a/core/src/main/resources/jenkins/model/JenkinsLocationConfiguration/help-url_fr.html +++ b/core/src/main/resources/jenkins/model/JenkinsLocationConfiguration/help-url_fr.html @@ -1,10 +1,11 @@ 
- Spécifie optionnellement l'adresse HTTP de l'installation de Jenkins, - comme http://yourhost.yourdomain/jenkins/. - Cette valeur est utilisée pour mettre des liens dans les emails envoyés - par Jenkins. + Spécifie optionnellement l'adresse HTTP de l'installation de Jenkins, comme + http://yourhost.yourdomain/jenkins/ + . Cette valeur est utilisée pour mettre des liens dans les emails envoyés par + Jenkins.

- Cela est nécessaire parce que Jenkins ne peut pas détecter de façon - fiable sa propre URL. + Cela est nécessaire parce que Jenkins ne peut pas détecter de façon fiable + sa propre URL. +

diff --git a/core/src/main/resources/jenkins/model/JenkinsLocationConfiguration/help-url_it.html b/core/src/main/resources/jenkins/model/JenkinsLocationConfiguration/help-url_it.html index 654e170b2c..5e61d55a2d 100644 --- a/core/src/main/resources/jenkins/model/JenkinsLocationConfiguration/help-url_it.html +++ b/core/src/main/resources/jenkins/model/JenkinsLocationConfiguration/help-url_it.html @@ -1,10 +1,13 @@
Specificare facoltativamente l'indirizzo HTTP dell'installazione di Jenkins, - come http://host.dominio/jenkins/. Questo valore è utilizzato per - far sapere a Jenkins come far riferimento a se stesso, ad es. per - visualizzare immagini o creare collegamenti nei messaggi di posta elettronica. + come + http://host.dominio/jenkins/ + . Questo valore è utilizzato per far sapere a Jenkins come far riferimento a + se stesso, ad es. per visualizzare immagini o creare collegamenti nei messaggi + di posta elettronica.

- Ciò è necessario perché Jenkins non può rilevare autonomamente tale URL in - modo affidabile. + Ciò è necessario perché Jenkins non può rilevare autonomamente tale URL in + modo affidabile. +

diff --git a/core/src/main/resources/jenkins/model/JenkinsLocationConfiguration/help-url_ja.html b/core/src/main/resources/jenkins/model/JenkinsLocationConfiguration/help-url_ja.html index db978934e6..88bd79902e 100644 --- a/core/src/main/resources/jenkins/model/JenkinsLocationConfiguration/help-url_ja.html +++ b/core/src/main/resources/jenkins/model/JenkinsLocationConfiguration/help-url_ja.html @@ -1,7 +1,7 @@
- JenkinsのURLアドレスを指定(任意)します(例 http://yourhost.yourdomain/jenkins/)。 - この値を使用して、Jenkinsが送信するE-mailにリンクを記述します。 + JenkinsのURLアドレスを指定(任意)します(例 + http://yourhost.yourdomain/jenkins/ + )。 この値を使用して、Jenkinsが送信するE-mailにリンクを記述します。 -

- この値は、Jenkins自身ではURLを確実に検出できないため必要です。 +

この値は、Jenkins自身ではURLを確実に検出できないため必要です。

diff --git a/core/src/main/resources/jenkins/model/JenkinsLocationConfiguration/help-url_nl.html b/core/src/main/resources/jenkins/model/JenkinsLocationConfiguration/help-url_nl.html index bbdd5b7e76..6acc220065 100644 --- a/core/src/main/resources/jenkins/model/JenkinsLocationConfiguration/help-url_nl.html +++ b/core/src/main/resources/jenkins/model/JenkinsLocationConfiguration/help-url_nl.html @@ -1,10 +1,11 @@
- Optioneel u kunt het HTTP adres van uw Jenkins instantie - (v.b. http://uwnode.uwdomein/jenkins/) opgeven. Deze waarde - zal gebruikt worden voor het genereren van webreferenties in de e-mails die - Jenkins uitstuurt. + Optioneel u kunt het HTTP adres van uw Jenkins instantie (v.b. + http://uwnode.uwdomein/jenkins/ + ) opgeven. Deze waarde zal gebruikt worden voor het genereren van + webreferenties in de e-mails die Jenkins uitstuurt.

- Dit is nodig omdat Jenkins niet op een betrouwbare manier z'n eigen URL kan - detecteren. + Dit is nodig omdat Jenkins niet op een betrouwbare manier z'n eigen URL kan + detecteren. +

diff --git a/core/src/main/resources/jenkins/model/JenkinsLocationConfiguration/help-url_pt_BR.html b/core/src/main/resources/jenkins/model/JenkinsLocationConfiguration/help-url_pt_BR.html index 04fbf08261..332a2bb907 100644 --- a/core/src/main/resources/jenkins/model/JenkinsLocationConfiguration/help-url_pt_BR.html +++ b/core/src/main/resources/jenkins/model/JenkinsLocationConfiguration/help-url_pt_BR.html @@ -1,9 +1,11 @@
- Opcionalmente, especifique o endereço HTTP da instalação do Jenkins, tal - como http://seuhost.seudominio/jenkins/. Este valor é usado para - por links nos e-mails gerados pelo Jenkins. + Opcionalmente, especifique o endereço HTTP da instalação do + Jenkins, tal como + http://seuhost.seudominio/jenkins/ + . Este valor é usado para por links nos e-mails gerados pelo Jenkins.

- Isto é necessário porque o Jenkins não pode resolver tal URL - de dentre dele mesmo. + Isto é necessário porque o Jenkins não pode resolver tal URL + de dentre dele mesmo. +

diff --git a/core/src/main/resources/jenkins/model/JenkinsLocationConfiguration/help-url_ru.html b/core/src/main/resources/jenkins/model/JenkinsLocationConfiguration/help-url_ru.html index 8992c0022e..55a47fa1b0 100644 --- a/core/src/main/resources/jenkins/model/JenkinsLocationConfiguration/help-url_ru.html +++ b/core/src/main/resources/jenkins/model/JenkinsLocationConfiguration/help-url_ru.html @@ -1,8 +1,11 @@ 
- Укажите адрес текущей инсталляции Jenkins в виде http://yourhost.yourdomain:8080/jenkins/. - Это значение бодет использоваться для генерации ссылок из сообщений в + Укажите адрес текущей инсталляции Jenkins в виде + http://yourhost.yourdomain:8080/jenkins/ + . Это значение бодет использоваться для генерации ссылок из сообщений в Jenkins. (опционально)

- Это требуется потому, что сам Jenkins не может достоверно определить свой URL. + Это требуется потому, что сам Jenkins не может достоверно определить свой + URL. +

diff --git a/core/src/main/resources/jenkins/model/JenkinsLocationConfiguration/help-url_tr.html b/core/src/main/resources/jenkins/model/JenkinsLocationConfiguration/help-url_tr.html index 9500f4c551..e15a1b3aff 100644 --- a/core/src/main/resources/jenkins/model/JenkinsLocationConfiguration/help-url_tr.html +++ b/core/src/main/resources/jenkins/model/JenkinsLocationConfiguration/help-url_tr.html @@ -1,9 +1,12 @@
- Jenkins kurulumunuzun HTTP adresini, http://yourhost.yourdomain/jenkins/ - şeklinde burada belirtebilirsiniz, böylelikle e-posta içerisinde Jenkins ile ilgili - linkler bu URL yardımı ile oluşturulacaktır. + Jenkins kurulumunuzun HTTP adresini, + http://yourhost.yourdomain/jenkins/ + şeklinde burada belirtebilirsiniz, böylelikle e-posta + içerisinde Jenkins ile ilgili linkler bu URL yardımı ile + oluşturulacaktır.

- Jenkins, kendi URL'ini güvenilir bir şekilde tespit edemeyeceği için, bu kısmı doldurmanız - gereklidir. + Jenkins, kendi URL'ini güvenilir bir şekilde tespit + edemeyeceği için, bu kısmı doldurmanız gereklidir. +

diff --git a/core/src/main/resources/jenkins/model/JenkinsLocationConfiguration/help-url_zh_TW.html b/core/src/main/resources/jenkins/model/JenkinsLocationConfiguration/help-url_zh_TW.html index d0513106b5..66b1884e47 100644 --- a/core/src/main/resources/jenkins/model/JenkinsLocationConfiguration/help-url_zh_TW.html +++ b/core/src/main/resources/jenkins/model/JenkinsLocationConfiguration/help-url_zh_TW.html @@ -1,7 +1,8 @@
- 可以設定 Jenkins 的 HTTP 網址，例如 http://yourhost.yourdomain/jenkins/。 - 這個值可以讓 Jenkins 知道該怎麼連回自己，例如: 在電子郵件中顯示圖片或是連結。 + 可以設定 Jenkins 的 HTTP 網址，例如 + http://yourhost.yourdomain/jenkins/ + 。 這個值可以讓 Jenkins 知道該怎麼連回自己，例如: + 在電子郵件中顯示圖片或是連結。 -

- 這不是多此一舉，因為 Jenkins 沒有辦法百分之一百自已偵測出正確的網址。 +

這不是多此一舉，因為 Jenkins 沒有辦法百分之一百自已偵測出正確的網址。

diff --git a/core/src/main/resources/jenkins/model/ProjectNamingStrategy/PatternProjectNamingStrategy/help-description.html b/core/src/main/resources/jenkins/model/ProjectNamingStrategy/PatternProjectNamingStrategy/help-description.html index 01e54328f0..82fdb71da5 100644 --- a/core/src/main/resources/jenkins/model/ProjectNamingStrategy/PatternProjectNamingStrategy/help-description.html +++ b/core/src/main/resources/jenkins/model/ProjectNamingStrategy/PatternProjectNamingStrategy/help-description.html @@ -1,4 +1,4 @@

- Provide a human-readable description to explain naming constraints. - This will be used as the error message when the job name does not match the pattern. + Provide a human-readable description to explain naming constraints. This will + be used as the error message when the job name does not match the pattern.

diff --git a/core/src/main/resources/jenkins/model/ProjectNamingStrategy/PatternProjectNamingStrategy/help-description_bg.html b/core/src/main/resources/jenkins/model/ProjectNamingStrategy/PatternProjectNamingStrategy/help-description_bg.html index 6a49633bb4..b613213e4c 100644 --- a/core/src/main/resources/jenkins/model/ProjectNamingStrategy/PatternProjectNamingStrategy/help-description_bg.html +++ b/core/src/main/resources/jenkins/model/ProjectNamingStrategy/PatternProjectNamingStrategy/help-description_bg.html @@ -1,4 +1,4 @@

- Потребителско описание на шаблона за имена на задачите за изграждане. - Извежда се като съобщение за грешка при опит да се наруши конвенцията. + Потребителско описание на шаблона за имена на задачите за изграждане. Извежда + се като съобщение за грешка при опит да се наруши конвенцията.

diff --git a/core/src/main/resources/jenkins/model/ProjectNamingStrategy/PatternProjectNamingStrategy/help-description_de.html b/core/src/main/resources/jenkins/model/ProjectNamingStrategy/PatternProjectNamingStrategy/help-description_de.html index 1c2fdec73c..c563ccbc4c 100644 --- a/core/src/main/resources/jenkins/model/ProjectNamingStrategy/PatternProjectNamingStrategy/help-description_de.html +++ b/core/src/main/resources/jenkins/model/ProjectNamingStrategy/PatternProjectNamingStrategy/help-description_de.html @@ -1,4 +1,5 @@

- Geben Sie hier eine Beschreibung des Namensschemas ein. - Sie wird als Fehlermeldung verwendet, wenn der Jobname nicht auf den Regulären Ausdruck passt. + Geben Sie hier eine Beschreibung des Namensschemas ein. Sie wird als + Fehlermeldung verwendet, wenn der Jobname nicht auf den Regulären Ausdruck + passt.

diff --git a/core/src/main/resources/jenkins/model/ProjectNamingStrategy/PatternProjectNamingStrategy/help-description_it.html b/core/src/main/resources/jenkins/model/ProjectNamingStrategy/PatternProjectNamingStrategy/help-description_it.html index 49ecf4ee13..2347952fe5 100644 --- a/core/src/main/resources/jenkins/model/ProjectNamingStrategy/PatternProjectNamingStrategy/help-description_it.html +++ b/core/src/main/resources/jenkins/model/ProjectNamingStrategy/PatternProjectNamingStrategy/help-description_it.html @@ -1,5 +1,5 @@

- Fornire una descrizione leggibile da un utente per spiegare i limiti - applicati ai nomi. Questa sarà utilizzata come messaggio d'errore se il - nome del processo non corrisponde al pattern. + Fornire una descrizione leggibile da un utente per spiegare i limiti applicati + ai nomi. Questa sarà utilizzata come messaggio d'errore se il nome del + processo non corrisponde al pattern.

diff --git a/core/src/main/resources/jenkins/mvn/DefaultGlobalSettingsProvider/help.html b/core/src/main/resources/jenkins/mvn/DefaultGlobalSettingsProvider/help.html index a4898a51a4..93250bd16d 100644 --- a/core/src/main/resources/jenkins/mvn/DefaultGlobalSettingsProvider/help.html +++ b/core/src/main/resources/jenkins/mvn/DefaultGlobalSettingsProvider/help.html @@ -1,3 +1,5 @@
- Use default maven settings ($HOME/.m2/settings.xml) as set on build node. + Use default maven settings ( + $HOME/.m2/settings.xml + ) as set on build node.
diff --git a/core/src/main/resources/jenkins/mvn/DefaultGlobalSettingsProvider/help_bg.html b/core/src/main/resources/jenkins/mvn/DefaultGlobalSettingsProvider/help_bg.html index b76131e324..f8762f6adf 100644 --- a/core/src/main/resources/jenkins/mvn/DefaultGlobalSettingsProvider/help_bg.html +++ b/core/src/main/resources/jenkins/mvn/DefaultGlobalSettingsProvider/help_bg.html @@ -1,4 +1,5 @@
- Използване на стандартните настройки на maven, зададени на компютъра - ($HOME/.m2/settings.xml). + Използване на стандартните настройки на maven, зададени на компютъра ( + $HOME/.m2/settings.xml + ).
diff --git a/core/src/main/resources/jenkins/mvn/DefaultGlobalSettingsProvider/help_it.html b/core/src/main/resources/jenkins/mvn/DefaultGlobalSettingsProvider/help_it.html index dfefa92935..b6f8f2ea7a 100644 --- a/core/src/main/resources/jenkins/mvn/DefaultGlobalSettingsProvider/help_it.html +++ b/core/src/main/resources/jenkins/mvn/DefaultGlobalSettingsProvider/help_it.html @@ -1,5 +1,5 @@
- Utilizza le impostazioni predefinite di Maven - ($HOME/.m2/settings.xml) così come impostate sul nodo di - compilazione. + Utilizza le impostazioni predefinite di Maven ( + $HOME/.m2/settings.xml + ) così come impostate sul nodo di compilazione.
diff --git a/core/src/main/resources/jenkins/mvn/DefaultGlobalSettingsProvider/help_zh_TW.html b/core/src/main/resources/jenkins/mvn/DefaultGlobalSettingsProvider/help_zh_TW.html index 9129ed4df5..8bc738f960 100644 --- a/core/src/main/resources/jenkins/mvn/DefaultGlobalSettingsProvider/help_zh_TW.html +++ b/core/src/main/resources/jenkins/mvn/DefaultGlobalSettingsProvider/help_zh_TW.html @@ -1,3 +1,5 @@
- 使用建置節點上的 Maven 預設設定 ($HOME/.m2/settings.xml)。 -
\ No newline at end of file + 使用建置節點上的 Maven 預設設定 ( + $HOME/.m2/settings.xml + )。 + diff --git a/core/src/main/resources/jenkins/mvn/DefaultSettingsProvider/help.html b/core/src/main/resources/jenkins/mvn/DefaultSettingsProvider/help.html index a4898a51a4..93250bd16d 100644 --- a/core/src/main/resources/jenkins/mvn/DefaultSettingsProvider/help.html +++ b/core/src/main/resources/jenkins/mvn/DefaultSettingsProvider/help.html @@ -1,3 +1,5 @@
- Use default maven settings ($HOME/.m2/settings.xml) as set on build node. + Use default maven settings ( + $HOME/.m2/settings.xml + ) as set on build node.
diff --git a/core/src/main/resources/jenkins/mvn/DefaultSettingsProvider/help_bg.html b/core/src/main/resources/jenkins/mvn/DefaultSettingsProvider/help_bg.html index b76131e324..f8762f6adf 100644 --- a/core/src/main/resources/jenkins/mvn/DefaultSettingsProvider/help_bg.html +++ b/core/src/main/resources/jenkins/mvn/DefaultSettingsProvider/help_bg.html @@ -1,4 +1,5 @@
- Използване на стандартните настройки на maven, зададени на компютъра - ($HOME/.m2/settings.xml). + Използване на стандартните настройки на maven, зададени на компютъра ( + $HOME/.m2/settings.xml + ).
diff --git a/core/src/main/resources/jenkins/mvn/DefaultSettingsProvider/help_it.html b/core/src/main/resources/jenkins/mvn/DefaultSettingsProvider/help_it.html index dfefa92935..b6f8f2ea7a 100644 --- a/core/src/main/resources/jenkins/mvn/DefaultSettingsProvider/help_it.html +++ b/core/src/main/resources/jenkins/mvn/DefaultSettingsProvider/help_it.html @@ -1,5 +1,5 @@
- Utilizza le impostazioni predefinite di Maven - ($HOME/.m2/settings.xml) così come impostate sul nodo di - compilazione. + Utilizza le impostazioni predefinite di Maven ( + $HOME/.m2/settings.xml + ) così come impostate sul nodo di compilazione.
diff --git a/core/src/main/resources/jenkins/mvn/DefaultSettingsProvider/help_zh_TW.html b/core/src/main/resources/jenkins/mvn/DefaultSettingsProvider/help_zh_TW.html index 9129ed4df5..8bc738f960 100644 --- a/core/src/main/resources/jenkins/mvn/DefaultSettingsProvider/help_zh_TW.html +++ b/core/src/main/resources/jenkins/mvn/DefaultSettingsProvider/help_zh_TW.html @@ -1,3 +1,5 @@
- 使用建置節點上的 Maven 預設設定 ($HOME/.m2/settings.xml)。 -
\ No newline at end of file + 使用建置節點上的 Maven 預設設定 ( + $HOME/.m2/settings.xml + )。 + diff --git a/core/src/main/resources/jenkins/mvn/FilePathGlobalSettingsProvider/help-path.html b/core/src/main/resources/jenkins/mvn/FilePathGlobalSettingsProvider/help-path.html index 551a01e749..79158f6d5a 100644 --- a/core/src/main/resources/jenkins/mvn/FilePathGlobalSettingsProvider/help-path.html +++ b/core/src/main/resources/jenkins/mvn/FilePathGlobalSettingsProvider/help-path.html @@ -1,3 +1,4 @@
- Path to settings.xml file, relative to project workspace or absolute (variables are supported). -
\ No newline at end of file + Path to settings.xml file, relative to project workspace or absolute + (variables are supported). + diff --git a/core/src/main/resources/jenkins/mvn/FilePathGlobalSettingsProvider/help-path_bg.html b/core/src/main/resources/jenkins/mvn/FilePathGlobalSettingsProvider/help-path_bg.html index f4be79b07e..3bf199bd58 100644 --- a/core/src/main/resources/jenkins/mvn/FilePathGlobalSettingsProvider/help-path_bg.html +++ b/core/src/main/resources/jenkins/mvn/FilePathGlobalSettingsProvider/help-path_bg.html @@ -1,4 +1,4 @@
- Път към файла „settings.xml“ — или абсолютен, или относителен спрямо - работното пространство на проекта (поддържат се променливи). -
\ No newline at end of file + Път към файла „settings.xml“ — или абсолютен, или относителен спрямо работното + пространство на проекта (поддържат се променливи). + diff --git a/core/src/main/resources/jenkins/mvn/FilePathGlobalSettingsProvider/help-path_ja.html b/core/src/main/resources/jenkins/mvn/FilePathGlobalSettingsProvider/help-path_ja.html index 6ba072857c..49e81ef31a 100644 --- a/core/src/main/resources/jenkins/mvn/FilePathGlobalSettingsProvider/help-path_ja.html +++ b/core/src/main/resources/jenkins/mvn/FilePathGlobalSettingsProvider/help-path_ja.html @@ -1,3 +1,3 @@
- settings.xmlのパスを、プロジェクトのワークスペースからの相対パスか、絶対パスで指定します(変数をサポートします)。 -
\ No newline at end of file + settings.xmlのパスを、プロジェクトのワークスペースからの相対パスか、絶対パスで指定します(変数をサポートします)。 + diff --git a/core/src/main/resources/jenkins/mvn/FilePathGlobalSettingsProvider/help-path_zh_TW.html b/core/src/main/resources/jenkins/mvn/FilePathGlobalSettingsProvider/help-path_zh_TW.html index c2710f0348..0cc6697f86 100644 --- a/core/src/main/resources/jenkins/mvn/FilePathGlobalSettingsProvider/help-path_zh_TW.html +++ b/core/src/main/resources/jenkins/mvn/FilePathGlobalSettingsProvider/help-path_zh_TW.html @@ -1,3 +1,3 @@
- settings.xml 檔路徑，可以是相對於專案工作區的路徑或是絕對路徑 (支援變數)。 -
\ No newline at end of file + settings.xml 檔路徑，可以是相對於專案工作區的路徑或是絕對路徑 (支援變數)。 + diff --git a/core/src/main/resources/jenkins/mvn/FilePathGlobalSettingsProvider/help.html b/core/src/main/resources/jenkins/mvn/FilePathGlobalSettingsProvider/help.html index 0fd18cd6fc..3f8ee10a8a 100644 --- a/core/src/main/resources/jenkins/mvn/FilePathGlobalSettingsProvider/help.html +++ b/core/src/main/resources/jenkins/mvn/FilePathGlobalSettingsProvider/help.html @@ -1,3 +1,6 @@
- Use a custom global settings.xml file from job workspace. Such a file is checked out from SCM as part of the job or a well known location. + Use a custom global + settings.xml + file from job workspace. Such a file is checked out from SCM as part of the + job or a well known location.
diff --git a/core/src/main/resources/jenkins/mvn/FilePathGlobalSettingsProvider/help_bg.html b/core/src/main/resources/jenkins/mvn/FilePathGlobalSettingsProvider/help_bg.html index 507efe3180..3992664b94 100644 --- a/core/src/main/resources/jenkins/mvn/FilePathGlobalSettingsProvider/help_bg.html +++ b/core/src/main/resources/jenkins/mvn/FilePathGlobalSettingsProvider/help_bg.html @@ -1,5 +1,7 @@
- Използване на специфичен глобален файл settings.xml от работното - пространство на проекта. Той трябва да бъде изтеглен от системата за контрол - на версиите като част от изграждането или да се намира на достъпно място. + Използване на специфичен глобален файл + settings.xml + от работното пространство на проекта. Той трябва да бъде изтеглен от системата + за контрол на версиите като част от изграждането или да се намира на достъпно + място.
diff --git a/core/src/main/resources/jenkins/mvn/FilePathGlobalSettingsProvider/help_it.html b/core/src/main/resources/jenkins/mvn/FilePathGlobalSettingsProvider/help_it.html index 21f414cb3c..cfccb54263 100644 --- a/core/src/main/resources/jenkins/mvn/FilePathGlobalSettingsProvider/help_it.html +++ b/core/src/main/resources/jenkins/mvn/FilePathGlobalSettingsProvider/help_it.html @@ -1,5 +1,7 @@
- Utilizza un file settings.xml globale personalizzato dallo spazio di - lavoro del processo. Tale file viene recuperato dal sistema di gestione del - codice sorgente come parte del processo o da un percorso noto. + Utilizza un file + settings.xml + globale personalizzato dallo spazio di lavoro del processo. Tale file viene + recuperato dal sistema di gestione del codice sorgente come parte del processo + o da un percorso noto.
diff --git a/core/src/main/resources/jenkins/mvn/FilePathGlobalSettingsProvider/help_ja.html b/core/src/main/resources/jenkins/mvn/FilePathGlobalSettingsProvider/help_ja.html index 7a79996bb7..986bbe7e4e 100644 --- a/core/src/main/resources/jenkins/mvn/FilePathGlobalSettingsProvider/help_ja.html +++ b/core/src/main/resources/jenkins/mvn/FilePathGlobalSettingsProvider/help_ja.html @@ -1,4 +1,6 @@
- 独自のsettings.xmlを使用します。ジョブの一部としてSCMからそのファイルをダウンロードしたり、 - 既知の場所にあるファイルを指定してください。 + 独自の + settings.xml + を使用します。ジョブの一部としてSCMからそのファイルをダウンロードしたり、 + 既知の場所にあるファイルを指定してください。
diff --git a/core/src/main/resources/jenkins/mvn/FilePathGlobalSettingsProvider/help_zh_TW.html b/core/src/main/resources/jenkins/mvn/FilePathGlobalSettingsProvider/help_zh_TW.html index 00550da55d..f81387b5dd 100644 --- a/core/src/main/resources/jenkins/mvn/FilePathGlobalSettingsProvider/help_zh_TW.html +++ b/core/src/main/resources/jenkins/mvn/FilePathGlobalSettingsProvider/help_zh_TW.html @@ -1,4 +1,5 @@
- 使用作業工作區中的自訂全域 settings.xml 檔。 - 這個檔案是跟專案一起從 SCM Checkout 出來的，或是放在某個共用的地方。 -
\ No newline at end of file + 使用作業工作區中的自訂全域 + settings.xml + 檔。 這個檔案是跟專案一起從 SCM Checkout 出來的，或是放在某個共用的地方。 + diff --git a/core/src/main/resources/jenkins/mvn/FilePathSettingsProvider/help-path.html b/core/src/main/resources/jenkins/mvn/FilePathSettingsProvider/help-path.html index 551a01e749..79158f6d5a 100644 --- a/core/src/main/resources/jenkins/mvn/FilePathSettingsProvider/help-path.html +++ b/core/src/main/resources/jenkins/mvn/FilePathSettingsProvider/help-path.html @@ -1,3 +1,4 @@
- Path to settings.xml file, relative to project workspace or absolute (variables are supported). -
\ No newline at end of file + Path to settings.xml file, relative to project workspace or absolute + (variables are supported). + diff --git a/core/src/main/resources/jenkins/mvn/FilePathSettingsProvider/help-path_bg.html b/core/src/main/resources/jenkins/mvn/FilePathSettingsProvider/help-path_bg.html index f4be79b07e..3bf199bd58 100644 --- a/core/src/main/resources/jenkins/mvn/FilePathSettingsProvider/help-path_bg.html +++ b/core/src/main/resources/jenkins/mvn/FilePathSettingsProvider/help-path_bg.html @@ -1,4 +1,4 @@
- Път към файла „settings.xml“ — или абсолютен, или относителен спрямо - работното пространство на проекта (поддържат се променливи). -
\ No newline at end of file + Път към файла „settings.xml“ — или абсолютен, или относителен спрямо работното + пространство на проекта (поддържат се променливи). + diff --git a/core/src/main/resources/jenkins/mvn/FilePathSettingsProvider/help-path_ja.html b/core/src/main/resources/jenkins/mvn/FilePathSettingsProvider/help-path_ja.html index 6ba072857c..49e81ef31a 100644 --- a/core/src/main/resources/jenkins/mvn/FilePathSettingsProvider/help-path_ja.html +++ b/core/src/main/resources/jenkins/mvn/FilePathSettingsProvider/help-path_ja.html @@ -1,3 +1,3 @@
- settings.xmlのパスを、プロジェクトのワークスペースからの相対パスか、絶対パスで指定します(変数をサポートします)。 -
\ No newline at end of file + settings.xmlのパスを、プロジェクトのワークスペースからの相対パスか、絶対パスで指定します(変数をサポートします)。 + diff --git a/core/src/main/resources/jenkins/mvn/FilePathSettingsProvider/help-path_zh_TW.html b/core/src/main/resources/jenkins/mvn/FilePathSettingsProvider/help-path_zh_TW.html index c960aad724..0cc6697f86 100644 --- a/core/src/main/resources/jenkins/mvn/FilePathSettingsProvider/help-path_zh_TW.html +++ b/core/src/main/resources/jenkins/mvn/FilePathSettingsProvider/help-path_zh_TW.html @@ -1,3 +1,3 @@
- settings.xml 檔路徑，可以是相對於專案工作區的路徑或是絕對路徑 (支援變數)。 -
\ No newline at end of file + settings.xml 檔路徑，可以是相對於專案工作區的路徑或是絕對路徑 (支援變數)。 + diff --git a/core/src/main/resources/jenkins/mvn/FilePathSettingsProvider/help.html b/core/src/main/resources/jenkins/mvn/FilePathSettingsProvider/help.html index 7a1e765e5d..9b897032ea 100644 --- a/core/src/main/resources/jenkins/mvn/FilePathSettingsProvider/help.html +++ b/core/src/main/resources/jenkins/mvn/FilePathSettingsProvider/help.html @@ -1,3 +1,6 @@
- Use a custom settings.xml file. Such a file is checked out from SCM as part of the job or a well known location. + Use a custom + settings.xml + file. Such a file is checked out from SCM as part of the job or a well known + location.
diff --git a/core/src/main/resources/jenkins/mvn/FilePathSettingsProvider/help_bg.html b/core/src/main/resources/jenkins/mvn/FilePathSettingsProvider/help_bg.html index 8bfb571d17..6ec89d7bb2 100644 --- a/core/src/main/resources/jenkins/mvn/FilePathSettingsProvider/help_bg.html +++ b/core/src/main/resources/jenkins/mvn/FilePathSettingsProvider/help_bg.html @@ -1,5 +1,6 @@
- Използване на специфичен файл settings.xml. Той трябва да бъде - изтеглен от системата за контрол на версиите като част от изграждането или - да се намира на достъпно място. + Използване на специфичен файл + settings.xml + . Той трябва да бъде изтеглен от системата за контрол на версиите като част от + изграждането или да се намира на достъпно място.
diff --git a/core/src/main/resources/jenkins/mvn/FilePathSettingsProvider/help_it.html b/core/src/main/resources/jenkins/mvn/FilePathSettingsProvider/help_it.html index 0d3a599552..6fc1ab8a74 100644 --- a/core/src/main/resources/jenkins/mvn/FilePathSettingsProvider/help_it.html +++ b/core/src/main/resources/jenkins/mvn/FilePathSettingsProvider/help_it.html @@ -1,5 +1,6 @@
- Utilizza un file settings.xml personalizzato. Tale file viene - recuperato dal sistema di gestione del codice sorgente come parte del - processo o da un percorso noto. + Utilizza un file + settings.xml + personalizzato. Tale file viene recuperato dal sistema di gestione del codice + sorgente come parte del processo o da un percorso noto.
diff --git a/core/src/main/resources/jenkins/mvn/FilePathSettingsProvider/help_ja.html b/core/src/main/resources/jenkins/mvn/FilePathSettingsProvider/help_ja.html index 7a79996bb7..986bbe7e4e 100644 --- a/core/src/main/resources/jenkins/mvn/FilePathSettingsProvider/help_ja.html +++ b/core/src/main/resources/jenkins/mvn/FilePathSettingsProvider/help_ja.html @@ -1,4 +1,6 @@
- 独自のsettings.xmlを使用します。ジョブの一部としてSCMからそのファイルをダウンロードしたり、 - 既知の場所にあるファイルを指定してください。 + 独自の + settings.xml + を使用します。ジョブの一部としてSCMからそのファイルをダウンロードしたり、 + 既知の場所にあるファイルを指定してください。
diff --git a/core/src/main/resources/jenkins/mvn/FilePathSettingsProvider/help_zh_TW.html b/core/src/main/resources/jenkins/mvn/FilePathSettingsProvider/help_zh_TW.html index ac735b8377..c97ea94d2b 100644 --- a/core/src/main/resources/jenkins/mvn/FilePathSettingsProvider/help_zh_TW.html +++ b/core/src/main/resources/jenkins/mvn/FilePathSettingsProvider/help_zh_TW.html @@ -1,4 +1,5 @@
- 使用自訂的 settings.xml 檔。 - 這個檔案是跟專案一起從 SCM Checkout 出來的，或是放在某個共用的地方。 -
\ No newline at end of file + 使用自訂的 + settings.xml + 檔。 這個檔案是跟專案一起從 SCM Checkout 出來的，或是放在某個共用的地方。 + diff --git a/core/src/main/resources/jenkins/security/ApiTokenProperty/help-tokenStore.html b/core/src/main/resources/jenkins/security/ApiTokenProperty/help-tokenStore.html index acdb1bd05e..b3a80a624c 100644 --- a/core/src/main/resources/jenkins/security/ApiTokenProperty/help-tokenStore.html +++ b/core/src/main/resources/jenkins/security/ApiTokenProperty/help-tokenStore.html @@ -1,16 +1,28 @@
- API tokens offer a way to make authenticated CLI or REST API calls. - See our wiki for more details.
- The username associated with each token is your Jenkins username.
-
- Some good practices for keeping your API tokens secure are: -
    -
  • Use a different token for each application so that if an application is compromised you can revoke its token individually.
    • -
  • Regenerate the tokens every 6 months (depending on your context). We display an indicator concerning the age of the token.
    • -
  • Protect it like your password, as it allows other people to access Jenkins as you.
    • -
-
- Every time Jenkins is restarted the creation dates for unused legacy tokens are reset - which means that the dates may be inaccurate. -
+ API tokens offer a way to make authenticated CLI or REST API calls. See + our wiki + for more details. +
+ The username associated with each token is your Jenkins username. +
+
+ Some good practices for keeping your API tokens secure are: +
    +
  • + Use a different token for each application so that if an application is + compromised you can revoke its token individually. +
    • +
  • + Regenerate the tokens every 6 months (depending on your context). We + display an indicator concerning the age of the token. +
    • +
  • + Protect it like your password, as it allows other people to access Jenkins + as you. +
    • +
+
+ Every time Jenkins is restarted the creation dates for unused legacy tokens + are reset which means that the dates may be inaccurate. +
diff --git a/core/src/main/resources/jenkins/security/ApiTokenProperty/help-tokenStore_bg.html b/core/src/main/resources/jenkins/security/ApiTokenProperty/help-tokenStore_bg.html index ab2eb75bf0..174286ace4 100644 --- a/core/src/main/resources/jenkins/security/ApiTokenProperty/help-tokenStore_bg.html +++ b/core/src/main/resources/jenkins/security/ApiTokenProperty/help-tokenStore_bg.html @@ -1,6 +1,9 @@
- Този жетон за API дава възможност за идентификация в извикването по REST. За повече подробности погледнете - документацията в уикито. - Жетонът от това API трябва да се пази подобно на парола, защото позволява на други хора да достъпват - Jenkins от ваше име и с вашите права. + Този жетон за API дава възможност за идентификация в извикването по REST. За + повече подробности погледнете + + документацията в уикито + + . Жетонът от това API трябва да се пази подобно на парола, защото позволява на + други хора да достъпват Jenkins от ваше име и с вашите права.
diff --git a/core/src/main/resources/jenkins/security/ApiTokenProperty/help-tokenStore_fr.html b/core/src/main/resources/jenkins/security/ApiTokenProperty/help-tokenStore_fr.html index 6962b64159..0f1174c308 100644 --- a/core/src/main/resources/jenkins/security/ApiTokenProperty/help-tokenStore_fr.html +++ b/core/src/main/resources/jenkins/security/ApiTokenProperty/help-tokenStore_fr.html @@ -1,17 +1,30 @@
- Les jetons d'API permettent l'authentification de l'utilisateur lors de l'utilisation du CLI ou des API REST. - Merci de consulter le wiki pour plus de détails.
- L'identifiant (username) associé au jeton est l'identifiant Jenkins.
-
+ Les jetons d'API permettent l'authentification de l'utilisateur lors de + l'utilisation du CLI ou des API REST. Merci de + consulter le wiki + pour plus de détails. +
+ L'identifiant (username) associé au jeton est l'identifiant Jenkins. +
+
Les bonnes pratiques pour garder vos jetons sécurisés sont:
    -
  • Utiliser un jeton différent par application, de telle sorte que si l'application est compromise ce jeton peut - être révoqué individuellement.
    • -
  • Regénérer le jeton tous les 6 mois (en fonction du contexte). L'ancienneté du jeton est affichée.
    • -
  • Protéger le jeton autant qu'un mot de passe, il permet d'utiliser Jenkins en votre nom.
    • +
  • + Utiliser un jeton différent par application, de telle sorte que si + l'application est compromise ce jeton peut être révoqué individuellement. +
    • +
  • + Regénérer le jeton tous les 6 mois (en fonction du contexte). L'ancienneté + du jeton est affichée. +
    • +
  • + Protéger le jeton autant qu'un mot de passe, il permet d'utiliser Jenkins + en votre nom. +
- A chaque redémarrage de Jenkins la date de création pour les jetons obsolètes est remise à zéro, c'est à dire que - la date peut ne pas être exacte. + A chaque redémarrage de Jenkins la date de création pour les jetons + obsolètes est remise à zéro, c'est à dire que la date peut ne pas être + exacte.
diff --git a/core/src/main/resources/jenkins/security/ApiTokenProperty/help-tokenStore_it.html b/core/src/main/resources/jenkins/security/ApiTokenProperty/help-tokenStore_it.html index fdd7c5c17a..0a0ea78be5 100644 --- a/core/src/main/resources/jenkins/security/ApiTokenProperty/help-tokenStore_it.html +++ b/core/src/main/resources/jenkins/security/ApiTokenProperty/help-tokenStore_it.html @@ -1,15 +1,27 @@
I token API offrono un modo di eseguire chiamate autenticate dall'interfaccia a riga di comando o tramite API REST. Si veda - il nostro wiki per - ulteriori informazioni.
- Il nome utente associato con ogni token è il nome utente di Jenkins.
-
+ il nostro wiki + per ulteriori informazioni. +
+ Il nome utente associato con ogni token è il nome utente di Jenkins. +
+
Per mantenere al sicuro i propri token API è opportuno:
    -
  • Utilizzare un token differente per ogni applicazione in modo che, se un'applicazione viene compromessa, si possa revocare il suo token individualmente.
    • -
  • Rigenerare i token ogni sei mesi (a seconda del contesto). Visualizziamo un indicatore relativo all'età del token.
    • -
  • Proteggerlo come la propria password, perché consente di accedere a Jenkins con le proprie credenziali.
    • +
  • + Utilizzare un token differente per ogni applicazione in modo che, se + un'applicazione viene compromessa, si possa revocare il suo token + individualmente. +
    • +
  • + Rigenerare i token ogni sei mesi (a seconda del contesto). Visualizziamo + un indicatore relativo all'età del token. +
    • +
  • + Proteggerlo come la propria password, perché consente di accedere a + Jenkins con le proprie credenziali. +
A ogni riavvio di Jenkins, le date di creazione per i token legacy non diff --git a/core/src/main/resources/jenkins/security/ApiTokenProperty/help-tokenStore_ja.html b/core/src/main/resources/jenkins/security/ApiTokenProperty/help-tokenStore_ja.html index 388a68dce3..6c5f55d127 100644 --- a/core/src/main/resources/jenkins/security/ApiTokenProperty/help-tokenStore_ja.html +++ b/core/src/main/resources/jenkins/security/ApiTokenProperty/help-tokenStore_ja.html @@ -1,5 +1,6 @@
- APIトークンは、REST API使用時の認証に使用されます。 - 詳細はWikiを参照してください。 - APIトークンはパスワードと同様に保護する必要があります。そうしないと、他人が詐称してJenkinsにアクセス可能になります。 -
\ No newline at end of file + APIトークンは、REST API使用時の認証に使用されます。 詳細は + Wiki + を参照してください。 + APIトークンはパスワードと同様に保護する必要があります。そうしないと、他人が詐称してJenkinsにアクセス可能になります。 +
diff --git a/core/src/main/resources/jenkins/security/ApiTokenProperty/help-tokenStore_zh_TW.html b/core/src/main/resources/jenkins/security/ApiTokenProperty/help-tokenStore_zh_TW.html index 12014396eb..f2e7e5e043 100644 --- a/core/src/main/resources/jenkins/security/ApiTokenProperty/help-tokenStore_zh_TW.html +++ b/core/src/main/resources/jenkins/security/ApiTokenProperty/help-tokenStore_zh_TW.html @@ -1,5 +1,6 @@
- 您在呼叫 REST API 時要使用 API Token 驗證。 - 詳情請參考我們的 Wiki。 - API Token 應該當做密碼一樣好好保管，因為有了它，其他人就能跟您一樣存取 Jenkins。 -
\ No newline at end of file + 您在呼叫 REST API 時要使用 API Token 驗證。 詳情請參考 + 我們的 Wiki + 。 API Token 應該當做密碼一樣好好保管，因為有了它，其他人就能跟您一樣存取 + Jenkins。 +
diff --git a/core/src/main/resources/jenkins/security/ApiTokenProperty/resources.css b/core/src/main/resources/jenkins/security/ApiTokenProperty/resources.css index 631043e98c..f344fe84d7 100644 --- a/core/src/main/resources/jenkins/security/ApiTokenProperty/resources.css +++ b/core/src/main/resources/jenkins/security/ApiTokenProperty/resources.css @@ -21,132 +21,132 @@ * OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN * THE SOFTWARE. */ -.token-list{ - /* reset to get rid of browser default */ - margin: 0; - padding: 0; - - max-width: 700px; - border: 1px solid #cccccc; - border-color: var(--medium-grey); - border-radius: 3px; -} +.token-list { + /* reset to get rid of browser default */ + margin: 0; + padding: 0; + + max-width: 700px; + border: 1px solid #cccccc; + border-color: var(--medium-grey); + border-radius: 3px; +} .token-list .token-list-item { - min-height: inherit; - padding: 8px 10px; - font-size: 0.875rem; - line-height: 26px; + min-height: inherit; + padding: 8px 10px; + font-size: 0.875rem; + line-height: 26px; } .token-list .token-list-item.legacy-token { - padding: 6px 5px 6px 5px; - border: 2px solid #ffe262; - border-left-width: 5px; - border-right-width: 5px; + padding: 6px 5px 6px 5px; + border: 2px solid #ffe262; + border-left-width: 5px; + border-right-width: 5px; } .token-list .token-list-empty-item { - display: block; + display: block; } .token-list .token-list-empty-item.hidden-message { - display: none; + display: none; } -.token-list .token-list-item .token-name-input{ - font-weight: bold; +.token-list .token-list-item .token-name-input { + font-weight: bold; } -.token-list .token-list-item .token-creation{ - margin-left: 5px; - font-size: 0.75rem; +.token-list .token-list-item .token-creation { + margin-left: 5px; + font-size: 0.75rem; } -.token-list .token-list-item .token-creation.age-ok{ - color: #6d7680; +.token-list .token-list-item .token-creation.age-ok { + color: #6d7680; } -.token-list .token-list-item .token-creation.age-mmmh{ - color: #e09307; +.token-list .token-list-item .token-creation.age-mmmh { + color: #e09307; } -.token-list .token-list-item .token-creation.age-argh{ - color: #de6868; +.token-list .token-list-item .token-creation.age-argh { + color: #de6868; } -.token-list .token-list-item .token-hide{ - display: none; +.token-list .token-list-item .token-hide { + display: none; } -.token-list .token-list-item .to-right{ - float: right; +.token-list .token-list-item .to-right { + float: right; } -.token-list .token-list-item .token-use-counter{ - font-size: 0.75rem; - color: #6d7680; +.token-list .token-list-item .token-use-counter { + font-size: 0.75rem; + color: #6d7680; } -.token-list .token-list-item .no-statistics{ - font-size: 0.75rem; - color: #6d7680; +.token-list .token-list-item .no-statistics { + font-size: 0.75rem; + color: #6d7680; } -.token-list .token-list-item .token-revoke{ - margin-left: 6px; +.token-list .token-list-item .token-revoke { + margin-left: 6px; } -.token-list .token-list-new-item .token-revoke{ - float: right; - line-height: 32px; +.token-list .token-list-new-item .token-revoke { + float: right; + line-height: 32px; } -.token-list .token-list-new-item .token-revoke.hidden-button{ - display: none; +.token-list .token-list-new-item .token-revoke.hidden-button { + display: none; } -.token-list .token-list-new-item .token-cancel.hidden-button{ - display: none; +.token-list .token-list-new-item .token-cancel.hidden-button { + display: none; } -.token-list .token-list-new-item .token-cancel .yui-button{ - vertical-align: baseline; +.token-list .token-list-new-item .token-cancel .yui-button { + vertical-align: baseline; } -.token-list .token-list-new-item .token-name{ - width: 40%; - display: inline-block; +.token-list .token-list-new-item .token-name { + width: 40%; + display: inline-block; } -.token-list .token-list-new-item .new-token-value{ - width: 40%; - display: none; - font-family: monospace; - margin-right: 2px; - font-size: 1em; +.token-list .token-list-new-item .new-token-value { + width: 40%; + display: none; + font-family: monospace; + margin-right: 2px; + font-size: 1em; } -.token-list .token-list-new-item .new-token-value.visible{ - display: inline-block; +.token-list .token-list-new-item .new-token-value.visible { + display: inline-block; } -.token-list .token-list-new-item .copy-button{ - float: right; +.token-list .token-list-new-item .copy-button { + float: right; } .token-list .token-revoke svg { - width: 18px; - vertical-align: middle; + width: 18px; + vertical-align: middle; } -#jenkins .token-list .token-list-new-item .copy-button .yui-button{ - vertical-align: middle; +#jenkins .token-list .token-list-new-item .copy-button .yui-button { + vertical-align: middle; } -#jenkins .token-list .token-list-new-item .copy-button button{ - margin-left: 6px; +#jenkins .token-list .token-list-new-item .copy-button button { + margin-left: 6px; } -.token-list .token-list-new-item .display-after-generation{ - margin-top: 5px; - display: none; +.token-list .token-list-new-item .display-after-generation { + margin-top: 5px; + display: none; } -.token-list .token-list-new-item .display-after-generation.visible{ - display: block; +.token-list .token-list-new-item .display-after-generation.visible { + display: block; } -.token-list .token-list-new-item .token-error-message{ - margin-top: 5px; - display: none; +.token-list .token-list-new-item .token-error-message { + margin-top: 5px; + display: none; } -.token-list .token-list-new-item .token-error-message.visible{ - display: block; +.token-list .token-list-new-item .token-error-message.visible { + display: block; } -.token-list .token-list-new-item .token-save{ - vertical-align: baseline; +.token-list .token-list-new-item .token-save { + vertical-align: baseline; } .token-list .repeated-chunk { - border-width: 0; - padding: 0; - margin: 0; + border-width: 0; + padding: 0; + margin: 0; +} +.token-list .repeatable-add { + margin: 6px 6px 3px 6px; } -.token-list .repeatable-add{ - margin: 6px 6px 3px 6px; -} \ No newline at end of file diff --git a/core/src/main/resources/jenkins/security/ApiTokenProperty/resources.js b/core/src/main/resources/jenkins/security/ApiTokenProperty/resources.js index 3a80cb6590..fb6b8aef4a 100644 --- a/core/src/main/resources/jenkins/security/ApiTokenProperty/resources.js +++ b/core/src/main/resources/jenkins/security/ApiTokenProperty/resources.js @@ -21,114 +21,119 @@ * OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN * THE SOFTWARE. */ -function revokeToken(anchorRevoke){ - var repeatedChunk = anchorRevoke.up('.repeated-chunk'); - var tokenList = repeatedChunk.up('.token-list'); - var confirmMessage = anchorRevoke.getAttribute('data-confirm'); - var targetUrl = anchorRevoke.getAttribute('data-target-url'); - - var inputUuid = repeatedChunk.querySelector('input.token-uuid-input'); - var tokenUuid = inputUuid.value; - - if(confirm(confirmMessage)){ - new Ajax.Request(targetUrl, { - method: "post", - parameters: {tokenUuid: tokenUuid}, - onSuccess: function(rsp,_) { - if(repeatedChunk.querySelectorAll('.legacy-token').length > 0){ - // we are revoking the legacy token - var messageIfLegacyRevoked = anchorRevoke.getAttribute('data-message-if-legacy-revoked'); - - var legacyInput = document.getElementById('apiToken'); - legacyInput.value = messageIfLegacyRevoked; - } - repeatedChunk.remove(); - adjustTokenEmptyListMessage(tokenList); - - } - }); - } +function revokeToken(anchorRevoke) { + var repeatedChunk = anchorRevoke.up(".repeated-chunk"); + var tokenList = repeatedChunk.up(".token-list"); + var confirmMessage = anchorRevoke.getAttribute("data-confirm"); + var targetUrl = anchorRevoke.getAttribute("data-target-url"); - return false; -} + var inputUuid = repeatedChunk.querySelector("input.token-uuid-input"); + var tokenUuid = inputUuid.value; -function saveApiToken(button){ - if(button.hasClassName('request-pending')){ - // avoid multiple requests to be sent if user is clicking multiple times - return; - } - button.addClassName('request-pending'); - var targetUrl = button.getAttribute('data-target-url'); - var repeatedChunk = button.up('.repeated-chunk '); - var tokenList = repeatedChunk.up('.token-list'); - var nameInput = repeatedChunk.querySelector('[name="tokenName"]'); - var tokenName = nameInput.value; - + if (confirm(confirmMessage)) { new Ajax.Request(targetUrl, { - method: "post", - parameters: {"newTokenName": tokenName}, - onSuccess: function(rsp,_) { - var json = rsp.responseJSON; - var errorSpan = repeatedChunk.querySelector('.error'); - if(json.status === 'error'){ - errorSpan.innerHTML = json.message; - errorSpan.addClassName('visible'); - - button.removeClassName('request-pending'); - }else{ - errorSpan.removeClassName('visible'); - - var tokenName = json.data.tokenName; - // in case the name was empty, the application will propose a default one - nameInput.value = tokenName; - - var tokenValue = json.data.tokenValue; - var tokenValueSpan = repeatedChunk.querySelector('.new-token-value'); - tokenValueSpan.innerText = tokenValue; - tokenValueSpan.addClassName('visible'); - - // show the copy button - var tokenCopyButton = repeatedChunk.querySelector('.copy-button'); - tokenCopyButton.setAttribute('text', tokenValue); - tokenCopyButton.removeClassName('invisible') - tokenCopyButton.addClassName('visible'); - - var tokenUuid = json.data.tokenUuid; - var uuidInput = repeatedChunk.querySelector('[name="tokenUuid"]'); - uuidInput.value = tokenUuid; - - var warningMessage = repeatedChunk.querySelector('.display-after-generation'); - warningMessage.addClassName('visible'); - - // we do not want to allow user to create twice a token using same name by mistake - button.remove(); - - var revokeButton = repeatedChunk.querySelector('.token-revoke'); - revokeButton.removeClassName('hidden-button'); - - var cancelButton = repeatedChunk.querySelector('.token-cancel'); - cancelButton.addClassName('hidden-button') - - repeatedChunk.addClassName('token-list-fresh-item'); - - adjustTokenEmptyListMessage(tokenList); - } + method: "post", + parameters: { tokenUuid: tokenUuid }, + onSuccess: function (rsp, _) { + if (repeatedChunk.querySelectorAll(".legacy-token").length > 0) { + // we are revoking the legacy token + var messageIfLegacyRevoked = anchorRevoke.getAttribute( + "data-message-if-legacy-revoked" + ); + + var legacyInput = document.getElementById("apiToken"); + legacyInput.value = messageIfLegacyRevoked; } + repeatedChunk.remove(); + adjustTokenEmptyListMessage(tokenList); + }, }); + } + + return false; } -function adjustTokenEmptyListMessage(tokenList){ - var emptyListMessage = tokenList.querySelector('.token-list-empty-item'); +function saveApiToken(button) { + if (button.hasClassName("request-pending")) { + // avoid multiple requests to be sent if user is clicking multiple times + return; + } + button.addClassName("request-pending"); + var targetUrl = button.getAttribute("data-target-url"); + var repeatedChunk = button.up(".repeated-chunk "); + var tokenList = repeatedChunk.up(".token-list"); + var nameInput = repeatedChunk.querySelector('[name="tokenName"]'); + var tokenName = nameInput.value; - // number of token that are already existing or freshly created - var numOfToken = tokenList.querySelectorAll('.token-list-existing-item, .token-list-fresh-item').length; - if(numOfToken >= 1){ - if(!emptyListMessage.hasClassName('hidden-message')){ - emptyListMessage.addClassName('hidden-message'); - } - }else{ - if(emptyListMessage.hasClassName('hidden-message')){ - emptyListMessage.removeClassName('hidden-message'); - } + new Ajax.Request(targetUrl, { + method: "post", + parameters: { newTokenName: tokenName }, + onSuccess: function (rsp, _) { + var json = rsp.responseJSON; + var errorSpan = repeatedChunk.querySelector(".error"); + if (json.status === "error") { + errorSpan.innerHTML = json.message; + errorSpan.addClassName("visible"); + + button.removeClassName("request-pending"); + } else { + errorSpan.removeClassName("visible"); + + var tokenName = json.data.tokenName; + // in case the name was empty, the application will propose a default one + nameInput.value = tokenName; + + var tokenValue = json.data.tokenValue; + var tokenValueSpan = repeatedChunk.querySelector(".new-token-value"); + tokenValueSpan.innerText = tokenValue; + tokenValueSpan.addClassName("visible"); + + // show the copy button + var tokenCopyButton = repeatedChunk.querySelector(".copy-button"); + tokenCopyButton.setAttribute("text", tokenValue); + tokenCopyButton.removeClassName("invisible"); + tokenCopyButton.addClassName("visible"); + + var tokenUuid = json.data.tokenUuid; + var uuidInput = repeatedChunk.querySelector('[name="tokenUuid"]'); + uuidInput.value = tokenUuid; + + var warningMessage = repeatedChunk.querySelector( + ".display-after-generation" + ); + warningMessage.addClassName("visible"); + + // we do not want to allow user to create twice a token using same name by mistake + button.remove(); + + var revokeButton = repeatedChunk.querySelector(".token-revoke"); + revokeButton.removeClassName("hidden-button"); + + var cancelButton = repeatedChunk.querySelector(".token-cancel"); + cancelButton.addClassName("hidden-button"); + + repeatedChunk.addClassName("token-list-fresh-item"); + + adjustTokenEmptyListMessage(tokenList); + } + }, + }); +} + +function adjustTokenEmptyListMessage(tokenList) { + var emptyListMessage = tokenList.querySelector(".token-list-empty-item"); + + // number of token that are already existing or freshly created + var numOfToken = tokenList.querySelectorAll( + ".token-list-existing-item, .token-list-fresh-item" + ).length; + if (numOfToken >= 1) { + if (!emptyListMessage.hasClassName("hidden-message")) { + emptyListMessage.addClassName("hidden-message"); + } + } else { + if (emptyListMessage.hasClassName("hidden-message")) { + emptyListMessage.removeClassName("hidden-message"); } + } } diff --git a/core/src/main/resources/jenkins/security/ResourceDomainConfiguration/help-url.html b/core/src/main/resources/jenkins/security/ResourceDomainConfiguration/help-url.html index 602ef4fc43..057e026cd1 100644 --- a/core/src/main/resources/jenkins/security/ResourceDomainConfiguration/help-url.html +++ b/core/src/main/resources/jenkins/security/ResourceDomainConfiguration/help-url.html @@ -1,51 +1,95 @@

- Jenkins serves many files that are potentially created by untrusted users, such as files in project workspaces or archived artifacts. - When no resource root URL is defined, Jenkins will serve these files with the HTTP header Content-Security-Policy ("CSP"). - By default it is set to a value that disables many modern web features to prevent cross-site scripting (XSS) and other attacks on Jenkins users accessing these files. - While the specific value for the CSP header is user configurable (and can even be disabled), doing so is a trade-off between security and functionality. + Jenkins serves many files that are potentially created by untrusted users, + such as files in project workspaces or archived artifacts. When no resource + root URL is defined, Jenkins will serve these files with the HTTP header + Content-Security-Policy + ("CSP"). By default it is set to a value that disables many modern web + features to prevent cross-site scripting (XSS) and other attacks on Jenkins + users accessing these files. While the specific value for the CSP header is + user configurable (and can even be disabled), doing so is a trade-off between + security and functionality.

- If the resource root URL is defined, Jenkins will instead redirect requests for user-created resource files to URLs starting with the URL configured here. - These URLs will not set the CSP header, allowing JavaScript and similar features to work. - For this option to work as expected, the following constraints and considerations apply: + If the resource root URL is defined, Jenkins will instead redirect requests + for user-created resource files to URLs starting with the URL configured here. + These URLs will not set the CSP header, allowing JavaScript and similar + features to work. For this option to work as expected, the following + constraints and considerations apply:

    -
  • The resource root URL must be a valid alternative choice for the Jenkins URL for requests to be processed correctly.
    • -
  • The Jenkins URL must be set and it must be different from this resource root URL (in fact, a different host name is required).
    • -
  • - Once set, Jenkins will only serve resource URL requests via the resource root URL. - All other requests will get HTTP 404 Not Found responses. -
    • +
  • + The resource root URL must be a valid alternative choice for the Jenkins URL + for requests to be processed correctly. +
    • +
  • + The Jenkins URL must be set and it must be different from this resource root + URL (in fact, a different host name is required). +
    • +
  • + Once set, Jenkins will only serve resource URL requests via the resource + root URL. All other requests will get + HTTP 404 Not Found + responses. +

- Once this URL has been set up correctly, Jenkins will redirect requests to workspaces, archived artifacts, and similar collections of usually user-generated content to URLs starting with the resource root URL. - Instead of a path like job/name_here/ws, resource URLs will contain a token encoding that path, the user for which the URL was created, and when it was created. - These resource URLs access static files as if the user for which they were created would access them: - If the user’s permission to access these files is removed, the corresponding resource URLs will not work anymore either. - These URLs are accessible to anyone without authentication until they expire, so sharing these URLs is akin to sharing the files directly. + Once this URL has been set up correctly, Jenkins will redirect requests to + workspaces, archived artifacts, and similar collections of usually + user-generated content to URLs starting with the resource root URL. Instead of + a path like + job/name_here/ws + , resource URLs will contain a token encoding that path, the user for which + the URL was created, and when it was created. These resource URLs access + static files + as if + the user for which they were created would access them: If the user’s + permission to access these files is removed, the corresponding resource URLs + will not work anymore either. + + These URLs are accessible to anyone without authentication until they + expire, so sharing these URLs is akin to sharing the files directly. +

Security considerations

Authentication

- Resource URLs do not require authentication (users will not have a valid session for the resource root URL). - Sharing a resource URL with another user, even one lacking Overall/Read permission for Jenkins, will grant that user access to these files until the URLs expire. + Resource URLs do not require authentication (users will not have a valid + session for the resource root URL). Sharing a resource URL with another user, + even one lacking Overall/Read permission for Jenkins, will grant that user + access to these files until the URLs expire.

Expiration

- Resource URLs expire after 30 minutes by default. - Expired resource URLs will redirect users to their equivalent Jenkins URLs, so that the user can reauthenticate, if necessary, and then be redirected back to a new resource URL that will be valid for another 30 minutes. - This will generally be transparent to the user if they have a valid Jenkins session. - Otherwise, they will need to authenticate with Jenkins again. - However, when browsing pages with HTML frames, like Javadoc sites, the login form cannot appear in a frame. - In these cases, users will need to reload the top-level frame to make the login form appear. + Resource URLs expire after 30 minutes by default. Expired resource URLs will + redirect users to their equivalent Jenkins URLs, so that the user can + reauthenticate, if necessary, and then be redirected back to a new resource + URL that will be valid for another 30 minutes. This will generally be + transparent to the user if they have a valid Jenkins session. Otherwise, they + will need to authenticate with Jenkins again. However, when browsing pages + with HTML frames, like Javadoc sites, the login form cannot appear in a frame. + In these cases, users will need to reload the top-level frame to make the + login form appear.

- To change how quickly resource URLs expire, set the system property jenkins.security.ResourceDomainRootAction.validForMinutes to the desired value in minutes. - Earlier expiration might make it harder to use these URLs, while later expiration increases the likelihood of unauthorized users gaining access through URLs shared with them by authorized users. + To change how quickly resource URLs expire, set the system property + jenkins.security.ResourceDomainRootAction.validForMinutes + to the desired value in minutes. Earlier expiration might make it harder to + use these URLs, while later expiration increases the likelihood of + unauthorized users gaining access through URLs shared with them by authorized + users.

Authenticity

- Resource URLs encode the URL, the user for which they were created, and their creation timestamp. - Additionally, this string contains an HMAC to ensure the authenticity of the URL. - This prevents attackers from forging URLs that would grant them access to resource files as if they were another user. + Resource URLs encode the URL, the user for which they were created, and their + creation timestamp. Additionally, this string contains an + + HMAC + + to ensure the authenticity of the URL. This prevents attackers from forging + URLs that would grant them access to resource files as if they were another + user.

diff --git a/core/src/main/resources/jenkins/security/ResourceDomainConfiguration/help-url_it.html b/core/src/main/resources/jenkins/security/ResourceDomainConfiguration/help-url_it.html index 8bf739aac8..acb7308429 100644 --- a/core/src/main/resources/jenkins/security/ResourceDomainConfiguration/help-url_it.html +++ b/core/src/main/resources/jenkins/security/ResourceDomainConfiguration/help-url_it.html @@ -1,51 +1,103 @@

- Jenkins serve molti file creati potenzialmente da utenti non affidabili, come file negli spazi di lavoro o artefatti archiviati. - Quando non è definito alcun URL radice risorse, Jenkins servirà tali file con l'intestazione HTTP Content-Security-Policy ("CSP"). - Per impostazione predefinita, è impostata a un valore che disabilita molte funzionalità Web moderne per prevenire attacchi cross-site scripting (XSS) e di altro tipo rivolti agli utenti Jenkins che accedono a tali file. - Il valore specifico per l'intestazione CSP è configurabile dall'utente (e può anche essere disabilitato), ma tale operazione è un compromesso fra sicurezza e funzionalità. + Jenkins serve molti file creati potenzialmente da utenti non affidabili, come + file negli spazi di lavoro o artefatti archiviati. Quando non è definito alcun + URL radice risorse, Jenkins servirà tali file con l'intestazione HTTP + Content-Security-Policy + ("CSP"). Per impostazione predefinita, è impostata a un valore che disabilita + molte funzionalità Web moderne per prevenire attacchi cross-site scripting + (XSS) e di altro tipo rivolti agli utenti Jenkins che accedono a tali file. Il + valore specifico per l'intestazione CSP è configurabile dall'utente (e può + anche essere disabilitato), ma tale operazione è un compromesso fra sicurezza + e funzionalità.

- Se l'URL radice delle risorse è definito, Jenkins redirigerà le richieste per i file di risorse creati dall'utente a URL che iniziano con l'URL configurato qui. - Per tali URL l'intestazione CSP non sarà impostata, il che consentirà a Javascript e a funzionalità simili di funzionare. - Affinché quest'opzione funzioni come desiderato, si applicano le seguenti restrizioni e considerazioni: + Se l'URL radice delle risorse è definito, Jenkins redirigerà le richieste per + i file di risorse creati dall'utente a URL che iniziano con l'URL configurato + qui. Per tali URL l'intestazione CSP non sarà impostata, il che consentirà a + Javascript e a funzionalità simili di funzionare. Affinché quest'opzione + funzioni come desiderato, si applicano le seguenti restrizioni e + considerazioni:

    -
  • L'URL radice delle risorse dev'essere un'alternativa valida all'URL radice di Jenkins affinché le richieste siano elaborate correttamente.
    • -
  • L'URL radice di Jenkins dev'essere impostato e dev'essere differente da quest'URL radice delle risorse (di fatto, è richiesto un nome host differente).
    • -
  • - Una volta impostata, Jenkins servirà le richieste per le URL risorse dall'URL radice delle risorse. - Tutte le altre richieste riceveranno una risposta HTTP 404 Not Found. -
    • +
  • + L'URL radice delle risorse dev'essere un'alternativa valida all'URL radice + di Jenkins affinché le richieste siano elaborate correttamente. +
    • +
  • + L'URL radice di Jenkins dev'essere impostato e dev'essere differente da + quest'URL radice delle risorse (di fatto, è richiesto un nome host + differente). +
    • +
  • + Una volta impostata, Jenkins servirà le richieste per le URL risorse + dall'URL radice delle risorse. Tutte le altre richieste riceveranno una + risposta + HTTP 404 Not Found + . +

- Una volta impostato correttamente quest'URL, Jenkins redirigerà le richieste agli spazi di lavoro, agli artefatti archiviati e a simili insiemi di contenuto solitamente generato dall'utente a URL che iniziano con l'URL radice delle risorse. - Anziché un percorso del tipo job/NOME/ws, gli URL risorse conterranno un token che codifica tale percorso, l'utente per cui è stato creato l'URL e quando è stato creato. - Tali URL risorse consentono di accedere a file statici con le credenziali dell'utente per cui sono stati creati: - se viene rimosso il permesso dell'utente di accedere a tali file, nemmeno gli URL risorse corrispondenti funzioneranno più. - Tali URL sono accessibili a chiunque senza autenticazione fino alla loro scadenza, per cui condividere tali URL equivale a condividere direttamente i file. + Una volta impostato correttamente quest'URL, Jenkins redirigerà le richieste + agli spazi di lavoro, agli artefatti archiviati e a simili insiemi di + contenuto solitamente generato dall'utente a URL che iniziano con l'URL radice + delle risorse. Anziché un percorso del tipo + job/NOME/ws + , gli URL risorse conterranno un token che codifica tale percorso, l'utente + per cui è stato creato l'URL e quando è stato creato. Tali URL risorse + consentono di accedere a file statici + con le credenziali + dell'utente per cui sono stati creati: se viene rimosso il permesso + dell'utente di accedere a tali file, nemmeno gli URL risorse corrispondenti + funzioneranno più. + + Tali URL sono accessibili a chiunque senza autenticazione fino alla loro + scadenza, per cui condividere tali URL equivale a condividere direttamente i + file. +

Considerazioni di sicurezza

Autenticazione

- Gli URL risorse non richiedono l'autenticazione (gli utenti non avranno una sessione valida per l'URL radice delle risorse). - La condivisione di un URL risorse con un altro utente, anche con uno che non ha il permesso Jenkins Generale/Lettura, consentirà a tale utente di accedere a tali file fino alla scadenza degli URL. + Gli URL risorse non richiedono l'autenticazione (gli utenti non avranno una + sessione valida per l'URL radice delle risorse). La condivisione di un URL + risorse con un altro utente, anche con uno che non ha il permesso Jenkins + Generale/Lettura, consentirà a tale utente di accedere a tali file fino alla + scadenza degli URL.

Scadenza

- Gli URL risorse, per impostazione predefinita, scadono dopo 30 minuti. - Gli URL risorse scaduti redirigeranno gli utenti agli URL Jenkins equivalenti in modo che l'utente possa autenticarsi nuovamente, se necessario, e quindi essere rediretto a un nuovo URL risorsa che sarà valido per altri 30 minuti. - Ciò in generale sarà trasparente per l'utente se hanno una sessione Jenkins valida. - In caso contrario, dovranno autenticarsi nuovamente su Jenkins. - Ciò nonostante, quando si naviga in una pagina con frame HTML, come siti Javadoc, la schermata di accesso non può apparire in un frame. - In tali casi, gli utenti dovranno aggiornare il frame principale per far apparire la schermata di accesso. + Gli URL risorse, per impostazione predefinita, scadono dopo 30 minuti. Gli URL + risorse scaduti redirigeranno gli utenti agli URL Jenkins equivalenti in modo + che l'utente possa autenticarsi nuovamente, se necessario, e quindi essere + rediretto a un nuovo URL risorsa che sarà valido per altri 30 minuti. Ciò in + generale sarà trasparente per l'utente se hanno una sessione Jenkins valida. + In caso contrario, dovranno autenticarsi nuovamente su Jenkins. Ciò + nonostante, quando si naviga in una pagina con frame HTML, come siti Javadoc, + la schermata di accesso non può apparire in un frame. In tali casi, gli utenti + dovranno aggiornare il frame principale per far apparire la schermata di + accesso.

- Per modificare il tempo di scadenza degli URL risorse, impostare la proprietà di sistema jenkins.security.ResourceDomainRootAction.validForMinutes al valore desiderato in minuti. - Un valore minore potrebbe rendere più difficile utilizzare tali URL, mentre un valore maggiore aumenta la possibilità che utenti non autorizzati ottengano l'accesso tramite URL condivisi con loro da utenti autorizzati. + Per modificare il tempo di scadenza degli URL risorse, impostare la proprietà + di sistema + jenkins.security.ResourceDomainRootAction.validForMinutes + al valore desiderato in minuti. Un valore minore potrebbe rendere più + difficile utilizzare tali URL, mentre un valore maggiore aumenta la + possibilità che utenti non autorizzati ottengano l'accesso tramite URL + condivisi con loro da utenti autorizzati.

Autenticità

- Gli URL risorse codificano l'URL, l'utente per cui sono stati creati e data e ora della loro creazione. - Inoltre, questa stringa contiene un HMAC per garantire l'autenticità dell'URL. - Ciò impedisce a un attaccante di falsificare URL che gli consentirebbero l'accesso a file di risorse con le credenziali di un altro utente. + Gli URL risorse codificano l'URL, l'utente per cui sono stati creati e data e + ora della loro creazione. Inoltre, questa stringa contiene un + + HMAC + + per garantire l'autenticità dell'URL. Ciò impedisce a un attaccante di + falsificare URL che gli consentirebbero l'accesso a file di risorse con le + credenziali di un altro utente.

diff --git a/core/src/main/resources/jenkins/security/UpdateSiteWarningsConfiguration/help.html b/core/src/main/resources/jenkins/security/UpdateSiteWarningsConfiguration/help.html index 1cb7b1df5d..5649ddff01 100644 --- a/core/src/main/resources/jenkins/security/UpdateSiteWarningsConfiguration/help.html +++ b/core/src/main/resources/jenkins/security/UpdateSiteWarningsConfiguration/help.html @@ -1,14 +1,24 @@

- This list contains all warnings relevant to currently installed components published by the configured update sites. - These are typically security-related. - Warnings that have been published but are not relevant to currently installed components (either because the affected component isn't installed, or an unaffected version is installed) are not shown here. + This list contains all warnings relevant to currently installed components + published by the configured update sites. These are typically + security-related. Warnings that have been published but are not relevant to + currently installed components (either because the affected component isn't + installed, or an unaffected version is installed) are not shown here.

- Checked entries (the default) are active, i.e. they're shown to administrators in an administrative monitor. - Entries can be unchecked to hide them. - This can be useful if you've evaluated a specific warning and are confident it does not apply to your environment or configuration, and continued use of the specified component does not constitute a security problem. + Checked entries (the default) are + active + , i.e. they're shown to administrators in an administrative monitor. Entries + can be unchecked to hide them. This can be useful if you've evaluated a + specific warning and are confident it does not apply to your environment or + configuration, and continued use of the specified component does not + constitute a security problem.

- Please note that only specific warnings can be disabled; it is not possible to disable all warnings about a certain component. - If you wish to disable the display of warnings entirely, then you can disable the administrative monitor in Configure System. + Please note that only specific warnings can be disabled; it is not possible to + disable all warnings about a certain component. If you wish to disable the + display of warnings entirely, then you can disable the administrative monitor + in + Configure System + .

diff --git a/core/src/main/resources/jenkins/security/UpdateSiteWarningsConfiguration/help_bg.html b/core/src/main/resources/jenkins/security/UpdateSiteWarningsConfiguration/help_bg.html index 722ab9cbe2..acb2b3b11c 100644 --- a/core/src/main/resources/jenkins/security/UpdateSiteWarningsConfiguration/help_bg.html +++ b/core/src/main/resources/jenkins/security/UpdateSiteWarningsConfiguration/help_bg.html @@ -1,15 +1,23 @@

- Този списък съдържа всички предупреждиния, които се отнасят до текущо инсталираните компоненти, които - са публикувани от текущо настроените сайтове за обновления. Стандартно новините са свързани с проблими - със сигурноста. Не се показват публикуваните предупреждения, които не се за текущо инсталираните - компоненти и версии. + Този списък съдържа всички предупреждиния, които се отнасят до текущо + инсталираните компоненти, които са публикувани от текущо настроените сайтове + за обновления. Стандартно новините са свързани с проблими със сигурноста. Не + се показват публикуваните предупреждения, които не се за текущо инсталираните + компоненти и версии.

- Стандартно отделине предупреждения са избрани/активни, т.е. те се показват на администраторите. - Като махнете отметката ги криете. - Това е полезно, ако сте разгледали определено предупреждение и сте сигурни, че не се отнася за вашата инсталация и - настройки, т.е. да продължите да ползвате съответната версия на определен компонент не е пробив в сигурността. + Стандартно отделине предупреждения са + избрани/активни + , т.е. те се показват на администраторите. Като махнете отметката ги криете. + Това е полезно, ако сте разгледали определено предупреждение и сте сигурни, че + не се отнася за вашата инсталация и настройки, т.е. да продължите да ползвате + съответната версия на определен компонент не е пробив в сигурността. +

+

- Предупрежденията могат да се изключват едно по едно, не може да заглушите всички предупреждения за определен компонент. - Ако искате въобще да изключите показването на всички предупреждения, може да направите това от Настройките на системата. + Предупрежденията могат да се изключват едно по едно, не може да заглушите + всички предупреждения за определен компонент. Ако искате въобще да изключите + показването на всички предупреждения, може да направите това от + Настройките на системата + .

diff --git a/core/src/main/resources/jenkins/security/UpdateSiteWarningsConfiguration/help_it.html b/core/src/main/resources/jenkins/security/UpdateSiteWarningsConfiguration/help_it.html index f29ff080e7..3452389da3 100644 --- a/core/src/main/resources/jenkins/security/UpdateSiteWarningsConfiguration/help_it.html +++ b/core/src/main/resources/jenkins/security/UpdateSiteWarningsConfiguration/help_it.html @@ -1,14 +1,25 @@

- Quest'elenco contiene tutti gli avvisi rilevanti per i componenti attualmente installati e pubblicati dai siti di aggiornamento configurati. - Tali avvisi tipicamente sono legati alla sicurezza. - Gli avvisi pubblicati ma non rilevanti per i componenti attualmente installati (perché il componente affetto non è installato o perché ne è installata una versione non affetta) non vengono visualizzati qui. + Quest'elenco contiene tutti gli avvisi rilevanti per i componenti attualmente + installati e pubblicati dai siti di aggiornamento configurati. Tali avvisi + tipicamente sono legati alla sicurezza. Gli avvisi pubblicati ma non rilevanti + per i componenti attualmente installati (perché il componente affetto non è + installato o perché ne è installata una versione non affetta) non vengono + visualizzati qui.

- Le voci selezionate (impostazione predefinita) sono attive, ossia sono visualizzate agli amministratori in un monitor amministrativo. - Le voci possono essere deselezionate per nasconderle. - Ciò può essere utile se si è valutato l'impatto di uno specifico avviso e se si è certi che non si applichi al proprio ambiente o configurazione, e che l'utilizzo continuativo del componente specificato non rappresenti un problema di sicurezza. + Le voci selezionate (impostazione predefinita) sono + attive + , ossia sono visualizzate agli amministratori in un monitor amministrativo. Le + voci possono essere deselezionate per nasconderle. Ciò può essere utile se si + è valutato l'impatto di uno specifico avviso e se si è certi che non si + applichi al proprio ambiente o configurazione, e che l'utilizzo continuativo + del componente specificato non rappresenti un problema di sicurezza.

- Si noti che è possibile disabilitare solo degli avvisi specifici; non è possibile disabilitare tutti gli avvisi per un determinato componente. - Se si desidera disabilitare completamente la visualizzazione degli avvisi, è possibile disabilitare il monitor amministrativo nella sezione Configura sistema. + Si noti che è possibile disabilitare solo degli avvisi specifici; non è + possibile disabilitare tutti gli avvisi per un determinato componente. Se si + desidera disabilitare completamente la visualizzazione degli avvisi, è + possibile disabilitare il monitor amministrativo nella sezione + Configura sistema + .

diff --git a/core/src/main/resources/jenkins/security/apitoken/ApiTokenPropertyConfiguration/help-creationOfLegacyTokenEnabled.html b/core/src/main/resources/jenkins/security/apitoken/ApiTokenPropertyConfiguration/help-creationOfLegacyTokenEnabled.html index 761f0f521a..28a33aee2a 100644 --- a/core/src/main/resources/jenkins/security/apitoken/ApiTokenPropertyConfiguration/help-creationOfLegacyTokenEnabled.html +++ b/core/src/main/resources/jenkins/security/apitoken/ApiTokenPropertyConfiguration/help-creationOfLegacyTokenEnabled.html @@ -1,5 +1,7 @@
- This option allows users to generate a legacy API token if they do not already have one. - Because legacy tokens are deprecated, we recommend disabling it and having users instead generate - new API tokens from the user configuration page. + This option allows users to generate a legacy API token if they do not already + have one. Because legacy tokens are + deprecated + , we recommend disabling it and having users instead generate new API tokens + from the user configuration page.
diff --git a/core/src/main/resources/jenkins/security/apitoken/ApiTokenPropertyConfiguration/help-creationOfLegacyTokenEnabled_it.html b/core/src/main/resources/jenkins/security/apitoken/ApiTokenPropertyConfiguration/help-creationOfLegacyTokenEnabled_it.html index 0767deec3c..3ec0ae8426 100644 --- a/core/src/main/resources/jenkins/security/apitoken/ApiTokenPropertyConfiguration/help-creationOfLegacyTokenEnabled_it.html +++ b/core/src/main/resources/jenkins/security/apitoken/ApiTokenPropertyConfiguration/help-creationOfLegacyTokenEnabled_it.html @@ -1,7 +1,7 @@
Quest'opzione consente agli utenti di generare un token API legacy se non ne possiedono già uno. Dal momento che i token legacy sono - deprecati, raccomandiamo la sua disabilitazione e - consigliamo agli utenti di generare nuovi token API dalla pagina di - configurazione utente. + deprecati + , raccomandiamo la sua disabilitazione e consigliamo agli utenti di generare + nuovi token API dalla pagina di configurazione utente.
diff --git a/core/src/main/resources/jenkins/security/apitoken/ApiTokenPropertyConfiguration/help-tokenGenerationOnCreationEnabled.html b/core/src/main/resources/jenkins/security/apitoken/ApiTokenPropertyConfiguration/help-tokenGenerationOnCreationEnabled.html index f56b1a1d61..16edd5d5c1 100644 --- a/core/src/main/resources/jenkins/security/apitoken/ApiTokenPropertyConfiguration/help-tokenGenerationOnCreationEnabled.html +++ b/core/src/main/resources/jenkins/security/apitoken/ApiTokenPropertyConfiguration/help-tokenGenerationOnCreationEnabled.html @@ -1,5 +1,7 @@
- This option causes a legacy API token to be generated automatically for newly created users. - Because legacy tokens are deprecated, we recommend disabling it and having users instead generate - new API tokens from the user configuration page as needed. + This option causes a legacy API token to be generated automatically for newly + created users. Because legacy tokens are + deprecated + , we recommend disabling it and having users instead generate new API tokens + from the user configuration page as needed.
diff --git a/core/src/main/resources/jenkins/security/apitoken/ApiTokenPropertyConfiguration/help-tokenGenerationOnCreationEnabled_it.html b/core/src/main/resources/jenkins/security/apitoken/ApiTokenPropertyConfiguration/help-tokenGenerationOnCreationEnabled_it.html index aac2fa7b6f..d266d8eb38 100644 --- a/core/src/main/resources/jenkins/security/apitoken/ApiTokenPropertyConfiguration/help-tokenGenerationOnCreationEnabled_it.html +++ b/core/src/main/resources/jenkins/security/apitoken/ApiTokenPropertyConfiguration/help-tokenGenerationOnCreationEnabled_it.html @@ -1,7 +1,7 @@
Quest'opzione fa sì che per gli utenti di nuova creazione venga generato automaticamente un token API legacy. Dal momento che i token legacy sono - deprecati, raccomandiamo la sua disabilitazione e - consigliamo agli utenti di generare nuovi token API dalla pagina di - configurazione utente se necessario. + deprecati + , raccomandiamo la sua disabilitazione e consigliamo agli utenti di generare + nuovi token API dalla pagina di configurazione utente se necessario.
diff --git a/core/src/main/resources/jenkins/security/apitoken/ApiTokenPropertyConfiguration/help-usageStatisticsEnabled.html b/core/src/main/resources/jenkins/security/apitoken/ApiTokenPropertyConfiguration/help-usageStatisticsEnabled.html index cf5baf744d..bc525a172b 100644 --- a/core/src/main/resources/jenkins/security/apitoken/ApiTokenPropertyConfiguration/help-usageStatisticsEnabled.html +++ b/core/src/main/resources/jenkins/security/apitoken/ApiTokenPropertyConfiguration/help-usageStatisticsEnabled.html @@ -1,8 +1,10 @@
- If this option is enabled, then the date of the most recent use of each API token and the total number of times - it has been used are stored in Jenkins. - This allows users to see if they have unused or outdated API tokens which should be revoked. -
- - This data is stored in your Jenkins instance and will not be used for any other purpose. + If this option is enabled, then the date of the most recent use of each API + token and the total number of times it has been used are stored in Jenkins. + This allows users to see if they have unused or outdated API tokens which + should be revoked. +
+ + This data is stored in your Jenkins instance and will not be used for any + other purpose.
diff --git a/core/src/main/resources/jenkins/security/apitoken/ApiTokenPropertyConfiguration/help-usageStatisticsEnabled_it.html b/core/src/main/resources/jenkins/security/apitoken/ApiTokenPropertyConfiguration/help-usageStatisticsEnabled_it.html index 7df1cfdca4..aa71ef450e 100644 --- a/core/src/main/resources/jenkins/security/apitoken/ApiTokenPropertyConfiguration/help-usageStatisticsEnabled_it.html +++ b/core/src/main/resources/jenkins/security/apitoken/ApiTokenPropertyConfiguration/help-usageStatisticsEnabled_it.html @@ -1,9 +1,8 @@
Se quest'opzione è abilitata, verranno salvati in Jenkins la data - dell'utilizzo più recente di ogni token API e il numero totale di volte in - cui questo è stato utilizzato. - Ciò consente agli utenti di vedere se hanno dei token API non utilizzati od - obsoleti che dovrebbero essere revocati. + dell'utilizzo più recente di ogni token API e il numero totale di volte in cui + questo è stato utilizzato. Ciò consente agli utenti di vedere se hanno dei + token API non utilizzati od obsoleti che dovrebbero essere revocati.
Questi dati sono salvati all'interno dell'istanza di Jenkins e non saranno diff --git a/core/src/main/resources/jenkins/security/apitoken/LegacyApiTokenAdministrativeMonitor/resources.css b/core/src/main/resources/jenkins/security/apitoken/LegacyApiTokenAdministrativeMonitor/resources.css index 1c1ffa94ea..29b69bedb4 100644 --- a/core/src/main/resources/jenkins/security/apitoken/LegacyApiTokenAdministrativeMonitor/resources.css +++ b/core/src/main/resources/jenkins/security/apitoken/LegacyApiTokenAdministrativeMonitor/resources.css @@ -22,31 +22,31 @@ * THE SOFTWARE. */ .legacy-token-usage table .no-token { - padding: 8px 12px; - font-style: italic; + padding: 8px 12px; + font-style: italic; } .legacy-token-usage table tr.selected { - background-color: #f9f8de; + background-color: #f9f8de; } -.legacy-token-usage .selection-panel{ - margin-top: 8px; +.legacy-token-usage .selection-panel { + margin-top: 8px; } -.legacy-token-usage .selection-panel .action{ - margin-left: 4px; - margin-right: 4px; - text-decoration: none; - color: #204A87; +.legacy-token-usage .selection-panel .action { + margin-left: 4px; + margin-right: 4px; + text-decoration: none; + color: #204a87; } -.legacy-token-usage .selection-panel .action:hover{ - text-decoration: underline; +.legacy-token-usage .selection-panel .action:hover { + text-decoration: underline; } -.legacy-token-usage .selection-panel .action:visited{ - /* avoid visited behavior */ - color: #204A87; +.legacy-token-usage .selection-panel .action:visited { + /* avoid visited behavior */ + color: #204a87; } -.legacy-token-usage .action-panel{ - margin-top: 8px; +.legacy-token-usage .action-panel { + margin-top: 8px; } diff --git a/core/src/main/resources/jenkins/security/apitoken/LegacyApiTokenAdministrativeMonitor/resources.js b/core/src/main/resources/jenkins/security/apitoken/LegacyApiTokenAdministrativeMonitor/resources.js index 31cedefeba..21bb3d903e 100644 --- a/core/src/main/resources/jenkins/security/apitoken/LegacyApiTokenAdministrativeMonitor/resources.js +++ b/core/src/main/resources/jenkins/security/apitoken/LegacyApiTokenAdministrativeMonitor/resources.js @@ -21,130 +21,139 @@ * OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN * THE SOFTWARE. */ -function selectAll(anchor){ - var parent = anchor.up('.legacy-token-usage'); - var allCheckBoxes = parent.querySelectorAll('.token-to-revoke'); - var concernedCheckBoxes = allCheckBoxes; - - checkTheDesiredOne(allCheckBoxes, concernedCheckBoxes); +function selectAll(anchor) { + var parent = anchor.up(".legacy-token-usage"); + var allCheckBoxes = parent.querySelectorAll(".token-to-revoke"); + var concernedCheckBoxes = allCheckBoxes; + + checkTheDesiredOne(allCheckBoxes, concernedCheckBoxes); } -function selectFresh(anchor){ - var parent = anchor.up('.legacy-token-usage'); - var allCheckBoxes = parent.querySelectorAll('.token-to-revoke'); - var concernedCheckBoxes = parent.querySelectorAll('.token-to-revoke.fresh-token'); - - checkTheDesiredOne(allCheckBoxes, concernedCheckBoxes); +function selectFresh(anchor) { + var parent = anchor.up(".legacy-token-usage"); + var allCheckBoxes = parent.querySelectorAll(".token-to-revoke"); + var concernedCheckBoxes = parent.querySelectorAll( + ".token-to-revoke.fresh-token" + ); + + checkTheDesiredOne(allCheckBoxes, concernedCheckBoxes); } -function selectRecent(anchor){ - var parent = anchor.up('.legacy-token-usage'); - var allCheckBoxes = parent.querySelectorAll('.token-to-revoke'); - var concernedCheckBoxes = parent.querySelectorAll('.token-to-revoke.recent-token'); - - checkTheDesiredOne(allCheckBoxes, concernedCheckBoxes); +function selectRecent(anchor) { + var parent = anchor.up(".legacy-token-usage"); + var allCheckBoxes = parent.querySelectorAll(".token-to-revoke"); + var concernedCheckBoxes = parent.querySelectorAll( + ".token-to-revoke.recent-token" + ); + + checkTheDesiredOne(allCheckBoxes, concernedCheckBoxes); } -function checkTheDesiredOne(allCheckBoxes, concernedCheckBoxes){ - var mustCheck = false; - for(var i = 0; i < concernedCheckBoxes.length && !mustCheck ; i++){ - var checkBox = concernedCheckBoxes[i]; - if(!checkBox.checked){ - mustCheck = true; - } - } - - for(var i = 0; i < allCheckBoxes.length ; i++){ - var checkBox = allCheckBoxes[i]; - checkBox.checked = false; - } - - for(var i = 0; i < concernedCheckBoxes.length ; i++){ - var checkBox = concernedCheckBoxes[i]; - checkBox.checked = mustCheck; - } - - for(var i = 0; i < allCheckBoxes.length ; i++){ - var checkBox = allCheckBoxes[i]; - onCheckChanged(checkBox); +function checkTheDesiredOne(allCheckBoxes, concernedCheckBoxes) { + var mustCheck = false; + for (var i = 0; i < concernedCheckBoxes.length && !mustCheck; i++) { + var checkBox = concernedCheckBoxes[i]; + if (!checkBox.checked) { + mustCheck = true; } + } + + for (var i = 0; i < allCheckBoxes.length; i++) { + var checkBox = allCheckBoxes[i]; + checkBox.checked = false; + } + + for (var i = 0; i < concernedCheckBoxes.length; i++) { + var checkBox = concernedCheckBoxes[i]; + checkBox.checked = mustCheck; + } + + for (var i = 0; i < allCheckBoxes.length; i++) { + var checkBox = allCheckBoxes[i]; + onCheckChanged(checkBox); + } } -function confirmAndRevokeAllSelected(button){ - var parent = button.up('.legacy-token-usage'); - var allCheckBoxes = parent.querySelectorAll('.token-to-revoke'); - var allCheckedCheckBoxes = []; - for(var i = 0; i < allCheckBoxes.length ; i++){ - var checkBox = allCheckBoxes[i]; - if(checkBox.checked){ - allCheckedCheckBoxes.push(checkBox); - } +function confirmAndRevokeAllSelected(button) { + var parent = button.up(".legacy-token-usage"); + var allCheckBoxes = parent.querySelectorAll(".token-to-revoke"); + var allCheckedCheckBoxes = []; + for (var i = 0; i < allCheckBoxes.length; i++) { + var checkBox = allCheckBoxes[i]; + if (checkBox.checked) { + allCheckedCheckBoxes.push(checkBox); } - - if(allCheckedCheckBoxes.length == 0){ - var nothingSelected = button.getAttribute('data-nothing-selected'); - alert(nothingSelected); - }else{ - var confirmMessageTemplate = button.getAttribute('data-confirm-template'); - var confirmMessage = confirmMessageTemplate.replace('%num%', allCheckedCheckBoxes.length); - if(confirm(confirmMessage)){ - var url = button.getAttribute('data-url'); - var selectedValues = []; - - for(var i = 0; i < allCheckedCheckBoxes.length ; i++){ - var checkBox = allCheckedCheckBoxes[i]; - var userId = checkBox.getAttribute('data-user-id'); - var uuid = checkBox.getAttribute('data-uuid'); - selectedValues.push({userId: userId, uuid: uuid}); - } - - var params = {values: selectedValues} - new Ajax.Request(url, { - postBody: Object.toJSON(params), - contentType:"application/json", - encoding:"UTF-8", - onComplete: function(rsp) { - window.location.reload(); - } - }); - } + } + + if (allCheckedCheckBoxes.length == 0) { + var nothingSelected = button.getAttribute("data-nothing-selected"); + alert(nothingSelected); + } else { + var confirmMessageTemplate = button.getAttribute("data-confirm-template"); + var confirmMessage = confirmMessageTemplate.replace( + "%num%", + allCheckedCheckBoxes.length + ); + if (confirm(confirmMessage)) { + var url = button.getAttribute("data-url"); + var selectedValues = []; + + for (var i = 0; i < allCheckedCheckBoxes.length; i++) { + var checkBox = allCheckedCheckBoxes[i]; + var userId = checkBox.getAttribute("data-user-id"); + var uuid = checkBox.getAttribute("data-uuid"); + selectedValues.push({ userId: userId, uuid: uuid }); + } + + var params = { values: selectedValues }; + new Ajax.Request(url, { + postBody: Object.toJSON(params), + contentType: "application/json", + encoding: "UTF-8", + onComplete: function (rsp) { + window.location.reload(); + }, + }); } + } } -function onLineClicked(event){ - var line = this; - var checkBox = line.querySelector('.token-to-revoke'); - // to allow click on checkbox to act normally - if(event.target === checkBox){ - return; - } - checkBox.checked = !checkBox.checked; - onCheckChanged(checkBox); +function onLineClicked(event) { + var line = this; + var checkBox = line.querySelector(".token-to-revoke"); + // to allow click on checkbox to act normally + if (event.target === checkBox) { + return; + } + checkBox.checked = !checkBox.checked; + onCheckChanged(checkBox); } -function onCheckChanged(checkBox){ - var line = checkBox.up('tr'); - if(checkBox.checked){ - line.addClassName('selected'); - }else{ - line.removeClassName('selected'); - } +function onCheckChanged(checkBox) { + var line = checkBox.up("tr"); + if (checkBox.checked) { + line.addClassName("selected"); + } else { + line.removeClassName("selected"); + } } -(function(){ - document.addEventListener("DOMContentLoaded", function() { - var allLines = document.querySelectorAll('.legacy-token-usage table tr'); - for(var i = 0; i < allLines.length; i++){ - var line = allLines[i]; - if(!line.hasClassName('no-token-line')){ - line.onclick = onLineClicked; - } - } - - var allCheckBoxes = document.querySelectorAll('.token-to-revoke'); - for(var i = 0; i < allCheckBoxes.length; i++){ - var checkBox = allCheckBoxes[i]; - checkBox.onchange = function(){ onCheckChanged(this); }; - } - }); -})() +(function () { + document.addEventListener("DOMContentLoaded", function () { + var allLines = document.querySelectorAll(".legacy-token-usage table tr"); + for (var i = 0; i < allLines.length; i++) { + var line = allLines[i]; + if (!line.hasClassName("no-token-line")) { + line.onclick = onLineClicked; + } + } + + var allCheckBoxes = document.querySelectorAll(".token-to-revoke"); + for (var i = 0; i < allCheckBoxes.length; i++) { + var checkBox = allCheckBoxes[i]; + checkBox.onchange = function () { + onCheckChanged(this); + }; + } + }); +})(); diff --git a/core/src/main/resources/jenkins/security/seed/UserSeedProperty/help-resetSeed.html b/core/src/main/resources/jenkins/security/seed/UserSeedProperty/help-resetSeed.html index becdda38d3..1e1eff743d 100644 --- a/core/src/main/resources/jenkins/security/seed/UserSeedProperty/help-resetSeed.html +++ b/core/src/main/resources/jenkins/security/seed/UserSeedProperty/help-resetSeed.html @@ -1,9 +1,14 @@
- This action will disconnect all connected computers and devices for this user.
- The user will be required to log in again before performing any further operations.
+ This action will disconnect all connected computers and devices for this user. +
+ The user will be required to log in again before performing any further + operations. +
+
+
+ API tokens and SSH Public Keys provide additional access mechanisms, which + are not impacted by this action.
-
- API tokens and SSH Public Keys provide additional access mechanisms, which are not impacted by this action.
- To revoke all access for this user also revoke these mechanisms. -
+ To revoke all access for this user also revoke these mechanisms. +
diff --git a/core/src/main/resources/jenkins/security/seed/UserSeedProperty/help-resetSeed_it.html b/core/src/main/resources/jenkins/security/seed/UserSeedProperty/help-resetSeed_it.html index 6eb67b6ddc..6a484c660c 100644 --- a/core/src/main/resources/jenkins/security/seed/UserSeedProperty/help-resetSeed_it.html +++ b/core/src/main/resources/jenkins/security/seed/UserSeedProperty/help-resetSeed_it.html @@ -1,9 +1,16 @@
- Quest'azione disconnetterà tutti i computer e dispositivi connessi di quest'utente.
- All'utente sarà richiesto di accedere nuovamente prima di poter eseguire qualunque altra operazione.
+ Quest'azione disconnetterà tutti i computer e dispositivi connessi di + quest'utente. +
+ All'utente sarà richiesto di accedere nuovamente prima di poter eseguire + qualunque altra operazione. +
+
+
+ I token API e le chiavi pubbliche SSH forniscono meccanismi di accesso + aggiuntivi su cui quest'azione non ha effetto.
-
- I token API e le chiavi pubbliche SSH forniscono meccanismi di accesso aggiuntivi su cui quest'azione non ha effetto.
- Per revocare tutti gli accessi per quest'utente, procedere alla revoca anche per tali meccanismi. -
+ Per revocare tutti gli accessi per quest'utente, procedere alla revoca anche + per tali meccanismi. +
diff --git a/core/src/main/resources/jenkins/security/seed/UserSeedProperty/help-resetSeed_ja.html b/core/src/main/resources/jenkins/security/seed/UserSeedProperty/help-resetSeed_ja.html index 6bdb4d11d9..7e7c479970 100644 --- a/core/src/main/resources/jenkins/security/seed/UserSeedProperty/help-resetSeed_ja.html +++ b/core/src/main/resources/jenkins/security/seed/UserSeedProperty/help-resetSeed_ja.html @@ -1,9 +1,12 @@
- この操作は、このユーザーとして接続されている全てのコンピューターやデバイスを切断します。
- ユーザーが操作を続行するには再度ログインする必要があります。
+ この操作は、このユーザーとして接続されている全てのコンピューターやデバイスを切断します。 +
+ ユーザーが操作を続行するには再度ログインする必要があります。 +
+
+
+ APIトークンやSSH公開鍵の仕組みによりアクセスさせているものはこの操作による影響を受けません。
-
- APIトークンやSSH公開鍵の仕組みによりアクセスさせているものはこの操作による影響を受けません。
- このユーザーに関する全てのアクセスを無効にするには、それらの設定も無効にしてください。 -
+ このユーザーに関する全てのアクセスを無効にするには、それらの設定も無効にしてください。 +
diff --git a/core/src/main/resources/jenkins/security/seed/UserSeedProperty/resources.css b/core/src/main/resources/jenkins/security/seed/UserSeedProperty/resources.css index 8941a501ce..043d8cb9af 100644 --- a/core/src/main/resources/jenkins/security/seed/UserSeedProperty/resources.css +++ b/core/src/main/resources/jenkins/security/seed/UserSeedProperty/resources.css @@ -22,13 +22,13 @@ * THE SOFTWARE. */ .user-seed-panel .seed-message { - margin-bottom: 5px; -} + margin-bottom: 5px; +} .user-seed-panel .display-after-reset { - display: none; + display: none; } .user-seed-panel .display-after-reset.visible { - display: block; - margin-top: 5px; - margin-bottom: 5px; + display: block; + margin-top: 5px; + margin-bottom: 5px; } diff --git a/core/src/main/resources/jenkins/security/seed/UserSeedProperty/resources.js b/core/src/main/resources/jenkins/security/seed/UserSeedProperty/resources.js index 1a6b59acd3..ee14f1ea23 100644 --- a/core/src/main/resources/jenkins/security/seed/UserSeedProperty/resources.js +++ b/core/src/main/resources/jenkins/security/seed/UserSeedProperty/resources.js @@ -21,29 +21,29 @@ * OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN * THE SOFTWARE. */ -function resetSeed(button){ - var userSeedPanel = button.up('.user-seed-panel'); - var confirmMessage = button.getAttribute('data-confirm'); - var targetUrl = button.getAttribute('data-target-url'); - var redirectAfterClick = button.getAttribute('data-redirect-url'); - - var warningMessage = userSeedPanel.querySelector('.display-after-reset'); - if (warningMessage.hasClassName('visible')) { - warningMessage.removeClassName('visible'); - } - - if (confirm(confirmMessage)) { - new Ajax.Request(targetUrl, { - method: "post", - onSuccess: function(rsp, _) { - if (redirectAfterClick) { - window.location.href = redirectAfterClick; - } else { - if (!warningMessage.hasClassName('visible')) { - warningMessage.addClassName('visible'); - } - } - } - }); - } +function resetSeed(button) { + var userSeedPanel = button.up(".user-seed-panel"); + var confirmMessage = button.getAttribute("data-confirm"); + var targetUrl = button.getAttribute("data-target-url"); + var redirectAfterClick = button.getAttribute("data-redirect-url"); + + var warningMessage = userSeedPanel.querySelector(".display-after-reset"); + if (warningMessage.hasClassName("visible")) { + warningMessage.removeClassName("visible"); + } + + if (confirm(confirmMessage)) { + new Ajax.Request(targetUrl, { + method: "post", + onSuccess: function (rsp, _) { + if (redirectAfterClick) { + window.location.href = redirectAfterClick; + } else { + if (!warningMessage.hasClassName("visible")) { + warningMessage.addClassName("visible"); + } + } + }, + }); + } } diff --git a/core/src/main/resources/jenkins/slaves/RemotingWorkDirSettings/help-disabled.html b/core/src/main/resources/jenkins/slaves/RemotingWorkDirSettings/help-disabled.html index d35717026a..0f4e478da5 100644 --- a/core/src/main/resources/jenkins/slaves/RemotingWorkDirSettings/help-disabled.html +++ b/core/src/main/resources/jenkins/slaves/RemotingWorkDirSettings/help-disabled.html @@ -1,4 +1,8 @@
- Allows disabling Remoting Work Directory for the agent. - In such case the agent will be running in the legacy mode without logging enabled by default. + Allows disabling + + Remoting Work Directory + + for the agent. In such case the agent will be running in the legacy mode + without logging enabled by default.
diff --git a/core/src/main/resources/jenkins/slaves/RemotingWorkDirSettings/help-disabled_bg.html b/core/src/main/resources/jenkins/slaves/RemotingWorkDirSettings/help-disabled_bg.html index 0d1feca264..25a91db9b4 100644 --- a/core/src/main/resources/jenkins/slaves/RemotingWorkDirSettings/help-disabled_bg.html +++ b/core/src/main/resources/jenkins/slaves/RemotingWorkDirSettings/help-disabled_bg.html @@ -1,4 +1,8 @@
- Позволява изключването на отдалечената работна - директория за агента. В тези случаи подчиненият компютър ще работи в остарелия режим без журнални файлове. + Позволява изключването на + + отдалечената работна директория + + за агента. В тези случаи подчиненият компютър ще работи в остарелия режим без + журнални файлове.
diff --git a/core/src/main/resources/jenkins/slaves/RemotingWorkDirSettings/help-disabled_it.html b/core/src/main/resources/jenkins/slaves/RemotingWorkDirSettings/help-disabled_it.html index f0e29ffd50..3f1193e810 100644 --- a/core/src/main/resources/jenkins/slaves/RemotingWorkDirSettings/help-disabled_it.html +++ b/core/src/main/resources/jenkins/slaves/RemotingWorkDirSettings/help-disabled_it.html @@ -1,4 +1,8 @@
- Consente di disabilitare la directory di lavoro remoting per l'agente. - In tale caso l'agente sarà in esecuzione in modalità legacy senza che il logging sia abilitato per impostazione predefinita. + Consente di disabilitare + + la directory di lavoro remoting + + per l'agente. In tale caso l'agente sarà in esecuzione in modalità legacy + senza che il logging sia abilitato per impostazione predefinita.
diff --git a/core/src/main/resources/jenkins/slaves/RemotingWorkDirSettings/help-failIfWorkDirIsMissing.html b/core/src/main/resources/jenkins/slaves/RemotingWorkDirSettings/help-failIfWorkDirIsMissing.html index fbb4c572cc..cb9d63fa96 100644 --- a/core/src/main/resources/jenkins/slaves/RemotingWorkDirSettings/help-failIfWorkDirIsMissing.html +++ b/core/src/main/resources/jenkins/slaves/RemotingWorkDirSettings/help-failIfWorkDirIsMissing.html @@ -1,4 +1,5 @@
- If defined, Remoting will fail at startup if the target work directory is missing. - The option may be used to detect infrastructure issues like failed mount. + If defined, Remoting will fail at startup if the target work directory is + missing. The option may be used to detect infrastructure issues like failed + mount.
diff --git a/core/src/main/resources/jenkins/slaves/RemotingWorkDirSettings/help-failIfWorkDirIsMissing_bg.html b/core/src/main/resources/jenkins/slaves/RemotingWorkDirSettings/help-failIfWorkDirIsMissing_bg.html index 787565bf38..dfd2236c14 100644 --- a/core/src/main/resources/jenkins/slaves/RemotingWorkDirSettings/help-failIfWorkDirIsMissing_bg.html +++ b/core/src/main/resources/jenkins/slaves/RemotingWorkDirSettings/help-failIfWorkDirIsMissing_bg.html @@ -1,4 +1,5 @@
- Когато тук е зададена директория, Jenkins няма да стартира на този подчинен компютър, ако тя липсва. - Така може да засичате проблеми с инфраструктурата като неуспешно монтиране. + Когато тук е зададена директория, Jenkins няма да стартира на този подчинен + компютър, ако тя липсва. Така може да засичате проблеми с инфраструктурата + като неуспешно монтиране.
diff --git a/core/src/main/resources/jenkins/slaves/RemotingWorkDirSettings/help-failIfWorkDirIsMissing_it.html b/core/src/main/resources/jenkins/slaves/RemotingWorkDirSettings/help-failIfWorkDirIsMissing_it.html index c134c397a5..284bf70bb1 100644 --- a/core/src/main/resources/jenkins/slaves/RemotingWorkDirSettings/help-failIfWorkDirIsMissing_it.html +++ b/core/src/main/resources/jenkins/slaves/RemotingWorkDirSettings/help-failIfWorkDirIsMissing_it.html @@ -1,4 +1,5 @@
- Se l'opzione è definita, il componente di remoting fallirà se la directory di lavoro di destinazione è mancante. - L'opzione può essere utilizzata per rilevare problemi infrastrutturali come mount non riusciti. + Se l'opzione è definita, il componente di remoting fallirà se la directory di + lavoro di destinazione è mancante. L'opzione può essere utilizzata per + rilevare problemi infrastrutturali come mount non riusciti.
diff --git a/core/src/main/resources/jenkins/slaves/RemotingWorkDirSettings/help-internalDir.html b/core/src/main/resources/jenkins/slaves/RemotingWorkDirSettings/help-internalDir.html index 39f1b29fe4..a04ab552dd 100644 --- a/core/src/main/resources/jenkins/slaves/RemotingWorkDirSettings/help-internalDir.html +++ b/core/src/main/resources/jenkins/slaves/RemotingWorkDirSettings/help-internalDir.html @@ -1,4 +1,4 @@
- Defines a storage directory for the internal data. - This directory will be created within the Remoting working directory. + Defines a storage directory for the internal data. This directory will be + created within the Remoting working directory.
diff --git a/core/src/main/resources/jenkins/slaves/RemotingWorkDirSettings/help-internalDir_bg.html b/core/src/main/resources/jenkins/slaves/RemotingWorkDirSettings/help-internalDir_bg.html index 73d6e60d75..4f385384d3 100644 --- a/core/src/main/resources/jenkins/slaves/RemotingWorkDirSettings/help-internalDir_bg.html +++ b/core/src/main/resources/jenkins/slaves/RemotingWorkDirSettings/help-internalDir_bg.html @@ -1,4 +1,4 @@
- Указване на директория за съхранение на вътрешните данни. - Тя се създава като поддиректория на работната директория на подчинения компютър. + Указване на директория за съхранение на вътрешните данни. Тя се създава като + поддиректория на работната директория на подчинения компютър.
diff --git a/core/src/main/resources/jenkins/slaves/RemotingWorkDirSettings/help-internalDir_it.html b/core/src/main/resources/jenkins/slaves/RemotingWorkDirSettings/help-internalDir_it.html index adc9956b77..faaa5dd32d 100644 --- a/core/src/main/resources/jenkins/slaves/RemotingWorkDirSettings/help-internalDir_it.html +++ b/core/src/main/resources/jenkins/slaves/RemotingWorkDirSettings/help-internalDir_it.html @@ -1,4 +1,4 @@
- Definisce una directory di archiviazione per i dati interni. - Questa directory sarà creata all'interno della directory di lavoro del componente remoting. + Definisce una directory di archiviazione per i dati interni. Questa directory + sarà creata all'interno della directory di lavoro del componente remoting.
diff --git a/core/src/main/resources/jenkins/slaves/RemotingWorkDirSettings/help-workDirPath.html b/core/src/main/resources/jenkins/slaves/RemotingWorkDirSettings/help-workDirPath.html index 761945eaab..24572f09eb 100644 --- a/core/src/main/resources/jenkins/slaves/RemotingWorkDirSettings/help-workDirPath.html +++ b/core/src/main/resources/jenkins/slaves/RemotingWorkDirSettings/help-workDirPath.html @@ -1,4 +1,5 @@
- If defined, a custom Remoting work directory will be used instead of the Agent Root Directory. - This option has no environment variable resolution so far, it is recommended to use only absolute paths. + If defined, a custom Remoting work directory will be used instead of the Agent + Root Directory. This option has no environment variable resolution so far, it + is recommended to use only absolute paths.
diff --git a/core/src/main/resources/jenkins/slaves/RemotingWorkDirSettings/help-workDirPath_bg.html b/core/src/main/resources/jenkins/slaves/RemotingWorkDirSettings/help-workDirPath_bg.html index 7f5c24c5af..d8544e97c4 100644 --- a/core/src/main/resources/jenkins/slaves/RemotingWorkDirSettings/help-workDirPath_bg.html +++ b/core/src/main/resources/jenkins/slaves/RemotingWorkDirSettings/help-workDirPath_bg.html @@ -1,4 +1,5 @@
- Ако е зададена, ще се ползва тази работна директория, а не тази на подчинения компютър. - Тази опция не поддържа променливи, препоръчва се да използвате само абсолютни пътища. + Ако е зададена, ще се ползва тази работна директория, а не тази на подчинения + компютър. Тази опция не поддържа променливи, препоръчва се да използвате само + абсолютни пътища.
diff --git a/core/src/main/resources/jenkins/slaves/RemotingWorkDirSettings/help-workDirPath_it.html b/core/src/main/resources/jenkins/slaves/RemotingWorkDirSettings/help-workDirPath_it.html index c59dd28e78..38d79198f2 100644 --- a/core/src/main/resources/jenkins/slaves/RemotingWorkDirSettings/help-workDirPath_it.html +++ b/core/src/main/resources/jenkins/slaves/RemotingWorkDirSettings/help-workDirPath_it.html @@ -1,4 +1,6 @@
- Se l'opzione è definita, verrà utilizzata una directory di lavoro del componente remoting personalizzata anziché la directory radice dell'agente. - Quest'opzione finora non risolve le variabili d'ambiente, è consigliato utilizzare solo percorsi assoluti. + Se l'opzione è definita, verrà utilizzata una directory di lavoro del + componente remoting personalizzata anziché la directory radice dell'agente. + Quest'opzione finora non risolve le variabili d'ambiente, è consigliato + utilizzare solo percorsi assoluti.
diff --git a/core/src/main/resources/jenkins/tasks/filters/impl/RetainVariablesLocalRule/help-retainCharacteristicEnvVars.html b/core/src/main/resources/jenkins/tasks/filters/impl/RetainVariablesLocalRule/help-retainCharacteristicEnvVars.html index c14bd2cdd9..1355d6e83b 100644 --- a/core/src/main/resources/jenkins/tasks/filters/impl/RetainVariablesLocalRule/help-retainCharacteristicEnvVars.html +++ b/core/src/main/resources/jenkins/tasks/filters/impl/RetainVariablesLocalRule/help-retainCharacteristicEnvVars.html @@ -1,5 +1,14 @@

- When checked, characteristic environment variables will be retained in addition to the variables listed above. - These environment variables are job- and build-specific, defined by Jenkins, and are used to identify and kill processes started by this build step. - See the documentation for more details on starting processes. + When checked, + characteristic environment variables + will be retained in addition to the variables listed above. These environment + variables are job- and build-specific, defined by Jenkins, and are used to + identify and kill processes started by this build step. + + See the documentation for more details on starting processes. +

diff --git a/core/src/main/resources/jenkins/tasks/filters/impl/RetainVariablesLocalRule/help-variables.html b/core/src/main/resources/jenkins/tasks/filters/impl/RetainVariablesLocalRule/help-variables.html index 0788d14647..c8df8d8fa9 100644 --- a/core/src/main/resources/jenkins/tasks/filters/impl/RetainVariablesLocalRule/help-variables.html +++ b/core/src/main/resources/jenkins/tasks/filters/impl/RetainVariablesLocalRule/help-variables.html @@ -1,3 +1,7 @@
-

Whitespace separated, case insensitive list of environment variables that will be retained, i.e. not removed from the environment of this build step or reset to their default.

+

+ Whitespace separated, case insensitive list of environment variables that + will be retained, i.e. not removed from the environment of this build step + or reset to their default. +

diff --git a/core/src/main/resources/jenkins/tasks/filters/impl/RetainVariablesLocalRule/help.html b/core/src/main/resources/jenkins/tasks/filters/impl/RetainVariablesLocalRule/help.html index 2a4c6fb571..3ca8720bd2 100644 --- a/core/src/main/resources/jenkins/tasks/filters/impl/RetainVariablesLocalRule/help.html +++ b/core/src/main/resources/jenkins/tasks/filters/impl/RetainVariablesLocalRule/help.html @@ -1,48 +1,59 @@
-

Limit which environment variables are passed to a build step.

+

Limit which environment variables are passed to a build step.

-

Environment variables passed to the build step are filtered, unless listed below.

+

+ Environment variables passed to the build step are filtered, unless listed + below. +

-

The behavior of this filter depends on whether the environment variable is originally defined outside Jenkins:

-
    -
  • If the environment variable originates from Jenkins configuration, such as JOB_URL, - it will not be passed to the build step unless specified here.
    • -
  • If the environment variable originates from outside Jenkins, such as PATH, - the behavior depends on the option Process environment variables handling: - If that option is set to Retain, the original value will be passed to the build step, discarding any modifications inside Jenkins. - If that option is set to Remove, the variable will not be passed to the build step. -
    • -
-

- The following table shows the effect of filtering on an environment variable: -

- - - - - - - - - - - - - - - - -
BehaviorOriginally defined outside JenkinsOriginally defined inside Jenkins
- Process environment variables handling: reset - - Variable is reset to original value - - Variable is removed -
- Process environment variables handling: removed - - Variable is removed - - Variable is removed -
+

+ The behavior of this filter depends on whether the environment variable is + originally defined outside Jenkins: +

+
    +
  • + If the environment variable originates from Jenkins configuration, such as + JOB_URL + , it will not be passed to the build step unless specified here. +
    • +
  • + If the environment variable originates from outside Jenkins, such as + PATH + , the behavior depends on the option + Process environment variables handling + : If that option is set to + Retain + , the original value will be passed to the build step, discarding any + modifications inside Jenkins. If that option is set to + Remove + , the variable will not be passed to the build step. +
    • +
+

+ The following table shows the effect of filtering on an environment + variable: +

+ + + + + + + + + + + + + + + + +
BehaviorOriginally defined outside JenkinsOriginally defined inside Jenkins
+ Process environment variables handling: + reset + Variable is reset to original valueVariable is removed
+ Process environment variables handling: + removed + Variable is removedVariable is removed
diff --git a/core/src/main/resources/jenkins/triggers/ReverseBuildTrigger/help.html b/core/src/main/resources/jenkins/triggers/ReverseBuildTrigger/help.html index aa5b27cfbb..934986a207 100644 --- a/core/src/main/resources/jenkins/triggers/ReverseBuildTrigger/help.html +++ b/core/src/main/resources/jenkins/triggers/ReverseBuildTrigger/help.html @@ -1,10 +1,12 @@

- Set up a trigger so that when some other projects finish building, - a new build is scheduled for this project. This is convenient for running - an extensive test after a build is complete, for example. -

- This configuration complements the "Build other projects" section - in the "Post-build Actions" of an upstream project, but is preferable when you want to configure the downstream project. + Set up a trigger so that when some other projects finish building, a new + build is scheduled for this project. This is convenient for running an + extensive test after a build is complete, for example.

-
\ No newline at end of file +

+ This configuration complements the "Build other projects" section in the + "Post-build Actions" of an upstream project, but is preferable when you want + to configure the downstream project. +

+
diff --git a/core/src/main/resources/jenkins/triggers/ReverseBuildTrigger/help_bg.html b/core/src/main/resources/jenkins/triggers/ReverseBuildTrigger/help_bg.html index 6681a2c018..7064da53d6 100644 --- a/core/src/main/resources/jenkins/triggers/ReverseBuildTrigger/help_bg.html +++ b/core/src/main/resources/jenkins/triggers/ReverseBuildTrigger/help_bg.html @@ -1,10 +1,11 @@

Задаване на автоматично насрочване на изграждане на този проект след - завършването на изграждането на друг. Така е удобно да насрочите - продължителна последователност от тестове след изграждане, когато то - е завършило, без да го забавяте. -

+ завършването на изграждането на друг. Така е удобно да насрочите + продължителна последователност от тестове след изграждане, когато то е + завършило, без да го забавяте. +

+

Тази настройка допълва раздела „Изграждане на други проекти“ в „Действия след изграждане“ на проект, от който този зависи, но тази е за предпочитане, ако искате настройката да е при зависещите проекти. diff --git a/core/src/main/resources/jenkins/triggers/ReverseBuildTrigger/help_de.html b/core/src/main/resources/jenkins/triggers/ReverseBuildTrigger/help_de.html index d37d2f2d63..3953e9ed80 100644 --- a/core/src/main/resources/jenkins/triggers/ReverseBuildTrigger/help_de.html +++ b/core/src/main/resources/jenkins/triggers/ReverseBuildTrigger/help_de.html @@ -1,12 +1,13 @@

Richtet einen Build-Auslöser ein, so dass immer dann, wenn ein anderes - Projekt erfolgreich gebaut wurde, ein neuer Build dieses Projekts - geplant wird. Dies ist beispielsweise sehr praktisch, um ausführliche - Tests an einen erfolgreichen Build anzuschließen. -

- Die Angaben hier sind das exakte Spiegelbild des Abschnitts "Andere Projekte bauen" - unter "Post-Build Aktionen". Eine Veränderung hier wird automatisch von den - anderen Projekten reflektiert. + Projekt erfolgreich gebaut wurde, ein neuer Build dieses Projekts geplant + wird. Dies ist beispielsweise sehr praktisch, um ausführliche Tests an einen + erfolgreichen Build anzuschließen. +

+

+ Die Angaben hier sind das exakte Spiegelbild des Abschnitts "Andere Projekte + bauen" unter "Post-Build Aktionen". Eine Veränderung hier wird automatisch + von den anderen Projekten reflektiert.

diff --git a/core/src/main/resources/jenkins/triggers/ReverseBuildTrigger/help_fr.html b/core/src/main/resources/jenkins/triggers/ReverseBuildTrigger/help_fr.html index db5f3600f0..487e3ab882 100644 --- a/core/src/main/resources/jenkins/triggers/ReverseBuildTrigger/help_fr.html +++ b/core/src/main/resources/jenkins/triggers/ReverseBuildTrigger/help_fr.html @@ -1,12 +1,12 @@ 

- Positionne un déclencheur de build, de façon à ce qu'à la suite du build - de certains projets, un build soit lancé pour ce projet. - Cela est utile pour lancer un long test après la construction d'un - projet, par exemple. -

+ Positionne un déclencheur de build, de façon à ce qu'à la suite du build de + certains projets, un build soit lancé pour ce projet. Cela est utile pour + lancer un long test après la construction d'un projet, par exemple. +

+

Cette configuration est l'inverse de la section "Construire d'autres projets" dans "Actions post-build'. Changer l'un modifiera l'autre automatiquement.

-
\ No newline at end of file +
diff --git a/core/src/main/resources/jenkins/triggers/ReverseBuildTrigger/help_it.html b/core/src/main/resources/jenkins/triggers/ReverseBuildTrigger/help_it.html index 4ae55ce96d..615b03898b 100644 --- a/core/src/main/resources/jenkins/triggers/ReverseBuildTrigger/help_it.html +++ b/core/src/main/resources/jenkins/triggers/ReverseBuildTrigger/help_it.html @@ -1,10 +1,11 @@

Imposta un trigger in modo tale per cui quando termina la compilazione di - altri progetti venga pianificata una nuova compilazione per questo - progetto. Ciò, ad esempio, è utile per eseguire dei test estesi dopo il - completamento di una compilazione. -

+ altri progetti venga pianificata una nuova compilazione per questo progetto. + Ciò, ad esempio, è utile per eseguire dei test estesi dopo il completamento + di una compilazione. +

+

Questa configurazione è complementare alla sezione "Compila altri progetti" nelle "Azioni di post-compilazione" di un progetto upstream, ma è preferibile utilizzarla quando si vuole configurare il progetto downstream. diff --git a/core/src/main/resources/jenkins/triggers/ReverseBuildTrigger/help_ja.html b/core/src/main/resources/jenkins/triggers/ReverseBuildTrigger/help_ja.html index 79845b7fcb..455d7ab99a 100644 --- a/core/src/main/resources/jenkins/triggers/ReverseBuildTrigger/help_ja.html +++ b/core/src/main/resources/jenkins/triggers/ReverseBuildTrigger/help_ja.html @@ -1,11 +1,11 @@ 

他のプロジェクトのビルドが終了した時に、 - このプロジェクトの新規ビルドがスケジュールされるようにトリガーを設定します。 - 例えば、ビルドが完了した後に大量のテストを実行するケースなどで便利です。 + このプロジェクトの新規ビルドがスケジュールされるようにトリガーを設定します。 + 例えば、ビルドが完了した後に大量のテストを実行するケースなどで便利です。

この設定は、"ビルド後の処理"の"他のプロジェクトのビルド"と正反対の設定です。 - 片方を変更すると自動的にもう片方も変更されます。 + 片方を変更すると自動的にもう片方も変更されます。

diff --git a/core/src/main/resources/jenkins/triggers/ReverseBuildTrigger/help_pt_BR.html b/core/src/main/resources/jenkins/triggers/ReverseBuildTrigger/help_pt_BR.html index 91934b75d4..2c273929d9 100644 --- a/core/src/main/resources/jenkins/triggers/ReverseBuildTrigger/help_pt_BR.html +++ b/core/src/main/resources/jenkins/triggers/ReverseBuildTrigger/help_pt_BR.html @@ -1,10 +1,14 @@

- Configura um disparador tal que quando algum outro projeto terminar a construção, - uma nova construção é agendada para este projeto. Isto é conveniente para executar - um teste extensivo após uma construção ser completada, por exemplo. -

- Esta configuração é a visão oposta da seção "Construir outros projetos" - em "Açõs Pós-construção". Atualizar uma mudará automaticamente a outra. + Configura um disparador tal que quando algum outro projeto terminar a + construção, uma nova construção é agendada para + este projeto. Isto é conveniente para executar um teste extensivo + após uma construção ser completada, por exemplo. +

+

+ Esta configuração é a visão oposta da seção + "Construir outros projetos" em "Açõs + Pós-construção". Atualizar uma mudará automaticamente a + outra.

diff --git a/core/src/main/resources/jenkins/triggers/ReverseBuildTrigger/help_ru.html b/core/src/main/resources/jenkins/triggers/ReverseBuildTrigger/help_ru.html index ae6b82d90d..7a4c512368 100644 --- a/core/src/main/resources/jenkins/triggers/ReverseBuildTrigger/help_ru.html +++ b/core/src/main/resources/jenkins/triggers/ReverseBuildTrigger/help_ru.html @@ -1,10 +1,12 @@ 

- Устанавливает триггер таким образом, что когда другой проект завершает сборку, - запускается сборка этого проекта. Это полезно для запуска дополнительных - тестов после завершения сборки, например. -

- Эта опция противоположна опции "Собрать другой проект" в секции "Послесборочные - действия". Изменив это значение, второе изменится автоматически. + Устанавливает триггер таким образом, что когда другой проект завершает + сборку, запускается сборка этого проекта. Это полезно для запуска + дополнительных тестов после завершения сборки, например.

-
\ No newline at end of file +

+ Эта опция противоположна опции "Собрать другой проект" в секции + "Послесборочные действия". Изменив это значение, второе изменится + автоматически. +

+
diff --git a/core/src/main/resources/jenkins/triggers/ReverseBuildTrigger/help_tr.html b/core/src/main/resources/jenkins/triggers/ReverseBuildTrigger/help_tr.html index d9d223b21b..3ab7a76174 100644 --- a/core/src/main/resources/jenkins/triggers/ReverseBuildTrigger/help_tr.html +++ b/core/src/main/resources/jenkins/triggers/ReverseBuildTrigger/help_tr.html @@ -1,12 +1,17 @@

- Belirlediğiniz diğer projeler, yapılandırmalarını bitirdiğinde, bu proje - için yeni bir yapılandırma başlatmak için bir tetikleyici ayarlayabilirsiniz. - Mesela, bir yapılandırma bittikten sonra geniş kapsamlı test yapılandırmaları + Belirlediğiniz diğer projeler, + yapılandırmalarını bitirdiğinde, bu proje için + yeni bir yapılandırma başlatmak için bir tetikleyici + ayarlayabilirsiniz. Mesela, bir yapılandırma bittikten sonra + geniş kapsamlı test yapılandırmaları çalıştırabilirsiniz. -

- Bu konfigürasyon, "Yapılandırma-sonrası Aksiyonlar" kısmındaki "Diğer projeleri yapılandır" - kısmının tersten görüntüsü gibidir. Birindeki tetikleme konfigürasyonunu değiştirmek, diğerindeki - de otomatik olarak etkileyecektir.

-
\ No newline at end of file +

+ Bu konfigürasyon, "Yapılandırma-sonrası Aksiyonlar" + kısmındaki "Diğer projeleri yapılandır" + kısmının tersten görüntüsü gibidir. + Birindeki tetikleme konfigürasyonunu değiştirmek, + diğerindeki de otomatik olarak etkileyecektir. +

+ diff --git a/core/src/main/resources/jenkins/triggers/ReverseBuildTrigger/help_zh_TW.html b/core/src/main/resources/jenkins/triggers/ReverseBuildTrigger/help_zh_TW.html index b1cb77a319..3478a95aab 100644 --- a/core/src/main/resources/jenkins/triggers/ReverseBuildTrigger/help_zh_TW.html +++ b/core/src/main/resources/jenkins/triggers/ReverseBuildTrigger/help_zh_TW.html @@ -2,7 +2,8 @@

設定觸發程序，在某他一些專案建置結束後，安排建置本專案。 舉例來說，這個功能可以讓您很方便的在建置完成後再執行大範圍的測試。 -

+

+

這是「建置後動作」裡「建置其他專案」的對立觀點。更新了其中一邊後，另外一邊也會自動修改。

- \ No newline at end of file + diff --git a/core/src/main/resources/lib/form/advanced/advanced.js b/core/src/main/resources/lib/form/advanced/advanced.js index 69725eb886..365c64b9e1 100644 --- a/core/src/main/resources/lib/form/advanced/advanced.js +++ b/core/src/main/resources/lib/form/advanced/advanced.js @@ -1,45 +1,54 @@ -Behaviour.specify("INPUT.advanced-button", 'advanced', 0, function(e) { - makeButton(e,function(e) { - var link = $(e.target).up(".advancedLink"); - var tr; - link.style.display = "none"; // hide the button +Behaviour.specify("INPUT.advanced-button", "advanced", 0, function (e) { + makeButton(e, function (e) { + var link = $(e.target).up(".advancedLink"); + var tr; + link.style.display = "none"; // hide the button - var container = link.next("table.advancedBody"); - if (container) { - container = container.down(); // TABLE -> TBODY - tr = link.up("TR"); - } else { - container = link.next("div.advancedBody"); - tr = link.up(".tr"); - } - - // move the contents of the advanced portion into the main table - var nameRef = tr.getAttribute("nameref"); - while (container.lastElementChild != null) { - var row = container.lastElementChild; - if(nameRef!=null && row.getAttribute("nameref")==null) - row.setAttribute("nameref",nameRef); // to handle inner rowSets, don't override existing values - $(row).setOpacity(0); + var container = link.next("table.advancedBody"); + if (container) { + container = container.down(); // TABLE -> TBODY + tr = link.up("TR"); + } else { + container = link.next("div.advancedBody"); + tr = link.up(".tr"); + } - tr.parentNode.insertBefore(row, $(tr).next()); + // move the contents of the advanced portion into the main table + var nameRef = tr.getAttribute("nameref"); + while (container.lastElementChild != null) { + var row = container.lastElementChild; + if (nameRef != null && row.getAttribute("nameref") == null) + row.setAttribute("nameref", nameRef); // to handle inner rowSets, don't override existing values + $(row).setOpacity(0); - new YAHOO.util.Anim(row, { - opacity: { to:1 } - }, 0.2, YAHOO.util.Easing.easeIn).animate(); + tr.parentNode.insertBefore(row, $(tr).next()); - } - layoutUpdateCallback.call(); - }); - e = null; // avoid memory leak + new YAHOO.util.Anim( + row, + { + opacity: { to: 1 }, + }, + 0.2, + YAHOO.util.Easing.easeIn + ).animate(); + } + layoutUpdateCallback.call(); + }); + e = null; // avoid memory leak }); -Behaviour.specify('.advanced-customized-fields-info', 'advanced', 0, function(element) { - var id = element.getAttribute('data-id'); - var span = $(id) +Behaviour.specify( + ".advanced-customized-fields-info", + "advanced", + 0, + function (element) { + var id = element.getAttribute("data-id"); + var span = $(id); if (span != null) { - span.style.display = ''; + span.style.display = ""; } else if (console && console.log) { - var customizedFields = element.getAttribute('data-customized-fields'); - console.log('no element ' + id + ' for ' + customizedFields); + var customizedFields = element.getAttribute("data-customized-fields"); + console.log("no element " + id + " for " + customizedFields); } -}); + } +); diff --git a/core/src/main/resources/lib/form/apply/apply.js b/core/src/main/resources/lib/form/apply/apply.js index d06911af4f..7a8f7667c8 100644 --- a/core/src/main/resources/lib/form/apply/apply.js +++ b/core/src/main/resources/lib/form/apply/apply.js @@ -1,89 +1,94 @@ -Behaviour.specify("INPUT.apply-button", 'apply', 0, function (e) { - var id; - var containerId = "container"+(iota++); +Behaviour.specify("INPUT.apply-button", "apply", 0, function (e) { + var id; + var containerId = "container" + iota++; - var responseDialog = new YAHOO.widget.Panel("wait"+(iota++), { - fixedcenter:true, - close:true, - draggable:true, - zindex:4, - modal:true, - visible:false - }); + var responseDialog = new YAHOO.widget.Panel("wait" + iota++, { + fixedcenter: true, + close: true, + draggable: true, + zindex: 4, + modal: true, + visible: false, + }); - responseDialog.setHeader("Error"); - responseDialog.setBody("
"); - responseDialog.render(document.body); - var target; // iframe + responseDialog.setHeader("Error"); + responseDialog.setBody("
"); + responseDialog.render(document.body); + var target; // iframe - function attachIframeOnload(target, f) { - if (target.attachEvent) { - target.attachEvent("onload", f); - } else { - target.onload = f; - } - } + function attachIframeOnload(target, f) { + if (target.attachEvent) { + target.attachEvent("onload", f); + } else { + target.onload = f; + } + } - makeButton(e,function (e) { - var f = findAncestor(e.target, "FORM"); + makeButton(e, function (e) { + var f = findAncestor(e.target, "FORM"); - // create a throw-away IFRAME to avoid back button from loading the POST result back - id = "iframe"+(iota++); - target = Element('iframe', {id: id, name: id, style: 'height:100%; width:100%'}); - $(containerId).appendChild(target); + // create a throw-away IFRAME to avoid back button from loading the POST result back + id = "iframe" + iota++; + target = Element("iframe", { + id: id, + name: id, + style: "height:100%; width:100%", + }); + $(containerId).appendChild(target); - attachIframeOnload(target, function () { - if (target.contentWindow && target.contentWindow.applyCompletionHandler) { - // apply-aware server is expected to set this handler - target.contentWindow.applyCompletionHandler(window); - } else { - // otherwise this is possibly an error from the server, so we need to render the whole content. - var doc = target.contentDocument || target.contentWindow.document; - var error = doc.getElementById('error-description'); - var r = YAHOO.util.Dom.getClientRegion(); - var contentHeight = r.height/5; - var contentWidth = r.width/2; - if (!error) { - // fallback if it's not a regular error dialog from oops.jelly: use the entire body - error = Element('div', {id: 'error-description'}); - error.appendChild(doc.getElementsByTagName('body')[0]); - contentHeight = r.height*3/4; - contentWidth = r.width*3/4; - } + attachIframeOnload(target, function () { + if (target.contentWindow && target.contentWindow.applyCompletionHandler) { + // apply-aware server is expected to set this handler + target.contentWindow.applyCompletionHandler(window); + } else { + // otherwise this is possibly an error from the server, so we need to render the whole content. + var doc = target.contentDocument || target.contentWindow.document; + var error = doc.getElementById("error-description"); + var r = YAHOO.util.Dom.getClientRegion(); + var contentHeight = r.height / 5; + var contentWidth = r.width / 2; + if (!error) { + // fallback if it's not a regular error dialog from oops.jelly: use the entire body + error = Element("div", { id: "error-description" }); + error.appendChild(doc.getElementsByTagName("body")[0]); + contentHeight = (r.height * 3) / 4; + contentWidth = (r.width * 3) / 4; + } - if (oldError = $('error-description')) { - // Remove old error if there is any - $(containerId).removeChild(oldError); - } + if ((oldError = $("error-description"))) { + // Remove old error if there is any + $(containerId).removeChild(oldError); + } - $(containerId).appendChild(error); + $(containerId).appendChild(error); - var dialogStyleHeight = contentHeight+40; - var dialogStyleWidth = contentWidth+20; + var dialogStyleHeight = contentHeight + 40; + var dialogStyleWidth = contentWidth + 20; - $(containerId).style.height = contentHeight+"px"; - $(containerId).style.width = contentWidth+"px"; - $(containerId).style.overflow = "scroll"; + $(containerId).style.height = contentHeight + "px"; + $(containerId).style.width = contentWidth + "px"; + $(containerId).style.overflow = "scroll"; - responseDialog.cfg.setProperty("width", dialogStyleWidth+"px"); - responseDialog.cfg.setProperty("height", dialogStyleHeight+"px"); - responseDialog.center(); - responseDialog.show(); - } - window.setTimeout(function() {// otherwise Firefox will fail to leave the "connecting" state - $(id).remove(); - },0) - }); + responseDialog.cfg.setProperty("width", dialogStyleWidth + "px"); + responseDialog.cfg.setProperty("height", dialogStyleHeight + "px"); + responseDialog.center(); + responseDialog.show(); + } + window.setTimeout(function () { + // otherwise Firefox will fail to leave the "connecting" state + $(id).remove(); + }, 0); + }); - f.target = target.id; - f.elements['core:apply'].value = "true"; - Event.fire(f,"jenkins:apply"); // give everyone a chance to write back to DOM - try { - buildFormTree(f); - f.submit(); - } finally { - f.elements['core:apply'].value = null; - f.target = '_self'; - } - }); + f.target = target.id; + f.elements["core:apply"].value = "true"; + Event.fire(f, "jenkins:apply"); // give everyone a chance to write back to DOM + try { + buildFormTree(f); + f.submit(); + } finally { + f.elements["core:apply"].value = null; + f.target = "_self"; + } + }); }); diff --git a/core/src/main/resources/lib/form/breadcrumb-config-outline/init.css b/core/src/main/resources/lib/form/breadcrumb-config-outline/init.css index c13591b549..dc5faf8d53 100644 --- a/core/src/main/resources/lib/form/breadcrumb-config-outline/init.css +++ b/core/src/main/resources/lib/form/breadcrumb-config-outline/init.css @@ -1,7 +1,7 @@ A.section-anchor { - position: relative; - top: -2em; - visibility: hidden; - display: inline-block; - width: 0px; + position: relative; + top: -2em; + visibility: hidden; + display: inline-block; + width: 0px; } diff --git a/core/src/main/resources/lib/form/breadcrumb-config-outline/init.js b/core/src/main/resources/lib/form/breadcrumb-config-outline/init.js index 6a74045ea3..ac5eed0bc2 100644 --- a/core/src/main/resources/lib/form/breadcrumb-config-outline/init.js +++ b/core/src/main/resources/lib/form/breadcrumb-config-outline/init.js @@ -1,21 +1,20 @@ Event.observe(window, "load", function () { - /** @type section.SectionNode */ - var outline = section.buildTree(); - var menu = new breadcrumbs.ContextMenu(); - $A(outline.children).each(function (e) { - var id = "section" + (iota++); // TODO: use human-readable ID - var caption = e.getHTML(); - var cur = $(e.section).down("A.section-anchor"); - if (cur != null) { - id = cur.id; - caption = caption.substring(caption.indexOf("</a>") + 4); - } else - $(e.section).insert({top:"#"}); - menu.add('#' + id, null, caption); - }); - var inpageNav = document.getElementById("inpage-nav") - var chevron = document.createElement("li") - chevron.classList.add("children") - inpageNav.parentNode.insertBefore(chevron, inpageNav.nextSibling); - breadcrumbs.attachMenu(chevron, menu); + /** @type section.SectionNode */ + var outline = section.buildTree(); + var menu = new breadcrumbs.ContextMenu(); + $A(outline.children).each(function (e) { + var id = "section" + iota++; // TODO: use human-readable ID + var caption = e.getHTML(); + var cur = $(e.section).down("A.section-anchor"); + if (cur != null) { + id = cur.id; + caption = caption.substring(caption.indexOf("</a>") + 4); + } else $(e.section).insert({ top: "#" }); + menu.add("#" + id, null, caption); + }); + var inpageNav = document.getElementById("inpage-nav"); + var chevron = document.createElement("li"); + chevron.classList.add("children"); + inpageNav.parentNode.insertBefore(chevron, inpageNav.nextSibling); + breadcrumbs.attachMenu(chevron, menu); }); diff --git a/core/src/main/resources/lib/form/combobox/combobox.js b/core/src/main/resources/lib/form/combobox/combobox.js index ff999f99a9..33b01633db 100644 --- a/core/src/main/resources/lib/form/combobox/combobox.js +++ b/core/src/main/resources/lib/form/combobox/combobox.js @@ -1,23 +1,27 @@ -Behaviour.specify("INPUT.combobox2", 'combobox', 100, function(e) { - var items = []; +Behaviour.specify("INPUT.combobox2", "combobox", 100, function (e) { + var items = []; - var c = new ComboBox(e,function(value) { - var candidates = []; - for (var i=0; i20) break; - } - } - return candidates; - }, {}); + var c = new ComboBox( + e, + function (value) { + var candidates = []; + for (var i = 0; i < items.length; i++) { + if (items[i].indexOf(value) == 0) { + candidates.push(items[i]); + if (candidates.length > 20) break; + } + } + return candidates; + }, + {} + ); - refillOnChange(e,function(params) { - new Ajax.Request(e.getAttribute("fillUrl"),{ - parameters: params, - onSuccess : function(rsp) { - items = eval('('+rsp.responseText+')'); - } - }); - }); -}); \ No newline at end of file + refillOnChange(e, function (params) { + new Ajax.Request(e.getAttribute("fillUrl"), { + parameters: params, + onSuccess: function (rsp) { + items = eval("(" + rsp.responseText + ")"); + }, + }); + }); +}); diff --git a/core/src/main/resources/lib/form/confirm.js b/core/src/main/resources/lib/form/confirm.js index fe830207a1..73bef66022 100644 --- a/core/src/main/resources/lib/form/confirm.js +++ b/core/src/main/resources/lib/form/confirm.js @@ -1,122 +1,121 @@ -(function() { - var errorMessage = "You have modified configuration"; - var needToConfirm = false; +(function () { + var errorMessage = "You have modified configuration"; + var needToConfirm = false; - function confirm() { - needToConfirm = true; + function confirm() { + needToConfirm = true; + } + + function clearConfirm() { + needToConfirm = false; + } + + function confirmExit() { + if (needToConfirm) { + return errorMessage; } + } - function clearConfirm() { - needToConfirm = false; + function isIgnoringConfirm(element) { + if (element.hasClassName("force-dirty")) { + return false; + } + if (element.hasClassName("ignore-dirty")) { + return true; + } + // to allow sub-section of the form to ignore confirm + // especially useful for "pure" JavaScript area + // we try to gather the first parent with a marker, + var dirtyPanel = element.up(".ignore-dirty-panel,.force-dirty-panel"); + if (!dirtyPanel) { + return false; } - function confirmExit() { - if (needToConfirm) { - return errorMessage; - } + if (dirtyPanel.hasClassName("force-dirty-panel")) { + return false; } - - function isIgnoringConfirm(element){ - if(element.hasClassName('force-dirty')){ - return false; - } - if(element.hasClassName('ignore-dirty')){ - return true; - } - // to allow sub-section of the form to ignore confirm - // especially useful for "pure" JavaScript area - // we try to gather the first parent with a marker, - var dirtyPanel = element.up('.ignore-dirty-panel,.force-dirty-panel'); - if(!dirtyPanel){ - return false; - } - - if(dirtyPanel.hasClassName('force-dirty-panel')){ - return false; - } - if(dirtyPanel.hasClassName('ignore-dirty-panel')){ - return true; - } - + if (dirtyPanel.hasClassName("ignore-dirty-panel")) { + return true; + } + + return false; + } + + function isModifyingButton(btn) { + // TODO don't consider hetero list 'add' buttons + // needs to handle the yui menus instead + // if (btn.classList.contains("hetero-list-add")) { + // return false; + // } + + if (btn.parentNode.parentNode.classList.contains("advanced-button")) { + // don't consider 'advanced' buttons return false; } - function isModifyingButton(btn) { - // TODO don't consider hetero list 'add' buttons - // needs to handle the yui menus instead - // if (btn.classList.contains("hetero-list-add")) { - // return false; - // } + if (isIgnoringConfirm(btn)) { + return false; + } - if (btn.parentNode.parentNode.classList.contains("advanced-button")) { - // don't consider 'advanced' buttons - return false; - } - - if(isIgnoringConfirm(btn)){ - return false; - } + // default to true + return true; + } - // default to true - return true; + function initConfirm() { + var configForm = document.getElementsByName("config"); + if (configForm.length > 0) { + configForm = configForm[0]; + } else { + configForm = document.getElementsByName("viewConfig")[0]; } - function initConfirm() { - var configForm = document.getElementsByName("config"); - if (configForm.length > 0) { - configForm = configForm[0] - } else { - configForm = document.getElementsByName("viewConfig")[0]; - } + YAHOO.util.Event.on($(configForm), "submit", clearConfirm, this); - YAHOO.util.Event.on($(configForm), "submit", clearConfirm, this); - - var buttons = configForm.getElementsByTagName("button"); - var name; - for ( var i = 0; i < buttons.length; i++) { - var button = buttons[i]; - name = button.parentNode.parentNode.getAttribute('name'); - if (name == "Submit" || name == "Apply" || name == "OK") { - $(button).on('click', function() { - needToConfirm = false; - }); - } else { - if (isModifyingButton(button)) { - $(button).on('click', confirm); - } + var buttons = configForm.getElementsByTagName("button"); + var name; + for (var i = 0; i < buttons.length; i++) { + var button = buttons[i]; + name = button.parentNode.parentNode.getAttribute("name"); + if (name == "Submit" || name == "Apply" || name == "OK") { + $(button).on("click", function () { + needToConfirm = false; + }); + } else { + if (isModifyingButton(button)) { + $(button).on("click", confirm); } } + } - var inputs = configForm.getElementsByTagName("input"); - for ( var i = 0; i < inputs.length; i++) { - var input = inputs[i]; - if(!isIgnoringConfirm(input)){ - if (input.type == 'checkbox' || input.type == 'radio') { - $(input).on('click', confirm); - } else { - $(input).on('input', confirm); - } + var inputs = configForm.getElementsByTagName("input"); + for (var i = 0; i < inputs.length; i++) { + var input = inputs[i]; + if (!isIgnoringConfirm(input)) { + if (input.type == "checkbox" || input.type == "radio") { + $(input).on("click", confirm); + } else { + $(input).on("input", confirm); } } + } - inputs = configForm.getElementsByTagName("select"); - for ( var i = 0; i < inputs.length; i++) { - var input = inputs[i]; - if(!isIgnoringConfirm(input)){ - $(input).on('change', confirm); - } + inputs = configForm.getElementsByTagName("select"); + for (var i = 0; i < inputs.length; i++) { + var input = inputs[i]; + if (!isIgnoringConfirm(input)) { + $(input).on("change", confirm); } + } - inputs = configForm.getElementsByTagName("textarea"); - for ( var i = 0; i < inputs.length; i++) { - var input = inputs[i]; - if(!isIgnoringConfirm(input)){ - $(input).on('input', confirm); - } + inputs = configForm.getElementsByTagName("textarea"); + for (var i = 0; i < inputs.length; i++) { + var input = inputs[i]; + if (!isIgnoringConfirm(input)) { + $(input).on("input", confirm); } } + } - window.onbeforeunload = confirmExit; - Event.on(window,'load', initConfirm); - + window.onbeforeunload = confirmExit; + Event.on(window, "load", initConfirm); })(); diff --git a/core/src/main/resources/lib/form/filter-menu-button/filter-menu-button.js b/core/src/main/resources/lib/form/filter-menu-button/filter-menu-button.js index abababa4e2..6d1ddb114d 100644 --- a/core/src/main/resources/lib/form/filter-menu-button/filter-menu-button.js +++ b/core/src/main/resources/lib/form/filter-menu-button/filter-menu-button.js @@ -1,19 +1,27 @@ -function createFilterMenuButton(button, menu, menuAlignment, menuMinScrollHeight) { +function createFilterMenuButton( + button, + menu, + menuAlignment, + menuMinScrollHeight +) { var MIN_NUM_OPTIONS = 5; var menuButton = new YAHOO.widget.Button(button, { type: "menu", menu: menu, menualignment: menuAlignment, - menuminscrollheight: menuMinScrollHeight + menuminscrollheight: menuMinScrollHeight, }); var filter = _createFilterMenuButton(menuButton._menu); menuButton._menu.element.appendChild(filter); menuButton._menu.showEvent.subscribe(function () { - filter.firstElementChild.value = ''; + filter.firstElementChild.value = ""; _applyFilterKeyword(menuButton._menu, filter.firstElementChild); - filter.style.display = (_getItemList(menuButton._menu).children.length >= MIN_NUM_OPTIONS) ? '' : 'NONE'; + filter.style.display = + _getItemList(menuButton._menu).children.length >= MIN_NUM_OPTIONS + ? "" + : "NONE"; }); menuButton._menu.setInitialFocus = function () { setTimeout(function () { @@ -26,12 +34,14 @@ function createFilterMenuButton(button, menu, menuAlignment, menuMinScrollHeight function _createFilterMenuButton(menu) { const filterInput = document.createElement("input"); - filterInput.classList.add('jenkins-input') + filterInput.classList.add("jenkins-input"); filterInput.setAttribute("placeholder", "Filter"); filterInput.setAttribute("spellcheck", "false"); filterInput.setAttribute("type", "search"); - filterInput.addEventListener('input', (event) => _applyFilterKeyword(menu, event)); + filterInput.addEventListener("input", (event) => + _applyFilterKeyword(menu, event) + ); const filterContainer = document.createElement("div"); filterContainer.appendChild(filterInput); @@ -40,12 +50,12 @@ function _createFilterMenuButton(menu) { } function _applyFilterKeyword(menu, filterInput) { - const filterKeyword = (filterInput.currentTarget.value || '').toLowerCase(); + const filterKeyword = (filterInput.currentTarget.value || "").toLowerCase(); const itemList = _getItemList(menu); let item, match; for (item of itemList.children) { match = item.innerText.toLowerCase().includes(filterKeyword); - item.style.display = match ? '' : 'NONE'; + item.style.display = match ? "" : "NONE"; } menu.align(); } diff --git a/core/src/main/resources/lib/form/hetero-list/hetero-list.js b/core/src/main/resources/lib/form/hetero-list/hetero-list.js index 11a98c532d..2cb1415609 100644 --- a/core/src/main/resources/lib/form/hetero-list/hetero-list.js +++ b/core/src/main/resources/lib/form/hetero-list/hetero-list.js @@ -2,155 +2,187 @@ // do the ones that extract innerHTML so that they can get their original HTML before // other behavior rules change them (like YUI buttons.) -Behaviour.specify("DIV.hetero-list-container", 'hetero-list', -100, function(e) { - e=$(e); - if(isInsideRemovable(e)) return; - - // components for the add button - var menu = document.createElement("SELECT"); - var btns = findElementsBySelector(e,"INPUT.hetero-list-add"), - btn = btns[btns.length-1]; // In case nested content also uses hetero-list - if (!btn) { - return; +Behaviour.specify( + "DIV.hetero-list-container", + "hetero-list", + -100, + function (e) { + e = $(e); + if (isInsideRemovable(e)) return; + + // components for the add button + var menu = document.createElement("SELECT"); + var btns = findElementsBySelector(e, "INPUT.hetero-list-add"), + btn = btns[btns.length - 1]; // In case nested content also uses hetero-list + if (!btn) { + return; + } + YAHOO.util.Dom.insertAfter(menu, btn); + + var prototypes = $(e.lastElementChild); + while (!prototypes.hasClassName("prototypes")) + prototypes = prototypes.previous(); + var insertionPoint = prototypes.previous(); // this is where the new item is inserted. + + // extract templates + var templates = []; + var i = 0; + $(prototypes) + .childElements() + .each(function (n) { + var name = n.getAttribute("name"); + var tooltip = n.getAttribute("tooltip"); + var descriptorId = n.getAttribute("descriptorId"); + // YUI Menu interprets this