If you have created a post-update hook on the remote repository to notify Jenkins when a push occurs, you might consider configuration as: Branch to build: **
Checkout to specific local branch: ** (requires Git plugin 2.4.4) Build Triggers: Poll SCM but leave the schedule blank. The job will only be scheduled if the post-update hook sends a push notification as described here: https://wiki.jenkins-ci.org/display/JENKINS/Git+Plugin#GitPlugin-Pushnotificationfromrepository This configuration will schedule a build whenever a push to the remote takes place. Pro: single jenkins job builds any branch when it is pushed to the remote Con: build history has mixed branches. See earlier comment from Mark Waite. On Thursday, March 24, 2016 at 8:58:52 AM UTC-7, builderj wrote: > > Hello experts > > I'm just wondering if there is a way to set up ONE CI build job in Jenkins > for 4 different branches. > > Here is the scenario. Dev team will be working on 4 different feature > branches and check in changes regularly. So the parent CI job should looks > for changes in all the 4 branches and trigger the build for the branches > where changes were checked in. > > Appreciate any help. > > Thanks in advance. > -- 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/6dbdb120-b9b6-4883-943e-f9d2dbc6ba74%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
