#184: New build step for synchronizing concurrent builds: Blocker
------------------------+---------------------------------------------------
Reporter: gward | Owner: gward
Type: enhancement | Status: assigned
Priority: major | Milestone: 0.8.+
Version: 0.7.6 | Keywords: buildcoord
------------------------+---------------------------------------------------
Comment(by chrb):
dustin, your link to buildbot.net/trac/report/34 in the last comment links
to a non-existent report.
I would like to see something like this that supports merging the
buildpath. I was thinking of using triggers as gward suggested - creating
some trigger that requires ''n'' previous buildsteps to have succeeded,
like:
{{{
from buildbot.process.buildstep import SUCCESS
class SyncTrigger(Trigger):
def __init__(self, required):
self.required = required
self.triggers = 0
def start(self):
p = self.build.getProperties()
if 'reset' in p:
self.triggers = 0
if 'done' in p and self.triggers < self.required :
self.triggers += 1
i = self.required - self.triggers
self.step_status.setText(['waiting for '+i+' builds'])
return self.finished(SUCCESS)
else:
return Trigger.start(self)
}}}
You would need to send a trigger with 'reset' keyword from the Build that
initiates the flow-control split, and triggers with 'done' keyword at the
end of each concurrent Build.
--
Ticket URL: <http://buildbot.net/trac/ticket/184#comment:19>
Buildbot <http://buildbot.net/>
Buildbot: build/test automation
------------------------------------------------------------------------------
Sell apps to millions through the Intel(R) Atom(Tm) Developer Program
Be part of this innovative community and reach millions of netbook users
worldwide. Take advantage of special opportunities to increase revenue and
speed time-to-market. Join now, and jumpstart your future.
http://p.sf.net/sfu/intel-atom-d2d
_______________________________________________
Buildbot-commits mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/buildbot-commits
