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

Pipeline support in EnvInject

XMLWordPrintable

    • Pipeline support in EnvInject

      EnvInject does not support Pipeline now. Though there are many workarounds, it would be useful to address particular integration use-cases

          [JENKINS-42614] Pipeline support in EnvInject

          Oleg Nenashev created issue -
          Oleg Nenashev made changes -
          Labels New: pipeline
          Oleg Nenashev made changes -
          Epic Child New: JENKINS-38483 [ 174665 ]
          Oleg Nenashev made changes -
          Epic Child New: JENKINS-40412 [ 177075 ]
          Oleg Nenashev made changes -
          Epic Child New: JENKINS-26569 [ 160239 ]
          Oleg Nenashev made changes -
          Epic Child New: JENKINS-42875 [ 179880 ]
          Oleg Nenashev made changes -
          Epic Child New: JENKINS-42876 [ 179881 ]
          Oleg Nenashev made changes -
          Epic Child New: JENKINS-43535 [ 180851 ]
          Oleg Nenashev made changes -
          Epic Child New: JENKINS-43536 [ 180852 ]

          Nick Christopher added a comment -

          Here's the use case I have today.  We work on sprint branches in our SCM.  As we advance sprint to sprint we change the branch name. To handle this we set a global variable (SPRINT_BRANCH) with the branch name as its value.  Jenkins jobs designed to always focus on the "current sprint"  use that global variable ${SPRINT_BRANCH} as the branch name in the SCM checkout.  Elsewhere in Jenkins, using this variable works with the plugin SCM operations. This pattern allows us to migrate any number of jobs from one branch to the next by simply changing the value of SPRINT_BRANCH.  With Pipeline, a variable can not be used as the branch name.  

          Nick Christopher added a comment - Here's the use case I have today.  We work on sprint branches in our SCM.  As we advance sprint to sprint we change the branch name. To handle this we set a global variable (SPRINT_BRANCH) with the branch name as its value.  Jenkins jobs designed to always focus on the "current sprint"  use that global variable ${SPRINT_BRANCH} as the branch name in the SCM checkout.  Elsewhere in Jenkins, using this variable works with the plugin SCM operations. This pattern allows us to migrate any number of jobs from one branch to the next by simply changing the value of SPRINT_BRANCH.  With Pipeline, a variable can not be used as the branch name.  

            Unassigned Unassigned
            oleg_nenashev Oleg Nenashev
            Votes:
            22 Vote for this issue
            Watchers:
            36 Start watching this issue

              Created:
              Updated: