[Buildbot-devel] Buildbot configuration for multiple builders

[Byrne, David]

Thanks Darragh,

	I was able to get this to work.  It isn't a perfect solution as mentioned below because the blame list is not unique to each type.  It's too bad that there isn't a cleaner way to implement this.  Another addition I would like to see is a Scheduler that works like a combination of Nightly and a triggered scheduler.  I guess what I mean is a scheduler that sets the build to go off at a specific time (like midnight for example) when an event or series of events occur (like a source check-in).  I like what I've been able to do with buildbot so far.  I'm trying to use it in combination with Subversion and Roundup to manage my overall development process and work flow.

Thanks,
David Byrne

-----Original Message-----
From: Bailey, Darragh [mailto:dbailey at hp.com] 
Sent: Tuesday, July 17, 2007 1:42 PM
To: Byrne, David
Cc: buildbot-devel at lists.sourceforge.net
Subject: RE: [Buildbot-devel] Buildbot configuration for multiple builders


I think the problem is that you don't want to use dependent schedulers, but source change schedulers.

Have a look at the API's documentation, the following link contains details about the scheduler AnyBranchScheduler, which I believe is what would be used to schedule builds based on changes to the source code respository (I don't use it myself):

http://buildbot.net/repos/release/docs/reference/buildbot.scheduler.AnyBranchScheduler-class.html


It has a parameter "fileIsImportant", which looks to take as an argument, a callback function.

I suspect that the solution is to have different schedulers & builders for the tasks of builds based on source code changes, and build steps to checkout the distributables to UAT. Then specify different functions to be passed in as the argument "fileIsImportant" to filter out changes to the areas which are not of interest for a given scheduler.

I.e. FileIsImportantA should filter out any checkin's of the distributables, and FileIsImportantB should filter out any checkin's of anything except the distributables.


I don't think its perfect since I suspect that checkin's of distributables will still show up in the buildbot changelog details for any source code builds, but it should prevent them from triggering such builds.


--
Regards,
Darragh Bailey

Systems Software Engineer
Hewlett Packard Galway Ltd.
+353 91 75-4674

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

_______________________________________________
The contents of this message and any attachments to it are confidential and may be legally privileged. If you have received this message in error you should delete it from your system immediately and advise the sender.
To any recipient of this message within HP, unless otherwise stated you should consider this message and attachments as "HP CONFIDENTIAL".