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

0.6 breaks backwards compatibility because of ENV vars now have digits appended to them

XMLWordPrintable

      This check-in(https://github.com/jenkinsci/multiple-scms-plugin/commit/2490dd7e48cf485f91797a14a5e2a700848ae76a) broke backwards compatibility for the Multi SCM plugin by appending _X digits to ENV vars that existed on more than 1 SCM config.

      Any job that relies on the Multi SCM plugin and counted on the last SCM configuration being passed into the environment without any _X digits is now broken.

          [JENKINS-34249] 0.6 breaks backwards compatibility because of ENV vars now have digits appended to them

          Antek Baranski created issue -
          Antek Baranski made changes -
          Description Original: This checking (https://github.com/jenkinsci/multiple-scms-plugin/commit/2490dd7e48cf485f91797a14a5e2a700848ae76a) broke backwards compatibility for the Multi SCM plugin by appending _X digits to ENV vars that existed on more than 1 SCM config.

          Any job that relies on the Multi SCM plugin and counted on the last SCM configuration being passed into the environment is now broken.           		New: This check-in(https://github.com/jenkinsci/multiple-scms-plugin/commit/2490dd7e48cf485f91797a14a5e2a700848ae76a) broke backwards compatibility for the Multi SCM plugin by appending _X digits to ENV vars that existed on more than 1 SCM config.

          Any job that relies on the Multi SCM plugin and counted on the last SCM configuration being passed into the environment is now broken.
          Antek Baranski made changes -
          Description Original: This check-in(https://github.com/jenkinsci/multiple-scms-plugin/commit/2490dd7e48cf485f91797a14a5e2a700848ae76a) broke backwards compatibility for the Multi SCM plugin by appending _X digits to ENV vars that existed on more than 1 SCM config.

          Any job that relies on the Multi SCM plugin and counted on the last SCM configuration being passed into the environment is now broken.           		New: This check-in(https://github.com/jenkinsci/multiple-scms-plugin/commit/2490dd7e48cf485f91797a14a5e2a700848ae76a) broke backwards compatibility for the Multi SCM plugin by appending _X digits to ENV vars that existed on more than 1 SCM config.

          Any job that relies on the Multi SCM plugin and counted on the last SCM configuration being passed into the environment without any _X digits is now broken.
          Antek Baranski made changes -
          Summary Original: 0.6 breaks backwards compatibility because of ENV vars now having digits appended to them New: 0.6 breaks backwards compatibility because of ENV vars now have digits appended to them

          Antek Baranski added a comment - - edited

          Fixed: https://github.com/jenkinsci/multiple-scms-plugin/pull/19

          Antek Baranski added a comment - - edited Fixed: https://github.com/jenkinsci/multiple-scms-plugin/pull/19
          Antek Baranski made changes -
          Status Original: Open [ 1 ] New: In Progress [ 3 ]
          R. Tyler Croy made changes -
          Workflow Original: JNJira [ 170309 ] New: JNJira + In-Review [ 185720 ]

            sauraus Antek Baranski
            sauraus Antek Baranski
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: