Ah, you mean one global stage0 for all branches - didn't think of that. Also thanks for the above goodies. Ill check them out.
Regards, Lars onsdag 28 april 2021 kl. 16:42:22 UTC+2 skrev ice...@googlemail.com: > If you use gerrit-trigger you don't need to discover new branches. You get > the GERRIT_BRANCH from the trigger data. > > > A typical checkout looks like: > checkout ([poll: false, > scm: [$class: 'GitSCM', > branches: [[name: '$GERRIT_BRANCH']], > doGenerateSubmoduleConfigurations: false, > extensions: [[$class: 'BuildChooserSetting', > buildChooser: [$class: > 'GerritTriggerBuildChooser']], > ], > gitTool: 'Default', > submoduleCfg: [], > userRemoteConfigs: [[credentialsId: 'XXXX', > refspec: '$GERRIT_REFSPEC', > url: 'ssh://<host > here>/$GERRIT_PROJECT']] > ] > ]) > > > > lar...@gmail.com schrieb am Mittwoch, 28. April 2021 um 13:41:04 UTC+2: > >> onsdag 28 april 2021 kl. 11:41:45 UTC+2 skrev ice...@googlemail.com: >> >>> lar...@gmail.com schrieb am Mittwoch, 28. April 2021 um 10:51:59 UTC+2: >>> >>>> Thanks. What I want to achieve in the end is a pipeline with a stage0 >>>> check for uploaded patches, and if that passes have it do a +1 verify >>>> vote. >>>> Then a multistage job that runs of what is submitted. >>>> And I want the pipelines created automatically for master and each >>>> release branch. I thought I could do this some how with multi-branch and >>>> some kind of gerrit trigger, either the gerrit-trigger plugin or via >>>> gerrit >>>> webhook plugin.. >>>> Regards, Lars >>>> >>> >>> Well, that is possible. You can combine Jenkinsfile and gerrit trigger >>> (I would do that for the stage0 checks), just checkout scm is not possible >>> at the moment, yuo need to use the var from gerrit trigger in the checkout >>> incantation. >>> >>> >> Ok, even for multi-branch so it can discover new branches? I have not >> found a method for that to setup gerrit-triggers for new patch-sets. Do you >> have any hints? >> >> >>> For the submitted checks multibranch + gerrit-review + (gerrit webhook) >>> will work. >>> >> -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/648619d0-d698-4804-9822-effd59271121n%40googlegroups.com.
