#68: New mechanism for monitoring buildbot startup
--------------------+-------------------------
Reporter: joduinn | Owner: tom.prince
Type: defect | Status: assigned
Priority: major | Milestone: 0.8.8
Version: 0.7.5 | Resolution:
Keywords: sprint |
--------------------+-------------------------
Comment (by dustin):
The fix here is, I think, for the startup script to set up an IPC channel
with the new process, and then use that to get status information from the
master. That channel could be a PB listener on a random port, listening
only on 127.0.0.1, plus a random username/password. When the master first
starts up, it would connect to this port and authenticate, then send both
Twisted log information and state changes (starting, configuring, running,
failed, etc.) to the script.
This could work on most systems, although it will run afoul of the Windows
firewall if python.exe is not given an exclusion. For that, I think we
could add a '--no-wait' option that simply starts the master and skips the
rest.
--
Ticket URL: <http://trac.buildbot.net/ticket/68#comment:15>
Buildbot <http://buildbot.net/>
Buildbot: build/test automation
------------------------------------------------------------------------------
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_d2d_feb
_______________________________________________
Buildbot-commits mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/buildbot-commits
