[Buildbot-devel] Buildbot configuration for multiple builders

[Bailey, Darragh]

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".
________________________________________
From: buildbot-devel-bounces at lists.sourceforge.net [mailto:buildbot-devel-bounces at lists.sourceforge.net] On Behalf Of Byrne, David
Sent: 17 July 2007 15:44
To: buildbot-devel at lists.sourceforge.net
Subject: Re: [Buildbot-devel] Buildbot configuration for multiple builders

The problem is that I'm not wanting to trigger the build off of the build of the distributables, but off of the checkin of the distributables.  Our development team checks in source that gets automatically built into distributables for QA.  The QA team checks out these distributables and when they think that they are ok for user testing, they check in the distributables.  At that time, I would like the distributables to get automatically checked out to UAT.  I was hoping to use buildbot to do this so that we had one place to see the process flow working.  If I'm not mistaken, with the Dependent scheduler, the checkout of the distributables would happen immediately after they were built.

Thanks,
David Byrne

________________________________________
From: Cavanagh, Sean (Sean) [mailto:scavanagh at avaya.com] 
Sent: Tuesday, July 17, 2007 10:27 AM
To: Byrne, David
Subject: RE: [Buildbot-devel] Buildbot configuration for multiple builders

Have you tried a Dependent scheduler? 

________________________________________
From: buildbot-devel-bounces at lists.sourceforge.net [mailto:buildbot-devel-bounces at lists.sourceforge.net] On Behalf Of Byrne, David
Sent: Monday, July 16, 2007 7:26 PM
To: buildbot-devel at lists.sourceforge.net
Subject: [Buildbot-devel] Buildbot configuration for multiple builders

I've been using buildbot successfully for the last few months now and I'm now having a little difficulty in configuring it to have new responsibilities.  I have an subversion repository that holds both our source code and our distributables (binaries, configuration files, etc).  We use buildbot for only one of our projects currently (though we hope to use it more in the future).  What it currently does now is build our distributables whenever source code is checked in.  What I would like it to do is to also migrate distributables automatically to our test server when the distributables are checked in.  The problem is that I'm not sure how to set it up so that the same repository can trigger different builders to fire.  We have a builder on our development box to build the distributables and a builder on the test box to retrieve the distributables.  I can't find an easy way to set this up.  Am I missing something?  Any help would be appreciated.

Thanks,
David Byrne