Should it immediately restart the builder afterwards?
On Fri, May 6, 2011 at 2:27 PM, Chad Woolley <[email protected]> wrote: > On Thu, May 5, 2011 at 12:39 AM, Brian Guthrie > <[email protected]> wrote: >> I looked at #1 but didn't get a chance to dive into it. I need to >> check that the daemon code still functions after the upgrade. If it >> does, is it just a matter of appropriating that code? Should this be >> manifested as a new button, or a new state of the existing button? > > Yeah, basically just walk the process tree of the builder. A "kill > build" button is what I was thinking. Good for testing, restarting > builds, runaway builds, etc. > _______________________________________________ > Cruisecontrolrb-developers mailing list > [email protected] > http://rubyforge.org/mailman/listinfo/cruisecontrolrb-developers > _______________________________________________ Cruisecontrolrb-developers mailing list [email protected] http://rubyforge.org/mailman/listinfo/cruisecontrolrb-developers
