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

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.

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.

• environment: Jenkins 2.7.3, Gerrit Trigger Plugin 2.22.0

The issue names no source files or tests. Start by comparing the existing GitHub Multibranch implementation with the gerrit-trigger-plugin integration points, then define how Gerrit repositories, branches, and change requests map to separate sub-jobs and how each patch set supplies its Jenkinsfile. Done means Gerrit can be selected as a multibranch source with per-branch and per-change history.