[Buildbot-devel] How to force a triggered build to always use a particular branch

[Bailey, Darragh]

> > -----Original Message-----
> > From: Bailey, Darragh 
> > Sent: 30 July 2009 15:42
> > To: buildbot-devel list
> > Subject: [Buildbot-devel] How to force a triggered build to 
> > always use a particular branch
> > 
> > 
> > Is it possible to force a build that has been triggered by 
> > another build to always build from a particular branch and 
> > not from the branch used by the build that triggered it?
> > 
> > defaultBranch allows the branch to be overridden, and I don't 
> > see anything that ensures it is always set to the same value.
> > 
> > Plan on trying to set the branch property via the trigger 
> > step for the next run, but I would have preferred to limit it 
> > to the source checkout step of the triggered build rather 
> > than the trigger step of every other build.
> 
> Never mind, I missed the importance of using svnurl where you 
> don't want to use branches.

Which then results in an exception should a build step using the svnurl option to ignore branches is triggered by a build that uses branches.

Fails on the following line "462      assert not branch # we need baseURL= to use branches" in /usr/lib64/python2.3/site-packages/buildbot/steps/source.py.

Forcing branch to None via the trigger doesn't look likely to work. It didn't work when I tried using that method to force the branch used in the triggered build to be trunk. So can't see it working here.



Looking for some suggestions, so going to provide a little more detail on what I'm trying to do.

I have 3 builders producing iso images from 3 different branches. Subsequently these need to unpacked and the files in the iso image are signed with a digital signature. The code that handles the code signing is kept uptodate on the trunk since there are various changes made to the software that does the signing. By keeping it separate this way, I can go back and resign older revision builds.


Thinking of maybe trying to tackle this from a different angle
Maybe try to create a new class based on the MaildirService that instead monitors the target directory where the original builders upload their built isos to and then use that to trigger the builder that then processes these files so that it can work from the trunk branch while handling output from builers operating on a number of different branches.

--
Regards,
Darragh Bailey

Systems Software Engineer
Hewlett Packard Galway Ltd.

Postal Address:    Hewlett Packard Galway Limited, Ballybrit Business Park, Galway
Registered Office: Hewlett Packard Galway Limited, 63-74 Sir John Rogerson's Quay Dublin 2
Registered Number: 361933