tuxillo has quit [Read error: Connection reset by peer]
yokel has quit [Ping timeout: 256 seconds]
yokel has joined #buildbot
jtux has joined #buildbot
jtux has quit [Remote host closed the connection]
jtux has joined #buildbot
tuxillo has joined #buildbot
deepy has quit [*.net *.split]
deepy has joined #buildbot
alicef_ has quit [Ping timeout: 246 seconds]
alicef_ has joined #buildbot
medfly has joined #buildbot
<medfly>
Hi, I'm tinkering with some examples and kinda surprised at the state of buildbot-slave - I seem to be doing python3 support patches. am I looking at the wrong thing?
<mscastanho>
Hi, I'm trying to create a setup where I have a single builder (with a Trigger step) trigger several other Triggerable schedulers depending on the files changed in the last set of incoming changes (that triggered the first build). Right now I'm using a subclass of Trigger to override getSchedulersAndProperties, but I suspect I don't have access to the set of changed files inside the Trigger step,
<mscastanho>
which I would need to check to decide which schedulers to trigger. Is my suspicion correct? Do you see another way to accomplish this?
<cmouse>
the actual change should be available.
<cmouse>
i think it'll be under source stamp maybe?
tuxillo has joined #buildbot
<mscastanho>
cmouse: you're right. I think I was trying to access it the wrong way. Thanks!