Hello,
I'm trying to set up a buildbot instance using the wonderful
`buildbot_travis` extension. I have been able to test my setup using
`bbtravis run --docker-image=...` to make sure the basic setup is sane,
then I configured a buildbot master with one LocalWorker and one
DockerLatentWorker to schedule actual builds.
Doing a forcebuild I notice that the spawner works as expected, but the
running then can't be reached. Thus, build steps are dynamically created
from my repo's yml file, but can't be started.
Looking at the logs I see from twistd.log that the master receives
timeouts trying to reach the worker, and from the docker daemon logs (as
well as `docker ps -a` I see that the container was started, but exited
immediately).
Any idea what I may be doing wrong, or how I can debug this ?
Thanks,
Stefan
--
...ich hab' noch einen Koffer in Berlin...
_______________________________________________
users mailing list
users@buildbot.net
https://lists.buildbot.net/mailman/listinfo/users