Hi, Could you add systemd support to buildbot-slave-0.8.8 so it can go stable along with buildbot-0.8.8 (bug #487736) ? Thanks
What is the proper way to start buildbot-slave? I thought it was simply: # /usr/bin/buildslave start error reading '/usr/portage/app-emulation/virtualbox-modules/buildbot.tac': No such file or directory invalid buildslave directory '/usr/portage/app-emulation/virtualbox-modules' But it fails as you can see :S
See here http://docs.buildbot.net/current/tutorial/firstrun.html#creating-a-slave so assuming your /home/pacho/workdir/slavedir is your slave box working directory you should 'cd /home/pacho/workdir' and then 'buildslave start slavedir' Also look at the current init script.
Yeah, I was wondering about why init.d script doesn't use that and, instead, runs: --exec /usr/bin/python -- /usr/bin/twistd :/
(In reply to Pacho Ramos from comment #3) > Yeah, I was wondering about why init.d script doesn't use that and, instead, > runs: > --exec /usr/bin/python -- /usr/bin/twistd > > :/ I don't know to be honest, but the buildbot master is also doing this and you also added a systemd file there http://sources.gentoo.org/cgi-bin/viewvc.cgi/gentoo-x86/dev-util/buildbot/files/buildmaster.initd?revision=1.4&view=markup http://sources.gentoo.org/cgi-bin/viewvc.cgi/gentoo-x86/dev-util/buildbot/files/buildbot.service?revision=1.1&view=markup
Ah, I guess it's because for buildbot I was able to pass the directory at the end of the command... will try for this one too then ;)
+*buildbot-slave-0.8.8-r1 (22 Dec 2013) + + 22 Dec 2013; Pacho Ramos <pacho@gentoo.org> +buildbot-slave-0.8.8-r1.ebuild, + +files/buildslave.service: + Add unit file (#491038) +