[Buildbot-devel] How ­­­­to synchronise paralle­l­­b­uilds for correct m

[vasslitvinov at pisem.net]

This is still covered by what I wrote earlier.

What you need is the flag for MailNotifier I mentioned. What is probably missing is that your builders aren't joint in one buildset. Easiest way to do so is to drive all the builds by one SingleBranchScheduler().

Explaining stuff further is really complicated without seeing your configuration...

--

Vasily

Пнд 09 Сен 2013 10:20:50 +0400, Erik  написал:
Hi Vasily,

 writes:

>  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

------------------------------------------------------------------------------

Learn the latest--Visual Studio 2012, SharePoint 2013, SQL 2012, more!

Discover the easy way to master current and previous Microsoft technologies

and advance your career. Get an incredible 1,500+ hours of step-by-step

tutorial videos with LearnDevNow. Subscribe today and save!

http://pubads.g.doubleclick.net/gampad/clk?id=58041391&iu=/4140/ostg.clktrk

_______________________________________________

Buildbot-devel mailing list

Buildbot-devel at lists.sourceforge.net

https://lists.sourceforge.net/lists/listinfo/buildbot-devel

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