Opened 10 years ago

Closed 5 years ago

#1039 closed enhancement (fixed)

Allow trigger -> triggerable to span masters

Reported by: dustin Owned by:
Priority: major Milestone: 0.9.0
Version: Keywords: database, mq
Cc: l10n.moz@…

Description (last modified by dustin)

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.


Change History (8)

comment:1 Changed 10 years ago by catlee

As part of this, we should build a cmdline interface to trigger schedulers via 'buildbot trigger'

comment:2 Changed 10 years ago by Pike

  • Cc l10n.moz@… added

comment:3 Changed 10 years ago by dustin

  • Milestone changed from 0.8.3 to 0.8.+

comment:4 Changed 9 years ago by dustin

  • Keywords mq added
  • Milestone changed from 0.8.+ to 0.9.0

comment:5 Changed 7 years ago by dustin

  • Description modified (diff)

This should use the same communication mechanism as the force schedulers.

comment:6 Changed 6 years ago by dustin

  • Version 0.8.1 deleted

comment:7 Changed 6 years ago by dustin

  • Description modified (diff)

comment:8 Changed 5 years ago by tardyp

  • Resolution set to fixed
  • Status changed from new to closed

For me, this feature should work now.

Trigger step is putting buildrequests to the db, and watching completion via mq.


Note: See TracTickets for help on using tickets.