[Buildbot-devel] build stops

Alexander Lorenz lorenz at testingtech.de
Fri Mar 17 11:06:58 UTC 2006


Brian Warner wrote:
>> is it possible with buildbot to manually interrupt a build as to a) stop 
>> it completely or b) just pause it to continue later ?
>>     
>
> Only the former. There is a "Stop This Build" button on the per-Build web
> page, as well as an IRC command to interrupt the build. Both options stop the
> build completely.
>
>   
>> if at all, then probably only buildstep-wise and not inside a current 
>> buildstep, so that the running step when the interrupt was sent would 
>> have to be repeated, am i right?
>>     
>
> Once upon a time, there was the hope that BuildSteps cold be interrupted and
> then resumed or re-run as necessary (a simple "make" could be run a second
> time, but if the build were stopped in the middle of, say, a CVS checkout,
> then you'd probably have to re-do the whole build, since the tree might have
> been left in some weird state). The main use case for this was for when
> buildslaves lose contact with the buildmaster for a little while, but not
> forever.. the hope was that transient network problems shouldn't kill off a
> build that takes an hour to re-run.
>
> However, the code for this was never completed, so I kind of gave up on the
> idea. There are still some lingering remnants of this idea in the codebase
> (in particular the way that status messages are sent from the slave to the
> master: each with a number, and queued until the master acknowledges receipt.
> But in general we don't have a clean way to resume builds that have been
> interrupted.
>
> If the build contains a number of relatively short steps, then it might be
> feasible to pause one by waiting until the current step has finished, then
> just not running the next step until later. Does this seem useful?
>
>  -Brian
>
>   
if i get it right that you mean an "in between steps" pause, then yes! 
though not as neat as an "anywhere pause/resume", it would still be very 
useful and should be much less complicated - and also much less risky. ;)

there could be two ways of doing this:
- either the one you proposed -> on "pause" finish step and wait, on 
"resume" continue with next step
- or -> on "pause" wait at once, and on "resume" restart the step you 
were paused in. (and continue through the build) this one seems nicer at 
first ("pause" has immediate effect), but some kind of cleanup for this 
step might be necessary, before it could be restarted ...

but in general: _any_ kind of pause mechanism would be nice. :)


by the way, how is the status on salvaging/reusing parts of  interrupted 
builds at build restart, like it was mentioned at the end of the 
buildbot paper under "future directions"?




regards

lx


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://buildbot.net/pipermail/devel/attachments/20060317/34c03168/attachment.html>


More information about the devel mailing list