tardyp changed the topic of #buildbot to: A Software Freedom Conservancy Project | Buildbot-3.2.0 | docs: http://docs.buildbot.net/current/ | tutorial: http://docs.buildbot.net/current/tutorial | irclogs: https://libera.irclog.whitequark.org/buildbot
Zorry has quit [Quit: No Ping reply in 180 seconds.]
Zorry has joined #buildbot
Zorry has quit [Changing host]
Zorry has joined #buildbot
bdbaddog1 has joined #buildbot
bdbaddog has quit [Ping timeout: 272 seconds]
bdbaddog1 has quit [Quit: Leaving.]
Cheyenne has quit [Ping timeout: 252 seconds]
Cheyenne has joined #buildbot
antranigv has quit [Ping timeout: 250 seconds]
antranigv has joined #buildbot
rakan has joined #buildbot
<rakan> Hello everyone
<rakan> I've setup buildbot for a new github repo that i am testing. The setup has a github webhook & the rest of the components.
<rakan> When i push to my PR, i can see: Received 1 changes from GitHub PR #1 and then injected change 24... but i don't see how that the worker node started running the steps. I am using the docker-containers provided in your repo & a modified master.cfg
<glogan> rakan have you defined schedulers and builders?
<glogan> And workers. Those are still required with the docker containera
<glogan> eg: we do everything in docker. Our master is a persistent docker container, our workers are latent workers
<glogan> workers are defined on :87, builders and schedulers are inside of the loop at 154
<rakan> Yes... i do have all those components defined as in the example configurations
<rakan> Though after i see that the webhook has been received by the master... nothing else gets printed through the logs.
<glogan> workers are not paused?
<sknebel> does the build run if you force it manually from the buildbot ui?
<rakan> sknebel: Yes
<rakan> Workers are definitely not paused
<rakan> Here are my configs: https://pastebin.com/xY4gPDNe
<rakan> glogan
bdbaddog has joined #buildbot
rakan has quit [Quit: Client closed]
antranigv has quit [Ping timeout: 256 seconds]
antranigv has joined #buildbot