[Buildbot-devel] Cleaning, but not every build

[Henry]

1) Okay, I guess I'll add a clean step that only runs at the right  
time, and then look into the scheduler properties when 7.8 is released.

2) Multiple commits building up during buildbots stable tree wait time  
thing aren't the problem, since that can be set to zero or very low.  
The problem is that commits build up during an actual build and then  
for the next build all of them are built. This is faster than building  
each one individually, but gives a less clear build history, so if I  
try to implement this feature I'll might have one builder that does it  
this way and another that does it the other way.

I'll look into subclassing the scheduler.

Thanks

On Jul 17, 2008, at 7:59 AM, Axel Hecht wrote:
> 2008/7/17 Henry <dimensiondude.oss at gmail.com>:
>> Is there any way to make a builder that builds incrementally every
>> time it detects changes, only rebuilding things that have changed,
>> but also cleans everything and rebuilds regularly (say, daily). I  
>> know
>> how to make a builder that does one and another that does the the
>> other, but that leaves the incremental builder never cleaning.
>> buildbot doesn't seem to like having two builders use the same
>> directory.
>>
>> Also, is there any way to make it so instead of detecting a change,
>> building, and then detecting and building all of the changes since  
>> the
>> first build, it downloads and builds all the changes one by one, so
>> you can tell exactly which one broke it?
>>
>
> With 0.7.8, you'll get scheduler properties, that is, you can create
> two schedulers that are going to set different build properties when
> kicking off the build.
>
> You can then add a clobber step which would SKIP for depend builds,
> based on those set properties.
>
> To build each change, you need to subclass the scheduler, and send out
> subclasses subclassed SourceStamps in the build requests, and I don't
> see us fixing that for 0.7.8, sadly.
> http://hg.mozilla.org/users/axel_mozilla.com/tooling/index.cgi/file/8c1b43d8dfce/mozilla/tools/buildbotcustom/buildbotcustom/l10n.py#l311
> has sample code. http://buildbot.net/trac/ticket/288 is the ticket for
> making this better.
>
> Axel

On Jul 16, 2008, at 7:05 PM, Mark Roddy wrote:

> If I'm understanding correctly, I've had to solve these issues myself.
> Let me know if this is incorrect:
>
> 1) 'Incremental' and 'Full' builds - The only way I've found to
> accomplish this is to have two different builds setup (which you noted
> you could do).  There may be some work around I did not think of, but
> also keep in mind you'll probably want to do a 'full checkout' on your
> full builds rather then an update for which you'd need two different
> build steps.  I've run into issues where someone would delete a file,
> and subversion would delete the file on an update and the generated
> binary file would remain resulting in tests that should have failed
> but did not.
>
> 2) Building Changes One By One - Are you referring to that fact that a
> build triggered by a source code commit could actually have several
> commits in place?  If so you can always drop the wait time to
> something pretty low so that each commit gets its own build, but then
> you might have two problems.  Broken builds that someone fixed in a
> commit shortly there after, and people who have multiple commits to a
> single piece of work that actually leave things broken between them.
> I'd suggest that use rebuild from the web page and specify the
> revision number to be rebuilt until you find the problem.
>
> -Mark
>
>
> On 7/16/08, Henry <dimensiondude.oss at gmail.com> wrote:
>> Is there any way to make a builder that builds incrementally every
>> time it detects changes, only rebuilding things that have changed,
>> but also cleans everything and rebuilds regularly (say, daily). I  
>> know
>> how to make a builder that does one and another that does the the
>> other, but that leaves the incremental builder never cleaning.
>> buildbot doesn't seem to like having two builders use the same
>> directory.
>>
>> Also, is there any way to make it so instead of detecting a change,
>> building, and then detecting and building all of the changes since  
>> the
>> first build, it downloads and builds all the changes one by one, so
>> you can tell exactly which one broke it?
>>
>> -------------------------------------------------------------------------
>> This SF.Net email is sponsored by the Moblin Your Move Developer's  
>> challenge
>> Build the coolest Linux based applications with Moblin SDK & win  
>> great prizes
>> Grand prize is a trip for two to an Open Source event anywhere in  
>> the world
>> http://moblin-contest.org/redirect.php?banner_id=100&url=/
>> _______________________________________________
>> Buildbot-devel mailing list
>> Buildbot-devel at lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/buildbot-devel
>>
>
> -------------------------------------------------------------------------
> This SF.Net email is sponsored by the Moblin Your Move Developer's  
> challenge
> Build the coolest Linux based applications with Moblin SDK & win  
> great prizes
> Grand prize is a trip for two to an Open Source event anywhere in  
> the world
> http://moblin-contest.org/redirect.php?banner_id=100&url=/
> _______________________________________________
> Buildbot-devel mailing list
> Buildbot-devel at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/buildbot-devel