[JIRA] (JENKINS-40389) Gerrit support for Multibranch Pipeline
Title: Message Title Mike Kasberg commented on JENKINS-40389 Re: Gerrit support for Multibranch Pipeline This duplicates JENKINS-38046. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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.
[JIRA] (JENKINS-38046) Gerrit Trigger Plugin Should be a Source for Multibranch Pipeline
Title: Message Title
Mike Kasberg edited a comment on JENKINS-38046
Re: Gerrit Trigger Plugin Should be a Source for Multibranch Pipeline
Here is an (ugly) workaround:Use a normal pipeline job with the gerrit trigger. Have the pipeline execute a simple bootstrapping script, which loads the correct Jenkinsfile. The script might look like this:{ { code} #!/usr/bin/env groovynode('label') {stage 'Checkout' {// Checkout the patch set we're testing.// See https://wiki.jenkins-ci.org/display/JENKINS/Gerrit+Trigger#GerritTrigger-PipelineJobs// Using Gerrit Trigger with Pipeline jobs.git url: 'ssh://foo@gerrit/repository'def changeBranch = "change-${GERRIT_CHANGE_NUMBER}-${GERRIT_PATCHSET_NUMBER}"sh "git fetch origin ${GERRIT_REFSPEC}:${changeBranch}"sh "git checkout ${changeBranch}"sh "git clean -d -f -q -x"}// The rest comes from the repository itself!load 'Jenkinsfile'} {code } }
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
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.
[JIRA] (JENKINS-38046) Gerrit Trigger Plugin Should be a Source for Multibranch Pipeline
Title: Message Title
Mike Kasberg commented on JENKINS-38046
Re: Gerrit Trigger Plugin Should be a Source for Multibranch Pipeline
Here is an (ugly) workaround: Use a normal pipeline job with the gerrit trigger. Have the pipeline execute a simple bootstrapping script, which loads the correct Jenkinsfile. The script might look like this: {{ #!/usr/bin/env groovy node('label') { stage 'Checkout' { // Checkout the patch set we're testing. // See https://wiki.jenkins-ci.org/display/JENKINS/Gerrit+Trigger#GerritTrigger-PipelineJobs // Using Gerrit Trigger with Pipeline jobs. git url: 'ssh://foo@gerrit/repository' def changeBranch = "change-$ {GERRIT_CHANGE_NUMBER} -$ {GERRIT_PATCHSET_NUMBER} " sh "git fetch origin $ {GERRIT_REFSPEC} :$ {changeBranch}" sh "git checkout ${changeBranch} " sh "git clean -d -f -q -x" } // The rest comes from the repository itself! load 'Jenkinsfile' } }}
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
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.
[JIRA] (JENKINS-38046) Gerrit Trigger Plugin Should be a Source for Multibranch Pipeline
Title: Message Title Mike Kasberg created an issue Jenkins / JENKINS-38046 Gerrit Trigger Plugin Should be a Source for Multibranch Pipeline Issue Type: Improvement Assignee: rsandell Components: gerrit-trigger-plugin Created: 2016/Sep/07 11:38 PM Environment: Jenkins 2.7.3, Gerrit Trigger Plugin 2.22.0 Labels: pipeline Priority: Major Reporter: Mike Kasberg 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. Add Comment
