Ensure Jenkins build parameters are set #278
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Jenkins build parameters do not seem to be set on the very first build of a new branch. env.PARAM_NAME returns null, and referring to them directly by PARAM_NAME throws groovy.lang.MissingPropertyException. This is a very hacky solution - it checks for null parameters and makes sure that they are set to the defaults if so - but I haven't been able to find a better solution.
suzannehamilton
force-pushed
the
jenkins-default-parameters
branch
from
959ed4b
to
82d80ab
Compare
|
I've raised this as a Jenkins pipeline issue since other people have seen the same error: |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Jenkins build parameters do not seem to be set on the very first build of a new branch. env.PARAM_NAME returns null, and referring to them directly by PARAM_NAME throws groovy.lang.MissingPropertyException. This means that the first build of a new Jenkins branch always fails.
The parameters are set correctly on every subsequent build, whether it is triggered automatically by a branch push or manually in by a Jenkins user.
This is an extremely hacky solution - it checks for null parameters and makes sure that they are set to the defaults if so - but I haven't found anything better.
If anyone has any other ideas or can spot what I'm doing wrong with the parameters, please let me know! (@afda16?)
If not, I'll report this to Jenkins in case it's a broader issue with parameterized builds in multibranch pipelines.