-
Bug
-
Resolution: Unresolved
-
Minor
-
None
My pipeline defines a parameter with sth like:
parameters { booleanParam(name: 'RUN_TESTS', defaultValue: false, description: 'Do you want to run the build with tests?') }
Printing the param value with
script { if (params.RUN_TESTS) { echo "true: $RUN_TESTS" } else echo "false: $RUN_TESTS" }
shows that the value is always TRUE and the tests are always executed.
I think this is somewhat related to https://issues.jenkins-ci.org/browse/JENKINS-36543
[JENKINS-49794] Parameter references not using params.NAME retained across Replay
Component/s | New: workflow-job-plugin [ 21716 ] |
Description |
Original:
My pipeline defines a parameter with sth like: {noformat} parameters { booleanParam(name: 'RUN_TESTS', defaultValue: false, description: 'Do you want to run the build with tests?') }{noformat} Printing the param value with {code:java} script { if (params.RUN_TESTS) { echo "true: $RUN_TESTS" } else echo "false: $RUN_TESTS" }{code} shows that the value is always TRUE and the tests are always executed. I think this is somewhat related to I think this is somewhat related to https://issues.jenkins-ci.org/browse/JENKINS-36543  |
New:
My pipeline defines a parameter with sth like: {noformat} parameters { booleanParam(name: 'RUN_TESTS', defaultValue: false, description: 'Do you want to run the build with tests?') }{noformat} Printing the param value with {code:java} script { if (params.RUN_TESTS) { echo "true: $RUN_TESTS" } else echo "false: $RUN_TESTS" }{code} shows that the value is always TRUE and the tests are always executed. I think this is somewhat related to https://issues.jenkins-ci.org/browse/JENKINS-36543  |
Attachment | New: Screen Shot 2018-02-28 at 15.12.16.png [ 41626 ] |
plugin versions are attached as screenshot