verm__ changed the topic of #buildbot to: A Software Freedom Conservancy Project | Buildbot-3.5.0 | docs: http://docs.buildbot.net/current/ | tutorial: http://docs.buildbot.net/current/tutorial | irclogs: https://libera.irclog.whitequark.org/buildbot
guinevere has quit [Remote host closed the connection]
guinevere has joined #buildbot
jmd has joined #buildbot
jmd has quit [Remote host closed the connection]
Guest7178 is now known as mjw
manx has quit []
manx has joined #buildbot
manx has quit [Client Quit]
manx has joined #buildbot
jmd has joined #buildbot
mjw is now known as Guest5202
Guest5202 has quit [Killed (zinc.libera.chat (Nickname regained by services))]
Guest5202 has joined #buildbot
Luj has quit [Quit: Ping timeout (120 seconds)]
Luj has joined #buildbot
jmd has quit [Remote host closed the connection]
guinevere has quit [Remote host closed the connection]
guinevere has joined #buildbot
guest_83 has joined #buildbot
<guest_83> Hey! I am trying to map the dependency graph of some tool to builds in buildbot. If 'b' depends on 'a' according to the graph, the build for 'b' should wait for the one for 'a' to succeed/skip. It looks like Dependent Scheduler is the right component to use, but builds are currently implemented via Triggerable Scheduler. Is there a way to model
<guest_83> dependencies with a Triggerable Scheduler? Or is that a bad idea?
guest_83 has quit [Quit: Client closed]