[Buildbot-devel] Q: How do simultaneous change-set builds not collide?
mrmakent at cox.net
Fri May 16 03:18:59 UTC 2008
On Thu, 2008-05-15 at 23:12 -0400, Dustin J. Mitchell wrote:
> On Thu, May 15, 2008 at 11:03 PM, Mike Kent <mrmakent at cox.net> wrote:
> > If I have a build configured to allow multiple simultaneous builds to occur on a
> > build slave, and a build of a change-set is triggered while another change-set
> > build is already running on the same build slave, what keeps the two checkouts
> > of the change-set source code from colliding? I'm a newbie at buildbot, and I
> > don't see anything that would put the two change-set source checkouts into
> > different directories.
> The same *builder* can't run two builds at the same time. Each
> builder has its own subdirectory on each slave, so as long as builds
> stick to their subdirectories, there should be no interference.
OK, so maybe my understanding of what buildbot will do is completely
off. If for one builder, if it is currently running a build of a
change-set, and a second commit triggers another change-set build, are
they serialized (that is, the first build must finish before the second
That would be kinda unfortunate for us, as our builds take about an hour
(LARGE project). I was hoping the two change-set sources would be
checked out into separate directories, and the build run simultaneously.
More information about the devel