[Buildbot-devel] How ­­­to synchronise parallel­­b­uilds for correct ma

[Erik]

Hi Vasily,

<vasslitvinov at ...> writes:
> <vasslitvinov <at> ...> writes:
> > 
> > 
> > I still don't understand the problem then... if your builds are all doing
> > one changeset (e.g. if they're all spawned by one change detected by
> > changesource) than this parameter I wrote about is exactly what you
> > need - MailNotifier will wait till all builders that are within a
> > buildset are complete and only then it will send combined notification
> > for all of them.
> > 
> with your explanations this parameter seems to fit.
> I wasn't aware of this functionality, because the
> documentation is very vague on this parameter.
> I'll give it a try.

Please ignore my prev. post, I rewrite it (the correct terms are difficult
to me).


Unfortunately it doesn't work and it seems that my problem is quite
different then this parameter works.

Let me explain it a bit more precise:

We build every new checked in SVN revision, so lets assume someone have
checked in new revision 100. This will issue builders 1-10 to build
different targets.
Lets assume further builder 9 (building target 9 for SVN rev. 100) was
connected to a slow buildslave. Directly after this new revision 101 was
checked in.
Now new builds on builder 1-10 will be scheduled. Lets assume the builder 9
will be connected to a very fast buildslave now and prev build on slow slave
is still compiling revision 100.
This very fast buildslave has finished building of rev. 101 before slow
buildslave has finished rev. 100.
Now you have the problem I described even with the parameter you suggested.

I think it could only be solved if decision about mail notification after
fast buildslave (rev. 101) would be postponed until slow buildslave (rev.
100) is finished (or a timeout occurred).

Do you have an idea how to reach this functionality?


Thank you,

Erik