News for hackers. Stuff that matters.
Re:Use Jenkins "Build Per Branch" for Git Feature Branch Dev... by ddlatham on Wednesday June 13, 2012 @12:21AM (#4104304)
One disadvantage is that with multiple, short-lived branches, manually creating CI to confirm that all tests continue to pass becomes far too much overhead. It must be automated for this model to work and be trusted. "Jenkins Build Per Branch" is the answer to that problem.

We use something close to this model, but there's no need to create separate Jenkins jobs for each branch.

We have a single job that takes the git branch as a parameter and can run all of the automated tests (and other jobs for builds, etc.). There is a script that watches for new pull requests and automatically triggers the Jenkins job to run all the tests on that pull request to verify that they pass before the reviewer merges in to master.

Re:Use Jenkins "Build Per Branch" for Git Feature Branch Dev... by tomstuart on Wednesday June 13, 2012 @06:18AM (#4105176)
FYI this is something that Travis (http://travis-ci.org/) can now do; for example, see the travisbot comments on https://github.com/sinatra/sinatra/pull/521. It's not finished yet, but they've got more information at http://about.travis-ci.org/blog/announcing-pull-request-supp....
Re:Use Jenkins "Build Per Branch" for Git Feature Branch Dev... by steverb on Wednesday June 13, 2012 @08:11AM (#4105429)
We do the same using Team City and Git (on the .NET stack) although we don't merge to master until the feature in question has gone through manual QA as well.

We have 5 QA servers and a dashboard where the tester can point any of the QA servers to a feature branch. Works awesomely.

Re:Use Jenkins "Build Per Branch" for Git Feature Branch Dev... by tednaleid on Wednesday June 13, 2012 @12:26AM (#4104318)
Thats an interesting approach. If a branch is broken, which causes the job to fail, how do you communicate that and monitor when it's actually fixed (rather than another branch getting run which "fixes" it)?
Re:Use Jenkins "Build Per Branch" for Git Feature Branch Dev... by ddlatham on Wednesday June 13, 2012 @12:32AM (#4104333)
We have email notifications on test failures, so the creator and reviewer of the pull request can see it fails. Haven't done it yet, but would like to extend it to report back the result as a comment directly on the pull request.