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

Unable to override global envs after update to 2.1.4

    • 2.1.6

      We have a global setting of JIRA_URL=jira.acme.com

      In some jobs we override this in the "Prepare an environment for the run" section to JIRA_URL=jira-staging.acme.com

       

      After upgrading to 1.24 this stopped working. The effective value as seen in shell scripts is jira.acme.com

       

      Setting the value in a "Inject environment variables" build step also has no effect.

      The only thing that has an effect is to set the value inside the shell script.

          [JENKINS-47370] Unable to override global envs after update to 2.1.4

          Jakub Bochenski created issue -
          Jakub Bochenski made changes -
          Link New: This issue relates to JENKINS-47364 [ JENKINS-47364 ]
          Jakub Bochenski made changes -
          Labels New: regression
          arnaud dovi made changes -
          Priority Original: Critical [ 2 ] New: Blocker [ 1 ]
          pjdarton made changes -
          Link New: This issue relates to JENKINS-14437 [ JENKINS-14437 ]
          CloudBees Inc. made changes -
          Remote Link New: This issue links to "CloudBees Internal OSS-2517 (Web Link)" [ 20157 ]
          Oleg Nenashev made changes -
          Assignee Original: Oleg Nenashev [ oleg_nenashev ]
          Oleg Nenashev made changes -
          Assignee New: Oleg Nenashev [ oleg_nenashev ]
          Oleg Nenashev made changes -
          Assignee Original: Oleg Nenashev [ oleg_nenashev ]
          ickersep made changes -
          Released As New: 2.1.6
          Resolution New: Fixed [ 1 ]
          Status Original: Open [ 1 ] New: Fixed but Unreleased [ 10203 ]
          ickersep made changes -
          Status Original: Fixed but Unreleased [ 10203 ] New: Resolved [ 5 ]

            Unassigned Unassigned
            jbochenski Jakub Bochenski
            Votes:
            14 Vote for this issue
            Watchers:
            25 Start watching this issue

              Created:
              Updated:
              Resolved: