[JIRA] (JENKINS-38062) "Create Delivery Pipeline version" errors

"Create Delivery Pipeline version" errors

Issue Type:	Improvement
Assignee:	Patrik Boström
Components:	delivery-pipeline-plugin, matrix-project-plugin
Created:	2016/Sep/08 2:27 PM
Environment:	Jenkins 2.7.2 Delivery Pipeline Plugin 0.9.12 Matrix Project Plugin 1.7.1
Labels:	delivery matrix
Priority:	Major
Reporter:	Christopher Shannon

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}}

This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)

chris.and.amy.shannon@gmail.com (JIRA)

unread,

Sep 8, 2016, 10:29:01 AM9/8/16

to jenkinsc...@googlegroups.com

Christopher Shannon updated an issue

Jenkins /

"Create Delivery Pipeline version" errors

Change By:	Christopher Shannon
Issue Type:	Improvement Bug

h.meinardus@traveltrex.com (JIRA)

unread,

Sep 14, 2016, 12:30:01 PM9/14/16

to jenkinsc...@googlegroups.com

Henrik Meinardus commented on

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.

h.meinardus@traveltrex.com (JIRA)

unread,

Sep 15, 2016, 4:50:01 AM9/15/16

to jenkinsc...@googlegroups.com

Henrik Meinardus commented on

Additional note: The error appears from Jenkins 1.651.2 onward. 1.651.1 runs without problems. Maybe this is somehow connected to JENKINS-34540.

h.meinardus@traveltrex.com (JIRA)

unread,

Sep 15, 2016, 5:46:04 AM9/15/16

to jenkinsc...@googlegroups.com

Henrik Meinardus commented on

I digged a bit further in the commit history. This incompatibility was introduced by resolving SECURITY-170 (commit 57a82505f4dc5de97c57ad1f340561ad9f0159c5 and its follow-up) and can be worked around - as suggested in the warning - by starting the Jenkins Java process with the following additional parameter:

 
                                                                -Dhudson.model.ParametersAction.safeParameters=PIPELINE_VERSION

Maybe this should be documented on the plugin wiki page until it is fixed?

h.meinardus@traveltrex.com (JIRA)

unread,

Sep 15, 2016, 5:47:01 AM9/15/16

to jenkinsc...@googlegroups.com

Henrik Meinardus edited a comment on

I digged dug a bit further in the commit history. This incompatibility was introduced by resolving SECURITY-170 (commit 57a82505f4dc5de97c57ad1f340561ad9f0159c5 and its follow-up) and can be worked around - as suggested in the warning - by starting the Jenkins Java process with the following additional parameter:
{code}
-Dhudson.model.ParametersAction.safeParameters=PIPELINE_VERSION
{code}

Maybe this should be documented on the plugin wiki page until it is fixed?

chris.and.amy.shannon@gmail.com (JIRA)

unread,

Sep 15, 2016, 7:53:02 AM9/15/16

to jenkinsc...@googlegroups.com

Christopher Shannon commented on

FYI - yes you can work around the error message for PIPELINE_VERSION, but what is strange is that we see parameter errors for every parameter that we're sending downstream as well. You have to do the blanket override to get work around this right now.

 
                                                                -Dhudson.model.ParametersAction.keepUndefinedParameters=true

aheritier@apache.org (JIRA)

unread,

Mar 23, 2017, 6:40:02 PM3/23/17

to jenkinsc...@googlegroups.com

Arnaud Héritier commented on

~~JENKINS-34805~~ didn't solve the problem

This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)

tommy.tynja@diabol.se (JIRA)

unread,

Jun 12, 2019, 9:25:03 AM6/12/19

to jenkinsc...@googlegroups.com

Tommy Tynjä commented on

Backwards compatibility for delivery pipeline plugin 0.9.9 and older has been dropped as of 92d7fc6 by removing support for resolving version ParametersAction. Will be part of the next release of the delivery pipeline plugin.

This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)

tynjae@gmail.com (JIRA)

unread,

Jul 4, 2019, 5:39:03 AM7/4/19

to jenkinsc...@googlegroups.com

Tommy Tynjä commented on

Delivery Pipeline plugin fix released in delivery pipeline plugin 1.4.0.