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

Injected env variables not available for use in processing promotion.

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Major Major
    • promoted-builds-plugin
    • None
    • Ubuntu 12.04
    • Promoted Builds 3.3

      I inject a var from svn branches, names BRANCH so I can pull from different svn branches for a build.
      When I promote a build, I want to use this same $BRANCH variable to differentiate between branches for both svn tag location and copy-artifact locations.

      However, during the promotion processing this BRANCH variable is unset.
      It should be read back from the injected variables that were present at the time that build was made.

      Of course this requires that the injected variables file, injectedEnvVars.txt, be copied along with the artifacts to the promotion target location so they can be re-read again later for subsequent promotions.

          [JENKINS-14169] Injected env variables not available for use in processing promotion.

          J D added a comment -

          This is a huge issue for me when using promotions. I am constantly resetting environment variables in each promotion because they aren't carried over from the build. Is there any traction on this issue? It has be around for over 3 years now.

          J D added a comment - This is a huge issue for me when using promotions. I am constantly resetting environment variables in each promotion because they aren't carried over from the build. Is there any traction on this issue? It has be around for over 3 years now.

          Oleg Nenashev added a comment -

          ADAICT Promoted Builds 3.3 fixes it by enabling EnvInject plugin build wrappers

          Oleg Nenashev added a comment - ADAICT  Promoted Builds 3.3  fixes it by enabling EnvInject plugin build wrappers

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

              Created:
              Updated:
              Resolved: