I tried this arrangement some time ago and ended up dropping it, because it can't work the way I (and you) want it to work.
When the webhook 'poke' comes in, the job will look at the repository to see what has changed and determine whether any builds should be launched. It will match up the changes in the repository to the list of branch(es) it's been configured to watch/build. When the branch list is a build parameter, there's really nothing that can be matched against, although as you say it does somehow seem to remember the last branch that was built and if that branch changes it will build again. Also, having the same job build from multiple branches causes other problems; the build 'trend' is not useful, because the last 5 builds may all have been different branches. If you are using any plugins that do trend analysis (warnings, code coverage, etc.) they'll have the same problem. I'm going to experiment with using the Job Generator plugin instead, to create jobs from a template that will automatically build all the branches we care about (one for each branch), and those jobs can be manully triggered if needed. ----- Original Message ----- From: [email protected] To: [email protected] At: May 3 2013 16:14:13 We're using the Github webook and the "Build when a change is pushed to GitHub" for our build. The build is currently parametrized and takes a "Branch" String param which I substitue into the "Branches to build" field with ${Branch}. The default for the value is the name of our stable branch. I know that I can manually invoke a build and pass a branch name. What I'm trying to figure out is what gets built automatically when changes are pushed to Github? Which branches will it consider? In some limited testing, it's definitely not building all changes. Seems to be related to the last branch name that was used for the build. Any advice here? -- 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. -- 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.
