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

Gerrit Trigger Plugin Should be a Source for Multibranch Pipeline

XMLWordPrintable

      I want to use the new Multibranch Pipeline features of Jenkins with Gerrit source control.

      I should be able to choose Gerrit as the source for a multibranch pipeline. I should be able to select one or more repositories from Gerrit that each have their own Jenkinsfile. The pipeline would run the Jenkinsfile from the patch set that was pushed to Gerrit.

      There is no known workaround for this issue because one core requirement is to see each gerrit branch and change request as a different sub-job with its own history. This is essential because it allow you to know the build status of the branch instead of seeing a long queue of builds made on various branches and CRs, most likely full of failures.

      The behaviour described in this ticket is almost identical with the GitHub Multibranch implementation, the difference is that instead of having GitHub branches and PRs as the data source, we want to have Gerrit.

        1. 2017_07_13_09_15_19_exploratory_pipeline_Config_Jenkins_.png
          2017_07_13_09_15_19_exploratory_pipeline_Config_Jenkins_.png
          54 kB
        2. 2017_07_13_09_14_02_exploratory_pipeline_Config_Jenkins_.png
          2017_07_13_09_14_02_exploratory_pipeline_Config_Jenkins_.png
          45 kB

          [JENKINS-38046] Gerrit Trigger Plugin Should be a Source for Multibranch Pipeline

          Mike Kasberg created issue -
          Mike Kasberg made changes -
          Epic Link New: JENKINS-31152 [ 165808 ]
          Mike Kasberg made changes -
          Link New: This issue is duplicated by JENKINS-40389 [ JENKINS-40389 ]
          Stephen Connolly made changes -
          Labels Original: pipeline New: multibranch pipeline
          Sorin Sbarnea made changes -
          Description Original: I want to use the new Multibranch Pipeline features of Jenkins with Gerrit source control.

          I should be able to choose Gerrit as the source for a multibranch pipeline. I should be able to select one or more repositories from Gerrit that each have their own Jenkinsfile. The pipeline would run the Jenkinsfile from the patch set that was pushed to Gerrit.           		New: I want to use the new Multibranch Pipeline features of Jenkins with Gerrit source control.

          I should be able to choose Gerrit as the source for a multibranch pipeline. I should be able to select one or more repositories from Gerrit that each have their own Jenkinsfile. The pipeline would run the Jenkinsfile from the patch set that was pushed to Gerrit.

          There is *no known workaround* for this issue because one core requirement is to see *{color:#f79232}each gerrit branch and change request as a different build{color}* with its own history. This is essential because it allow you to know the build status of the branch instead of seeing a long queue of builds made on various branches and CRs, most likely full of failures.
          Sorin Sbarnea made changes -
          Description Original: I want to use the new Multibranch Pipeline features of Jenkins with Gerrit source control.

          I should be able to choose Gerrit as the source for a multibranch pipeline. I should be able to select one or more repositories from Gerrit that each have their own Jenkinsfile. The pipeline would run the Jenkinsfile from the patch set that was pushed to Gerrit.

          There is *no known workaround* for this issue because one core requirement is to see *{color:#f79232}each gerrit branch and change request as a different build{color}* with its own history. This is essential because it allow you to know the build status of the branch instead of seeing a long queue of builds made on various branches and CRs, most likely full of failures.
          		 New: I want to use the new Multibranch Pipeline features of Jenkins with Gerrit source control.

          I should be able to choose Gerrit as the source for a multibranch pipeline. I should be able to select one or more repositories from Gerrit that each have their own Jenkinsfile. The pipeline would run the Jenkinsfile from the patch set that was pushed to Gerrit.

          There is *no known workaround* for this issue because one core requirement is to see *{color:#f79232}each gerrit branch and change request as a different sub-job{color}* with its own history. This is essential because it allow you to know the build status of the branch instead of seeing a long queue of builds made on various branches and CRs, most likely full of failures.

          The behaviour described in this ticket is almost identical with the GitHub Multibranch implementation, the difference is that instead of having GitHub branches and PRs as the data source, we want to have Gerrit.
          Sorin Sbarnea made changes -
          Labels Original: multibranch pipeline New: gerrit multibranch pipeline
          Austin Phillips made changes -
          Attachment New: 2017_07_13_09_14_02_exploratory_pipeline_Config_Jenkins_.png [ 38855 ]
          Austin Phillips made changes -
          Attachment New: 2017_07_13_09_15_19_exploratory_pipeline_Config_Jenkins_.png [ 38856 ]
          Jesse Glick made changes -
          Link New: This issue relates to JENKINS-26102 [ JENKINS-26102 ]
          Jesse Glick made changes -
          Link New: This issue relates to JENKINS-26103 [ JENKINS-26103 ]

            lucamilanesio Luca Domenico Milanesio
            mkasberg Mike Kasberg
            Votes:
            48 Vote for this issue
            Watchers:
            57 Start watching this issue

              Created:
              Updated: