-
Bug
-
Resolution: Unresolved
-
Major
-
Jenkins 2.7.2
Delivery Pipeline Plugin 0.9.12
Matrix Project Plugin 1.7.1
Steps to reproduce:
- Create freestyle job and select the "Create Delivery Pipeline version" option (providing something like foo.${BUILD_NUMBER} in the Template field.
- Create a matrix build, with one user-defined axis and one input string parameter.
- Trigger the matrix build as a post-build step from the freestyle job, passing in the single parameter.
Although everything runs okay, jenkins.err.log will show several errors about skipping parameters.
{{Sep 08, 2016 9:03:26 AM hudson.model.ParametersAction filter
WARNING: Skipped parameter `INPUT` as it is undefined on `Sandbox/Matrix/Downstream/AXIS=64`. Set `-Dhudson.model.ParametersAction.keepUndefinedParameters`=true to allow undefined parameters to be injected as environment variables or `-Dhudson.model.ParametersAction.safeParameters=[comma-separated list]` to whitelist specific parameter names, even though it represents a security breach
Sep 08, 2016 9:03:26 AM hudson.model.ParametersAction filter
WARNING: Skipped parameter `PIPELINE_VERSION` as it is undefined on `Sandbox/Matrix/Downstream/AXIS=64`. Set `-Dhudson.model.ParametersAction.keepUndefinedParameters`=true to allow undefined parameters to be injected as environment variables or `-Dhudson.model.ParametersAction.safeParameters=[comma-separated list]` to whitelist specific parameter names, even though it represents a security breach}}
- is related to
-
JENKINS-34805 Delivery Pipeline plugin doesn't create the environment variable PIPELINE_VERSION since upgrade
-
- Resolved
-
A Result of this error seems to be that the PIPELINE_VERSION environment variable is not available to following build steps in the build job that creates the variable. But it appears on the pipeline view if used in the pipeline task description field.
I have a local Jenkins v1.639 instance where this works and the PIPELINE_VERSION environment variable can be used by following build steps.
The same build job on my local Jenkins v2.7.4 instance with the same configuration fails when I try to access PIPELINE_VERSION in following buildstep, because it is null. I can easily reproduce this with a minimal build job.