-
Improvement
-
Resolution: Unresolved
-
Major
-
Jenkins 2.7.3, Gerrit Trigger Plugin 2.22.0
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.
- is duplicated by
-
JENKINS-40389 Gerrit support for Multibranch Pipeline
- Closed
- relates to
-
JENKINS-26010 Workflow plugin not working with with Gerrit event
- Resolved
-
JENKINS-26102 Workflow step to wait for approval
- Open
-
JENKINS-26103 Workflow step to send approval "vote" to a change
- Open
- links to