tardyp changed the topic of #buildbot to: A Software Freedom Conservancy Project | Buildbot-2.10.0 | docs: http://docs.buildbot.net/current/ | tutorial: http://docs.buildbot.net/current/tutorial | logs: https://freenode.irclog.whitequark.org/buildbot
jcarl43 has quit [Quit: WeeChat 3.0]
kkleine has quit [Ping timeout: 260 seconds]
tflink_ is now known as tflink
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?
<felixfontein> buildbot-slave is dead. use https://pypi.org/project/buildbot-worker/ instead.
<medfly> thanks!
<felixfontein> I don't know who has access to the buildbot-slave PyPi project, but someone should mark it as deprecated / replaced
<cmouse> tardyp might know
<medfly> wow, hi cmouse!
<cmouse> hi
<cmouse> =)
<medfly> we used to chat in the same channel on quakenet!
<cmouse> yes
<tardyp> the problem is that changing that means uploading a new package version
kkleine has joined #buildbot
<tardyp> hopefully won't brake anybody's setup
<medfly> thanks
<cmouse> tardyp: people can affix the version if they insist on running ages old version
<tardyp> its just that I hope this version is functional. I just extracted the tarbal, and changed the description and re compressed it
<tardyp> running setup.py sdist do not work anymore :/
<cmouse> good point, on the other hand, it has been there for a while, so if that's the only change i'm sure people are prepared.
mbrndtgn has quit [Quit: The Lounge - https://thelounge.chat]
mbrndtgn has joined #buildbot
tuxillo has quit [Ping timeout: 256 seconds]
medfly has quit [Ping timeout: 265 seconds]
kkleine has quit [Ping timeout: 244 seconds]
kkleine has joined #buildbot
jcarl43 has joined #buildbot
jtux has quit [Quit: Leaving.]
kraiskil has joined #buildbot
kraiskil has quit [Ping timeout: 240 seconds]
kkleine has quit [Ping timeout: 260 seconds]
mscastanho has joined #buildbot
<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!
kraiskil has joined #buildbot
mscastanho has quit [Ping timeout: 265 seconds]
kkleine has joined #buildbot
kraiskil has quit [Ping timeout: 246 seconds]