[Buildbot-devel] Automated release builds

[Andy Howell]

On 09/10/2010 03:11 AM, Marcus Lindblom wrote:
> On 2010-09-10 03:23, Dustin J. Mitchell wrote:
>> On Thu, Sep 9, 2010 at 7:04 PM, Andy Howell<AndyHowell at austin.rr.com>  wrote:
>>> I noticed the new "change hooks" in the docs:
>>>   http://buildbot.net/buildbot/docs/latest/Change-Hooks.html#Change-Hooks
>>>
>>> It looks like I could just do a POST with the repository and branch ( CVS tag ) that I want.
>>
>> The "try" functionality might be better suited to this particular
>> purpose, as it does not inject a new Change object.  But the Change
>> Hooks are new and it would be interesting to see if they're
>> better-suited to the purpose!
> 
> How about just forcing a build on the release-builder via the 
> web-interface (a scripted POST if you'd like it automated) ?
> 
> I'm thinking about something similar for us here, as I could have steps 
> that upload the files somewhere, extract changelog vs. the last release, 
> etc etc etc.
> 
Marcus,

	Do you mean posting to /builders/<BUILDER>/force for each builder? I hadn't thought of that.

I've got a proof-of-concept test working by posting to /change_hook/base, using the
current tip of git. There is bug in master/buildbot/status/web/hooks/base.py

-def getChanges(self, request):
+def getChanges(request, options = None):


I think ether post method would work. With some tweaks to hooks/base.py, /change_hook/base
could have the advantage that any number of properties can be passed in. Another advantage
of this is that all builders across the platforms I build for will fire automatically.

The /builders/<BUILDER>/force on the other hand is limited to 3 properties, and each
builder would have to specified.

Once the build is done, I'd need to copy it to another host and generate some html. I'm
not sure if I'll do that in a step, have a status notifier that kicks off the copy and/or
the html generation, or have a master step. To generate the HTML I need to have a record
of previous releases.

Regards,

	Andy