Your setup is more akin to requiring multiple jobs than a multi config job. As the source you want to build is different. As it is different you will want to build only the branch that changed on any commit, not all of them.
Alternativly you can have a single normal job and have git checkout whichever branch changed - however I do not recommend this as trend reports become meaningless (and you may have different people maintinaing different branches and so want to change other settings like email notification etc.) /James From: [email protected] [mailto:[email protected]] On Behalf Of kabustalek Sent: 17 May 2013 08:38 To: [email protected] Subject: multi configuration project with different git branches Hi Can someone tell me whats the best way to checkout different git branches on a multi configuration project? i have a project (lets call it API) which has a java 1.6 branch and a java 1.7 branch, so i created a new multi configuration project with JDK1.6 and JDK1.7 (soon there will be a JDK1.8 i guess). how can i now configure the git checkout in jenkins to checkout a different branch regarding on the parameter? at the moment, jenkins always checks out the 1.6 branch because the API project is configured to use ** as repository. Unfrotunately i can not define it on sub-project basis. Regards, Oli -- 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 [email protected]<mailto:[email protected]>. For more options, visit https://groups.google.com/groups/opt_out. -- 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 [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
