Cruisecontrolrb users - Mar 2009 - Stopping builders

Hi,

When I call ''cruise stop'' from the command line, this just
sends a
command to mongrel to stop the rails app. Some time later the builders  
also seem to stop, but I''m not sure how this is achieved.

I''d like to get better control over the builders, ideally putting a  
cancel button on the UI so I can send a CTRL-C to the rake task. I''d  
also like the ''cruise stop'' command to wait for each builder
to stop,
and let me know how that is going.

I''m happy to hack on the code to do this but I could do with some  
guidance to get started. Can anyone give me some pointers as to how  
this would be achieved?

Matt Wynne
http://blog.mattwynne.net
http://www.songkick.com

On Wed, Mar 11, 2009 at 3:15 AM, Matt Wynne <matt at mattwynne.net>
wrote:
> Hi,
>
> When I call ''cruise stop'' from the command line, this
just sends a command
> to mongrel to stop the rails app. Some time later the builders also seem to
> stop, but I''m not sure how this is achieved.
>
> I''d like to get better control over the builders, ideally putting
a cancel
> button on the UI so I can send a CTRL-C to the rake task. I''d also
like the
> ''cruise stop'' command to wait for each builder to stop,
and let me know how
> that is going.
>
> I''m happy to hack on the code to do this but I could do with some
guidance
> to get started. Can anyone give me some pointers as to how this would be
> achieved?
This will probably be tricky to do in a cross-platform way, especially
on windows.

I''m planning (hopefully soon) to continue to improve the init script
(under daemon dir) to make sure it kills all builders and
sub-processes when cruise is stopped.  Not sure if this will make it
into ''cruise stop'', that code is kinda weird anyway, and would
have
the same problems to make it works cross-platform.  So, I''ll probably
just do it in the init script, which is currently unix- (maybe
debian-)only anyway, so I don''t have to worry about cross platform.

-- Chad
-- Chad