When you say "This is the first time the jobs were triggered", I think you mean that the jobs were defined and had not yet run. If that is the case, then I think the behavior you're seeing seems reasonable.
The webhook causes the jobs to poll the repo. The poll of the repo shows that there are changes on each of those branches which have not yet been built. When there are changes on a branch which have not been built, the job runs to build those changes. Once those changes are built, future checks for changes on that branch will see that there are no changes to be built. It may be possible to limit the start of polling to only specific branches by passing a "branch=your_branch_name" parameter with the webhook, but I don't have experience with that yet. Mark Waite On Fri, Aug 7, 2015 at 3:40 PM Siddharth Bhaskar < [email protected]> wrote: > We have a internal enterprise Github repo, and i have multiple feature > branches. I am facing a issue with triggering a build on a specific branch. > I have configured jobs for each of the feature branches. There is one > jenkins job for one feature branch. The first time i commit a code, it also > triggers builds for jobs with other branches. > > > Steps to reproduce the problem: > > 1.We have a internal Github for enterprise. For my repo, i have setup > webhook for github as below > > Settings -> Webhooks & Services -> Services > Select Jenkins (GitHub plugin) > Jenkins Hook Url: http://************/jenkins/github-webhook/ > > 2.For my 3 branches in github repo : branch1, branch2, branch3, i created > three jobs in jenkins:Job1, Job2, Job3 with SCM configured as below > > Source Code Management: > Repo URL: git@********/********.git > Branches to Build: refs/heads/BRANCH_NAME > > Build Trigger: Build when a change is pushed to GitHub > > 3.On committing code to my branch : branch1. It triggers all the 3 jobs in > jenkins: Job1, Job2, Job3. Note:This is the first time that the jobs were > triggered. > > 4.On committing code for the second time to branch: branch1. It triggers > only Job1 in jenkins. > > > It looks like first time all jobs are getting executed for the repo, > irrespective of the branch. > > Details on my jenkins setup: Jenkins Version: 1.565.1, GitHub plugin: 1.9.1 > > > Any help/guidance to solve this issue is appreciated. > > Please let me know if i missed any details > > > FYI: I tried steps listed > http://kohsuke.org/2011/12/01/polling-must-die-triggering-jenkins-builds-from-a-git-hook/ > > -- > 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]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/jenkinsci-users/e1f9b736-fbd8-45a9-a949-18d396d870cd%40googlegroups.com > <https://groups.google.com/d/msgid/jenkinsci-users/e1f9b736-fbd8-45a9-a949-18d396d870cd%40googlegroups.com?utm_medium=email&utm_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > -- 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]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CAO49JtF27JSLx8Avp%3DF0K2j_4gHEgk7iwMiQ94YR2n-_QTWPJQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
