You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Remove System V init instructions that no longer work (#383)
* Remove System V init instructions that no longer work
Use consistent headings and improve the phrasing a little.
* Use a more specific link
* Move property earlier in the line
* More phrasing fixes
* Fix README spelling error
* Fix changelog spelling errors
* Fix online help spelling errors
* Fix spelling error in form title
@@ -11,7 +10,7 @@ with various ways of specifying parameters for the new build.
11
10
These new builds appear as "Subprojects" in the Jenkins UI when you
12
11
are looking at a project that triggers them.
13
12
14
-
You can add multiple configurations: each has a list of projects to trigger, a condition for when to trigger them
13
+
You can add multiple configurations: each has a list of projects to trigger, a condition for when to trigger them
15
14
(based on the result of the current build), and a parameters section.
16
15
17
16
There is also a Parameterized Remote Trigger Plugin in case you want to trigger a build on a different/remote Jenkins Controller.
@@ -35,7 +34,7 @@ This lets you create a "function call" like semantics.
35
34
36
35
#### Usage as a Build step
37
36
38
-
When using the _Trigger/Call builds on another project_ item.
37
+
When using the _Trigger/Call builds on another project_ item.
39
38
If the trigger is configured with the "Block until the triggered projects finish their builds" enabled, the following Environment variables are made available for further build steps.
40
39
41
40
Env variables for future build steps:
@@ -48,87 +47,63 @@ Env variables for future build steps:
48
47
-`TRIGGERED_BUILD_RESULT_<project name>*RUN*<build number>` - Result of triggered build for build number
49
48
-`TRIGGERED_BUILD_RUN_COUNT_<project name>` - Number of builds triggered for the project
50
49
51
-
From 2.17 onwards: All Project names have characters not a-zA-Z or 0-9 replaced by
52
-
`_(multiple characters are condensed into a single)`.
50
+
From 2.17 onwards: All Project names have characters not a-zA-Z or 0-9 replaced by
51
+
`_(multiple characters are condensed into a single)`.
53
52
54
53
Note that with the BuildStep a variable can be used for the project name, I.E. `${projectName}`.
55
54
56
-
####Use of the plugin in a Matrix job
55
+
## Use of the plugin in a Matrix job
57
56
58
-
#####Post build task
57
+
### Post build task
59
58
60
-
When using the trigger parameterized build as a post build task for a matrix job the triggering will be be done once when all of the different matrix configurations have completed.
59
+
When using the trigger parameterized build as a post build task for a matrix job the triggering will be be done once when all of the different matrix configurations have completed.
61
60
In this case some of the Environment variables may not be resolvable as passing them to downstream jobs will fail.
62
61
You also cannot use a variable for the downstream project name.
63
-
If this functionality is needed, the BuildStep must be used.
62
+
If this functionality is needed, the BuildStep must be used.
64
63
65
-
Environment variables that should be available are the the default shell ones (`<yourserver:port>/env-vars.html`) and ones defined as Parameters.
64
+
Environment variables that should be available are the the default shell ones (`<yourserver:port>/env-vars.html`) and ones defined as Parameters.
66
65
Variables added by the other plugins as a buildwrappers may not be available.
67
66
68
-
#####Build step
67
+
### Build step
69
68
70
-
When using the trigger parameterized build as a buildstep it will be called for every different configuration,
69
+
When using the trigger parameterized build as a build step it will be called for every different configuration,
71
70
so if triggering another project with no parameters it will be done the same number of times as you have configurations,
72
71
possible causing the triggered job to run more than once.
73
72
74
73
However this also allows you to trigger other jobs with parameters relating to the current configuration,
75
74
i.e. triggering a build on the same node with the same JDK.
76
75
77
-
####Plugins contributing additional parameter types to this plugin
76
+
## Plugins contributing additional parameter types to this plugin
78
77
79
78
* Git Plugin
80
79
* NodeLabel Parameter Plugin
81
80
82
-
####Backward compatibility with version 2.22
81
+
## Backward compatibility with version 2.22
83
82
84
83
- Since Parameterized Trigger 2.23, there are cases that Parameterized Trigger fails to trigger downstream builds that can be successfully triggered with Parameterized Trigger \<= 2.22.
85
-
- This is caused by the new behavir introduced in Parameterized Trigger 2.23.
84
+
- This is caused by the new behavior introduced in Parameterized Trigger 2.23.
86
85
It gets to pass parameter values not directly to the downstream build, but to parameter definitions of downstream projects.
87
-
This enables parameter definitions perform its specific process, for example, selecting nodes with NodeLabel Parameter Plugin.
88
-
- Example: There is a project with a choice parameter with choices A, B, C.
86
+
This enables parameter definitions to perform its specific process, for example, selecting nodes with NodeLabel Parameter Plugin.
87
+
- Example: There is a project with a choice parameter with choices A, B, C.
89
88
When you triggered that project with parameter value D, it fails with following output in the upstream:
90
89
91
90
```
92
91
java.lang.IllegalArgumentException: Illegal choice: D at
- As those failures are ones designed by parameter definitions.
98
-
For example, the choice parameter is designed not to accept unexpected values.
99
-
-You will face same problem when you triggered those builds with Jenkins CLI or Remote access API.
97
+
For example, the choice parameter is designed to not accept unexpected values.
98
+
-The same behavior is visible builds are triggered those with the Jenkins CLI or the remote access API.
100
99
- It is recommended to fix your project configuration to have parameter definitions not fail.
101
100
- For example, use EnvInject Plugin to process values or use Extensible Choice Parameter Plugin which provides a choice parameter accepting edited values.
102
-
103
-
##### Workaround
104
-
105
-
As backward compatibility, you can make it work without fix by setting Java system property `hudson.plugins.parameterizedtrigger.ProjectSpecificParametersActionFactory.compatibility_mode` to `true`.
106
-
It can be done with launching Jenkins as followings:
Set the `hudson.plugins.parameterizedtrigger.ProjectSpecificParametersActionFactory.compatibility_mode` Java system property to `true` to restore the old behavior.
105
+
Refer to the ["Jenkins features controlled by system properties"](https://www.jenkins.io/doc/book/managing/system-properties/) for detailed instructions on Java system properties in Jenkins.
131
106
132
-
# Report an issue
107
+
##Report an issue
133
108
134
109
Please report issues and enhancements through the [Jenkins issue tracker](https://www.jenkins.io/participate/report-issue/redirect/#15592).
Copy file name to clipboardexpand all lines: src/main/resources/hudson/plugins/parameterizedtrigger/CounterBuildParameterFactory/help-validationFail.html
+1-1
Original file line number
Diff line number
Diff line change
@@ -2,7 +2,7 @@
2
2
This option determines the behaviour to take if the from,to and step values do not form a valid combination. One that gives a finite number of combinations.<br/>
3
3
The actions that can be taken are:
4
4
<ul>
5
-
<li><b>Fail the build step</b> This will fail the buildstep with a RuntimeException. (This is the default, and occured in older versions)</li>
5
+
<li><b>Fail the build step</b> This will fail the buildstep with a RuntimeException. (This is the default, and occurred in older versions)</li>
6
6
<li><b>Don't trigger these projects</b> This will cause the projects not to be triggered at all for this configuration.</li>
7
7
<li><b>Skip these parameters</b> This will allow the projects to be triggered without these parameters.</li>
Copy file name to clipboardexpand all lines: src/main/resources/hudson/plugins/parameterizedtrigger/FileBuildParameterFactory/help-noFilesFoundAction.html
+1-1
Original file line number
Diff line number
Diff line change
@@ -3,7 +3,7 @@
3
3
The actions that can be taken are:
4
4
<ul>
5
5
<li><b>Don't trigger these projects</b> This will cause the projects not to be triggered at all for this configuration. </li>
6
-
<li><b>Skip these parameters</b> This will allow the projects to be triggered without these parameters. (This is the default, and occured in older versions)</li>
6
+
<li><b>Skip these parameters</b> This will allow the projects to be triggered without these parameters. (This is the default, and occurred in older versions)</li>
7
7
<li><b>Fail the build step</b> This will fail the buildstep with a RuntimeException.</li>
0 commit comments