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

Gerrit Trigger Plugin Should be a Source for Multibranch Pipeline

    XMLWordPrintable

    Details

    • Similar Issues:

      Description

      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.

        Attachments

          Issue Links

            Activity

            mkasberg Mike Kasberg created issue -
            mkasberg Mike Kasberg made changes -
            Field Original Value New Value
            Epic Link JENKINS-31152 [ 165808 ]
            mkasberg Mike Kasberg made changes -
            Link This issue is duplicated by JENKINS-40389 [ JENKINS-40389 ]
            stephenconnolly Stephen Connolly made changes -
            Labels pipeline multibranch pipeline
            ssbarnea Sorin Sbarnea made changes -
            Description 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.
            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.
            ssbarnea Sorin Sbarnea made changes -
            Description 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.
            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.
            ssbarnea Sorin Sbarnea made changes -
            Labels multibranch pipeline gerrit multibranch pipeline
            austin_phillips Austin Phillips made changes -
            austin_phillips Austin Phillips made changes -
            jglick Jesse Glick made changes -
            Link This issue relates to JENKINS-26102 [ JENKINS-26102 ]
            jglick Jesse Glick made changes -
            Link This issue relates to JENKINS-26103 [ JENKINS-26103 ]
            jglick Jesse Glick made changes -
            Link This issue relates to JENKINS-26010 [ JENKINS-26010 ]
            jamesdumay James Dumay made changes -
            Remote Link This issue links to "CloudBees Internal OSS-2193 (Web Link)" [ 18390 ]
            jglick Jesse Glick made changes -
            Assignee rsandell [ rsandell ] lucamilanesio [ lucamilanesio ]
            jglick Jesse Glick made changes -
            Status Open [ 1 ] In Progress [ 3 ]

              People

              Assignee:
              lucamilanesio Luca Domenico Milanesio
              Reporter:
              mkasberg Mike Kasberg
              Votes:
              47 Vote for this issue
              Watchers:
              56 Start watching this issue

                Dates

                Created:
                Updated: