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

[austin.phill...@planetinnovation.com.au (JIRA)]

Title: Message Title

Austin Phillips commented on JENKINS-38046   Re: Gerrit Trigger Plugin Should be a Source for Multibranch Pipeline Here's another workaround using a normal pipeline job with the gerrit trigger plugin. Set up Gerrit triggers as per normal Set up Pipeline with 'Pipeline script from SCM', using the Gerrit environment variables as source information for the Jenkinsfile Use a Jenkinsfile in your source as normal, complete with 'checkout scm' step. Configuration of the Pipeline SCM is as follows: Set 'Repository URL' to $GERRIT_SCHEME://$GERRIT_HOST:$GERRIT_PORT/$GERRIT_PROJECT Click the 'Advanced' button and set 'Refspec' to $GERRIT_REFSPEC:$GERRIT_REFSPEC Set 'Branches to build' to $GERRIT_REFSPEC If desired, add 'Advanced clone behaviours' with 'Shallow clone' enabled with a 'Shallow clone depth' set to 1. Then, in your Gerrit repository Jenkins file:    node {     stage('Checkout') {         checkout scm    } stage('Build') { echo "Building...'    } }   Additional information: The advantage of this method is that there is only a single Jenkinsfile specification which lives in your SCM. The Pipeline configuration can be consistent across multiple projects as all of the SCM information is derived from Gerrit Trigger environment variables.  The Gerrit Trigger parameters become the source for the Jenkinsfile pipeline definition. The Jenkins master will check out a copy of the repository on the master to get access to the Jenkinsfile (ie Not in a workspace) The 'checkout scm' step inside the pipeline will check out the code according to the SCM information entered in the pipeline step.  Because the checkout occurs inside a 'node' block, the source repo ends up being checked out twice.  Once to obtain the Jenkinsfile by the master, once as part of the Jenkinsfile pipeline step.  The shallow clone options may help speed things up here. This has only been tested with the 'Patchset Created' Gerrit Trigger type.   Add Comment   This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.