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

Unable to override global envs after update to 2.1.4

    XMLWordPrintable

    Details

    • Similar Issues:
    • Released As:
      2.1.6

      Description

      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.

        Attachments

          Issue Links

            Activity

            Hide
            pjdarton pjdarton added a comment -

            This issue sounds very much like JENKINS-14437.

            Show
            pjdarton pjdarton added a comment - This issue sounds very much like JENKINS-14437 .
            Hide
            oleg_nenashev Oleg Nenashev added a comment -

            The regression impact is properly documented && the plugin 2.1.4 is marked as incompatible, so it should minimize the impact on users. 2.1.3 is also available through archives.

            Although I understand all the possible frustration by plugin users, I decided to NOT work on this issue. The regression has been introduced by me by a fix created during the working time, and I cordially apologize for any inconvenience it caused. Taking the proper regression announcement my team decided to not fix the regression in foreseeable future, because it is focused on other much more important tasks around Jenkins stability. I have no time to work on it during my spare time, because I am focused on the Jenkins core maintenance and other community work. On the other hand, I will be happy to review and deliver pull requests if somebody proposes them.

            I would also like to highlight that the plugin is waiting for adoption for more than two years. During all this time I was trying to keep this plugin afloat by reviewing the incoming pull requests, fixing defects and keeping the codebase up to date to simplify the handover. But I have not been using this plugin on my own so that such maintenance was a bit lame. I invite all active users to contribute to the plugin by taking ownership of this plugin and of EnvInject API. I am happy to provide any required knowledge transfers and do some assistance during the first months of maintenance

            Show
            oleg_nenashev Oleg Nenashev added a comment - The regression impact is properly documented && the plugin 2.1.4 is marked as incompatible, so it should minimize the impact on users. 2.1.3 is also available through archives. Although I understand all the possible frustration by plugin users, I decided to NOT work on this issue. The regression has been introduced by me by a fix created during the working time, and I cordially apologize for any inconvenience it caused. Taking the proper regression announcement my team decided to not fix the regression in foreseeable future, because it is focused on other much more important tasks around Jenkins stability. I have no time to work on it during my spare time, because I am focused on the Jenkins core maintenance and other community work. On the other hand, I will be happy to review and deliver pull requests if somebody proposes them. I would also like to highlight that the plugin is waiting for adoption for more than two years. During all this time I was trying to keep this plugin afloat by reviewing the incoming pull requests, fixing defects and keeping the codebase up to date to simplify the handover. But I have not been using this plugin on my own so that such maintenance was a bit lame. I invite all active users to contribute to the plugin by taking ownership of this plugin and of EnvInject API. I am happy to provide any required knowledge transfers and do some assistance during the first months of maintenance
            Hide
            ickersep ickersep added a comment -

            This seems to be fixed in 2.1.6

            Show
            ickersep ickersep added a comment - This seems to be fixed in 2.1.6
            Hide
            oleg_nenashev Oleg Nenashev added a comment -

            it's not

            Show
            oleg_nenashev Oleg Nenashev added a comment - it's not
            Hide
            flozano Francisco Lozano added a comment -

            We're heavily affected by this issue and can't upgrade from 2.1.3 because of it.

            Show
            flozano Francisco Lozano added a comment - We're heavily affected by this issue and can't upgrade from 2.1.3 because of it.

              People

              • Assignee:
                Unassigned
                Reporter:
                jbochenski Jakub Bochenski
              • Votes:
                13 Vote for this issue
                Watchers:
                23 Start watching this issue

                Dates

                • Created:
                  Updated: