[Buildbot-devel] How to set revision number for nightly builds

[Chris AtLee]

At Mozilla we use custom schedulers to do this.

The SpecifcNightly scheduler
(http://hg.mozilla.org/build/buildbotcustom/file/7fcf28632599/scheduler.py#l53)
allows us to specify a function that is run when the schedulers fires
to generate a SourceStamp to use for the nightly build(s). An example
of a function we use is lastGoodFunc
(http://hg.mozilla.org/build/buildbotcustom/file/7fcf28632599/misc_scheduler.py#l252)
which finds the last "good" revision on a set of builders to use for
the nightly build.

I hope you find something in there useful!

Cheers,
Chris

On Wed, May 25, 2011 at 4:11 PM, Tony Lazarew <anarky13 at gmail.com> wrote:
> Hi,
>
> I'll step in on behalf of Pavel with some details.
>
> Bob, thank you for suggestion -- we use this approach currently.
> Except for we don't perform any manipulations on source base (like
> revert). But it still leads to a problem which I'll try to describe.
>
> We have several platforms we build on and we want them all to use the
> same revision for the nightly build. Generally it works just nice
> because nightly build fires up at 12am and most of developers are
> asleep. But we ran into the following situation:
> 1) a new revision r1 is committed just 5 mins before the midnight
> 2) one builder b1 is not able to finish its post-commit build before
> midnight while others (b2, b3) finish time
> 3) nightly starts with a revision r1
> 4) new revision r2 arrives somewhere in time after the nightly took
> off but before b1 finished building r1
> 5) b1 finishes r1 and starts nightly build but already with r2
>
> So we get nightlies for both r1 and r2 on different builders which is
> not what we want.
>
> One kind of a solution as I see it is to use different builders for
> nightly and post-commit builds. The most straightforward one but I
> don't think we need that many builders doing mostly the same thing.
>
> Another solution would be to make a customized Nightly scheduler which
> will take the latest known revision from the pool of changes and put
> it into queue for all builders whether they are ready to build or not.
>
> Or maybe we're missing something and there's already a way to do this
> using built-in schedulers. Any suggestions are appreciated.
>
> Thanks,
> Tony
>
> 2011/5/25 Mark Richardson (Internal) <mark.richardson at nag.co.uk>:
>> Hi Bob,
>> please accept my apologies. I am sure many of us are working through
>> similar situations.
>> Best wishes,
>> Mark
>>
>> On 25/05/2011 16:01, Bob Hood wrote:
>>> On 5/25/2011 8:26 AM, Mark Richardson (Internal) wrote:
>>>> Hi all,
>>>> Just adding an observation.
>>>> I think Bob's solution is okay to the point where he reverts the
>>>> source. A copy of the source should be archived for reference at
>>>> least. (I do that before I start the compilation)
>>>
>>> I have post-build steps that do several things before I revert the
>>> changes, such as construct and protect regression archives of each build
>>> (with the revision modifications in place), package with an installer
>>> and publish for testers. Reverting is the *very* last thing I do. :)
>>>
>>> Render me gone,                       |||
>>> Bob                                 ^(===)^
>>> ---------------------------------oOO--(_)--OOo---------------------------------
>>>   We can't all be architects. Some of us excel at building from the blueprints.
>>>
>>>
>>> ________________________________________________________________________
>>> This e-mail has been scanned for all viruses by Star.
>>> ________________________________________________________________________
>>>
>>>
>>>
>>> ------------------------------------------------------------------------------
>>> vRanger cuts backup time in half-while increasing security.
>>> With the market-leading solution for virtual backup and recovery,
>>> you get blazing-fast, flexible, and affordable data protection.
>>> Download your free trial now.
>>> http://p.sf.net/sfu/quest-d2dcopy1
>>>
>>>
>>>
>>> _______________________________________________
>>> Buildbot-devel mailing list
>>> Buildbot-devel at lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/buildbot-devel
>>
>> ________________________________________________________________________
>> The Numerical Algorithms Group Ltd is a company registered in England
>> and Wales with company number 1249803. The registered office is:
>> Wilkinson House, Jordan Hill Road, Oxford OX2 8DR, United Kingdom.
>>
>> This e-mail has been scanned for all viruses by Star. The service is
>> powered by MessageLabs.
>> ________________________________________________________________________
>>
>> ------------------------------------------------------------------------------
>> vRanger cuts backup time in half-while increasing security.
>> With the market-leading solution for virtual backup and recovery,
>> you get blazing-fast, flexible, and affordable data protection.
>> Download your free trial now.
>> http://p.sf.net/sfu/quest-d2dcopy1
>> _______________________________________________
>> Buildbot-devel mailing list
>> Buildbot-devel at lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/buildbot-devel
>>
>
>
>
> --
> Tony
>
> ------------------------------------------------------------------------------
> vRanger cuts backup time in half-while increasing security.
> With the market-leading solution for virtual backup and recovery,
> you get blazing-fast, flexible, and affordable data protection.
> Download your free trial now.
> http://p.sf.net/sfu/quest-d2dcopy1
> _______________________________________________
> Buildbot-devel mailing list
> Buildbot-devel at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/buildbot-devel
>