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

Starting with >1.73 global environment variables overrule build specific parameter variables

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Blocker Blocker
    • envinject-plugin
    • None
    • WinXP

      Not sure if this is a bug or a feature. I used to have global environment variables set via "Manage Jenkins->Configure System->Environment variables" and used these values as default values for my job. Per job I have use "paramterized builds" to overrule these global variables. After updating to more recent envinject plugin it seems like the logic has been flipped upside down. The global env vars overrule the parameter vars and I have not figured out how to enable the old logic?! Is it possible to make this behaviour configurable?

          [JENKINS-16380] Starting with >1.73 global environment variables overrule build specific parameter variables

          Hans Baer created issue -
          Gregory Boissinot made changes -
          Resolution New: Fixed [ 1 ]
          Status Original: Open [ 1 ] New: Resolved [ 5 ]
          R. Tyler Croy made changes -
          Workflow Original: JNJira [ 147198 ] New: JNJira + In-Review [ 192276 ]
          pjdarton made changes -
          Link New: This issue relates to JENKINS-14437 [ JENKINS-14437 ]

            gbois Gregory Boissinot
            maedula Hans Baer
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: