#1039: Allow trigger -> triggerable to span masters
-------------------------+--------------------
Reporter: dustin | Owner:
Type: enhancement | Status: new
Priority: major | Milestone: 0.9.0
Version: 0.8.1 | Resolution:
Keywords: database, mq |
-------------------------+--------------------
Old description:
> Right now, a Trigger step must run on the same master as the Triggerable
> scheduler it talks to.
>
> That should move into the database so that the two can be isolated and
> Trigger can queue a message to the Triggerable.
New description:
Right now, a Trigger step must run on the same master as the Triggerable
scheduler it talks to.
That should move into the database so that the two can be isolated and
Trigger can queue a message to the Triggerable.
--
Comment (by dustin):
This should use the same communication mechanism as the force schedulers.
--
Ticket URL: <http://trac.buildbot.net/ticket/1039#comment:5>
Buildbot <http://buildbot.net/>
Buildbot: build/test automation
------------------------------------------------------------------------------
CenturyLink Cloud: The Leader in Enterprise Cloud Services.
Learn Why More Businesses Are Choosing CenturyLink Cloud For
Critical Workloads, Development Environments & Everything In Between.
Get a Quote or Start a Free Trial Today.
http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk
_______________________________________________
Buildbot-commits mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/buildbot-commits
