Hi there,
It's not automated to the extent that this Bamboo feature is, but for
select projects I have two Jenkins jobs: one for master, and another job
cloned from the first, but using the "Inverse" choosing strategy in the
git plugin -- i.e. it builds all branches *except* for master. The only
other change I make to the "feature branch" job is to discard all but
the last five builds and disable the trend graphs.
Or if you always name your feature branches like "feature/*", then you
can just enter that as your git branch, rather than using the Inverse
strategy.
So building feature branches is definitely possible today with minimal
effort, but sure -- the ability to do this completely automatically
(i.e. without a second job) would be cool. Thanks for the info.
Regards,
Chris
On 04/27/2012 07:06 PM, Gustavo Leite de Mendonça Chaves wrote:
This is the title of an Atlassian Blog Post
<http://blogs.atlassian.com/2012/04/bamboofeature-branch-continuous-integration-hg-git/>
which tells about a new feature in Bamboo 4 called Plan Branches. The
idea (as I understood it from the post, since I don't use Bamboo myself)
is that after you have configured a job for a project and pointed it to
the SCM master/trunk, you can then automatically create derived jobs
which share almost every configuration with the master's job but which
fetch the source from a specific branch. You can even enable "automatic
branch detection" so that these derived jobs are created automatically
when Bamboo detects that a new branch has been created.
Does anyone knows anything like that for Jenkins? I'd love to be able to
use it.
Gustavo.
