• Type: Bug
• Resolution: Fixed
• Priority: Critical
• Component/s: delivery-pipeline-plugin
• Labels:

  • 2.0
  • delivery-pipeline-plugin-0.9.9
  • jenkins2.0
• Environment:

  Jenkins 2.3
  delivery-pipeline plugin 0.9.9
  SECURITY-170 / CVE-2016-3721
  

[JENKINS-34805] Delivery Pipeline plugin doesn't create the environment variable PIPELINE_VERSION since upgrade

grant jew created issue - 2016-05-13 14:28

Jeebitesh Kalantri made changes - 2016-05-16 13:39

Labels

New: 2.0 delivery-pipeline-plugin-0.9.9 jenkins2.0

Tommy Tynjä made changes - 2016-05-18 06:43

Assignee	Original: Patrik Boström [ patbos ]	New: Tommy Tynjä [ tommysdk ]
Description	Original: After upgrading to Jenkins 2.2 delivery-pipeline plugin 0.9.9 The environment variable PIPELINE_VERSION doesn't get created and stored for the initial job. We use this in our downstream jobs which are all breaking now.	New: After upgrading to Jenkins 2.2 delivery-pipeline plugin 0.9.9 The environment variable PIPELINE_VERSION doesn't get created and stored for the initial job. This is due to SECURITY-170 / CVE-2016-3721. Please see https://wiki.jenkins-ci.org/display/SECURITY/Jenkins+Security+Advisory+2016-05-11. Original behaviour can be restored for testing purposes by setting hudson.model.ParametersAction.keepUndefinedParameters=true
Environment	Original: Jenkins 2.3 delivery-pipeline plugin 0.9.9	New: Jenkins 2.3 delivery-pipeline plugin 0.9.9 SECURITY-170 / CVE-2016-3721

Tommy Tynjä made changes - 2016-05-18 08:23

Status

Original: Open [ 1 ]

New: In Progress [ 3 ]

Tommy Tynjä made changes - 2016-06-10 06:33

Resolution		New: Fixed [ 1 ]
Status	Original: In Progress [ 3 ]	New: Resolved [ 5 ]

R. Tyler Croy made changes - 2016-07-25 23:57

Workflow

Original: JNJira [ 170996 ]

New: JNJira + In-Review [ 199002 ]

Arnaud Héritier made changes - 2017-03-23 22:39

Link

New: This issue is related to JENKINS-38062 [ JENKINS-38062 ]