-
Improvement
-
Resolution: Unresolved
-
Blocker
-
None
Steps to reproduce:
1. create job Foo with two string parameters: MAJOR, with default value '1', MINOR, with default value '0'
2. create job Bar with a groovy post-build hook thus:
def params = [] params.push( new StringParameterValue( 'MINOR', 2 ) ) def foo = manager.hudson.getJob( 'Foo' ) foo.scheduleBuild( 2, new Cause.UpstreamCause( manager.build ), new ParametersAction( params ) )
3. build Bar
Expected Result:
Foo builds with parameter values MAJOR=1, MINOR=2
Actual Result:
Foo build with parameter values MINOR=2
If MAJOR isn't specified in the parameter list when invoking the build, it should use the default value in Foo's configuration. Instead, the parameter isn't evaluated at all.
- is related to
-
JENKINS-31897 Default parameter value is not used
-
- Resolved
-
-
JENKINS-30178 Regression: parameters are not set on commit notification
-
- Closed
-
- relates to
-
JENKINS-42698 Support default value for parameters if they are not set
-
- Resolved
-
[JENKINS-13768] default parameter values are ignored when triggering parameterized build from groovy post-build script
Component/s | New: core [ 15593 ] | |
Component/s | Original: parameterized-trigger [ 15592 ] | |
Assignee | Original: huybrechts [ huybrechts ] | |
Issue Type | Original: Bug [ 1 ] | New: Improvement [ 4 ] |
Link | New: This issue is related to SECURITY-170 [ SECURITY-170 ] |
Link |
New:
This issue is related to |
Link |
New:
This issue is related to |
Workflow | Original: JNJira [ 144235 ] | New: JNJira + In-Review [ 176107 ] |
Priority | Original: Major [ 3 ] | New: Blocker [ 1 ] |
Component/s | New: groovy-postbuild-plugin [ 15685 ] | |
Component/s | Original: core [ 15593 ] | |
Assignee | New: Stefan Wolf [ wolfs ] |
Link |
New:
This issue relates to |