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

Promoted builds not picking up injected env settings as of 2.17 (2.15 is ok)

    • Icon: Bug Bug
    • Resolution: Duplicate
    • Icon: Major Major
    • promoted-builds-plugin
    • None
    • Linux xxxx 3.11.0-13-generic #20-Ubuntu SMP Wed Oct 23 07:38:26 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
      jenkins 1.553

      Promoted build action to copy files into a releases folder using this path:

      /u0/releases/Server/${BRANCH}/QA/${PROMOTED_NUMBER}

      works fine in 2.15, promotion log shows:

      [SCP] uploading file: '/home/jenkins/releases/Server/develop/QA/397/CHANGES'
      [SCP] uploading file: '/home/jenkins/releases/Server/develop/QA/397/Packages.gz'

      and fails to replace the ${BRANCH} env token when using 2.17:

      [SCP] uploading file: '/home/jenkins/releases/Server/${BRANCH}/QA/390/CHANGES'
      [SCP] uploading file: '/home/jenkins/releases/Server/${BRANCH}/QA/390/Packages.gz'

      Note that ${BRANCH} is not being replaced by "develop"

          [JENKINS-22094] Promoted builds not picking up injected env settings as of 2.17 (2.15 is ok)

          Bruce Edge created issue -
          Bruce Edge made changes -
          Link New: This issue duplicates JENKINS-22679 [ JENKINS-22679 ]
          Bruce Edge made changes -
          Resolution New: Duplicate [ 3 ]
          Status Original: Open [ 1 ] New: Closed [ 6 ]
          R. Tyler Croy made changes -
          Workflow Original: JNJira [ 154173 ] New: JNJira + In-Review [ 207489 ]
          Michael Fowler made changes -
          Link New: This issue is related to JENKINS-27883 [ JENKINS-27883 ]

            Unassigned Unassigned
            bedge Bruce Edge
            Votes:
            2 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: