Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-34805

Delivery Pipeline plugin doesn't create the environment variable PIPELINE_VERSION since upgrade

XMLWordPrintable

      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

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

          grant jew created issue -

          grant jew added a comment -

          downgraded to 2.0 and the PIPELINE_VERSION gets created and forwarded to downstream jobs.

          grant jew added a comment - downgraded to 2.0 and the PIPELINE_VERSION gets created and forwarded to downstream jobs.

          Ian Bamforth added a comment - - edited

          Now also released in 1.651.2.

          Ian Bamforth added a comment - - edited Now also released in 1.651.2.
          Jeebitesh Kalantri made changes -
          Labels New: 2.0 delivery-pipeline-plugin-0.9.9 jenkins2.0

          Jeebitesh Kalantri added a comment -

          We need fix for this ASAP.
          Workaround :- Use plugin Formatted Version Number to create PIPELINE_VERSION environment variable this should fix the issue for time being

          Jeebitesh Kalantri added a comment - We need fix for this ASAP. Workaround :- Use plugin Formatted Version Number to create PIPELINE_VERSION environment variable this should fix the issue for time being

          Daniel Beck added a comment -

          Probably SECURITY-170 from https://wiki.jenkins-ci.org/display/SECURITY/Jenkins+Security+Advisory+2016-05-11 and the plugin sending parameters that aren't defined on the job. Workaround: Define the parameter on the job.

          Daniel Beck added a comment - Probably SECURITY-170 from https://wiki.jenkins-ci.org/display/SECURITY/Jenkins+Security+Advisory+2016-05-11 and the plugin sending parameters that aren't defined on the job. Workaround: Define the parameter on the job.

          Pablo González added a comment -

          yeap! that is the reason. When the variable is declared in task then it is created, but yet still an issue when the variable is passed to another task.
          Although the variable is declared in the task, still blank until end. In the parameters list there are two variables PIPELINE_VERSION one with the value created in the first task and another one in blank.
          i can't make the workaround works in docker version yet.

          Pablo González added a comment - yeap! that is the reason. When the variable is declared in task then it is created, but yet still an issue when the variable is passed to another task. Although the variable is declared in the task, still blank until end. In the parameters list there are two variables PIPELINE_VERSION one with the value created in the first task and another one in blank. i can't make the workaround works in docker version yet.
          Tommy Tynjä made changes -
          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ä added a comment -

          This issue is also mentioned on: https://wiki.jenkins-ci.org/display/JENKINS/Plugins+affected+by+fix+for+SECURITY-170

          Tommy Tynjä added a comment - This issue is also mentioned on: https://wiki.jenkins-ci.org/display/JENKINS/Plugins+affected+by+fix+for+SECURITY-170
          Tommy Tynjä made changes -
          Status Original: Open [ 1 ] New: In Progress [ 3 ]

            tommysdk Tommy Tynjä
            gjew grant jew
            Votes:
            5 Vote for this issue
            Watchers:
            9 Start watching this issue

              Created:
              Updated:
              Resolved: