tag:blogger.com,1999:blog-2021989930591302225.post5469849197481939609..comments2023-10-18T07:48:44.802-07:00Comments on NYC DBA: Running a Buildbot buildslave as a Windows serviceAnonymoushttp://www.blogger.com/profile/09313712310740744659noreply@blogger.comBlogger3125tag:blogger.com,1999:blog-2021989930591302225.post-16621786421190088272014-03-19T14:52:43.473-07:002014-03-19T14:52:43.473-07:00You can use nssm for running the service.You can use nssm for running the service.Maciek D.https://www.blogger.com/profile/04734811908773155801noreply@blogger.comtag:blogger.com,1999:blog-2021989930591302225.post-68801382744472092002013-08-05T02:04:08.245-07:002013-08-05T02:04:08.245-07:00This "simplified" service can do its job...This "simplified" service can do its job indeed, but when I started to debug it (e.g. it gets stuck on service stop or restart), I realized I am re-implementing the "scary" buildbot_service.py, and when I looked into it, I found out it can actually run buildslave(s) as well. It just needs one step to specify the buildslave directory.<br /><br /><br />python buildbot_service.py install [optionally the logon and autostart details]<br />python buildbot_service.py start path_to_buildslave<br /><br />The path is then persisted and the service always starts running the buildslave. It can be repeated for multiple buildslaves/build masters on the machine.voytahttps://www.blogger.com/profile/18242279057632865426noreply@blogger.comtag:blogger.com,1999:blog-2021989930591302225.post-88192000459356817802010-01-06T16:19:48.476-08:002010-01-06T16:19:48.476-08:00For the record, thanks :)For the record, thanks :)Sarahhttps://www.blogger.com/profile/11661684696824682086noreply@blogger.com