From matt at mattwynne.net  Wed Apr  1 13:24:44 2009
From: matt at mattwynne.net (Matt Wynne)
Date: Wed, 1 Apr 2009 18:24:44 +0100
Subject: [Cruisecontrolrb-users] Cancelling a build
Message-ID: <0562C1EF-159B-439F-B448-7A7C911B8ADC@mattwynne.net>

What do other people do to cancel a build?

Right now I kill -9 the builder but it seems pretty brutal. Is there a  
nicer way?

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


From thewoolleyman at gmail.com  Wed Apr  1 15:04:13 2009
From: thewoolleyman at gmail.com (Chad Woolley)
Date: Wed, 1 Apr 2009 12:04:13 -0700
Subject: [Cruisecontrolrb-users] Cancelling a build
In-Reply-To: <0562C1EF-159B-439F-B448-7A7C911B8ADC@mattwynne.net>
References: <0562C1EF-159B-439F-B448-7A7C911B8ADC@mattwynne.net>
Message-ID: <e3af97510904011204l3d78c0ffub19b62ad7e73b24a@mail.gmail.com>

On Wed, Apr 1, 2009 at 10:24 AM, Matt Wynne <matt at mattwynne.net> wrote:
> What do other people do to cancel a build?
>
> Right now I kill -9 the builder but it seems pretty brutal. Is there a nicer
> way?

Not that I know of.  Plus, that still isn't good enough if there are
subprocesses - they can be orphaned,.

I just checked in some changes to the daemon/daemon_helper.rb init
script which does have logic to kill all child processes.  It would be
great to integrate this into the app, but I didn't have the energy to
tackle that in a cross-platform way.

From chris at seagul.co.uk  Thu Apr  2 04:39:31 2009
From: chris at seagul.co.uk (Chris Roos)
Date: Thu, 2 Apr 2009 09:39:31 +0100
Subject: [Cruisecontrolrb-users] Running cc.rb under Passenger (mod_rails)
	and the builders as Launch Agents
Message-ID: <b85742420904020139s7ffb04d9j7756e0122f8cd5d@mail.gmail.com>

Morning,

I spent quite some time getting cruisecontrol.rb running on a Mac
under Passenger (mod_rails) and the builders running as Launch Agents.
 I've documented it on my blog[1].  I'd appreciate knowing what people
think about this approach and any alternative approaches people might
be using to run cruise automatically and in the background.

Cheers,

Chris

[1] http://chrisroos.co.uk/blog/2009-03-31-cruisecontrolrb-with-passenger-and-launchd-on-a-mac

-- 
http://chrisroos.co.uk

From thewoolleyman at gmail.com  Thu Apr  2 05:15:37 2009
From: thewoolleyman at gmail.com (Chad Woolley)
Date: Thu, 2 Apr 2009 02:15:37 -0700
Subject: [Cruisecontrolrb-users] Running cc.rb under Passenger
	(mod_rails) and the builders as Launch Agents
In-Reply-To: <b85742420904020139s7ffb04d9j7756e0122f8cd5d@mail.gmail.com>
References: <b85742420904020139s7ffb04d9j7756e0122f8cd5d@mail.gmail.com>
Message-ID: <e3af97510904020215p82d94ddhc496e4c1cfc33dec@mail.gmail.com>

On Thu, Apr 2, 2009 at 1:39 AM, Chris Roos <chris at seagul.co.uk> wrote:
> ?I've documented it on my blog[1]. ?I'd appreciate knowing what people
> think about this approach and any alternative approaches people might
> be using to run cruise automatically and in the background.

Interesting, but seems painful.  The passenger support could be useful, though.

I just checked in changes to ccrb master which allow the init scripts
under daemon to run on OSX.  You should be able to hook this to
launchd, or just set it as a startup item for the current user's
profile.

From chris at seagul.co.uk  Thu Apr  2 05:39:39 2009
From: chris at seagul.co.uk (Chris Roos)
Date: Thu, 2 Apr 2009 10:39:39 +0100
Subject: [Cruisecontrolrb-users] Running cc.rb under Passenger
	(mod_rails) and the builders as Launch Agents
In-Reply-To: <e3af97510904020215p82d94ddhc496e4c1cfc33dec@mail.gmail.com>
References: <b85742420904020139s7ffb04d9j7756e0122f8cd5d@mail.gmail.com>
	<e3af97510904020215p82d94ddhc496e4c1cfc33dec@mail.gmail.com>
Message-ID: <b85742420904020239sc062075k51cd6b0f7933c329@mail.gmail.com>

On Thu, Apr 2, 2009 at 10:15 AM, Chad Woolley <thewoolleyman at gmail.com> wrote:
> On Thu, Apr 2, 2009 at 1:39 AM, Chris Roos <chris at seagul.co.uk> wrote:
>> ?I've documented it on my blog[1]. ?I'd appreciate knowing what people
>> think about this approach and any alternative approaches people might
>> be using to run cruise automatically and in the background.
>
> Interesting, but seems painful. ?The passenger support could be useful, though.
>
> I just checked in changes to ccrb master which allow the init scripts
> under daemon to run on OSX. ?You should be able to hook this to
> launchd, or just set it as a startup item for the current user's
> profile.

Yeah, I saw your commit that mentioned that it could now be daemonised
on Mac OS X.  I might try that although I suspect I'll have the same
public-key-authentication problem that results in me having to run the
launch agents as a logged in user at the moment.  On that note, does
anyone know how to get around that particular problem (daemon's
running as root but git access being public key only and the public
key belongs to a non-root user)?

Cheers,

Chris

From thewoolleyman at gmail.com  Thu Apr  2 12:28:30 2009
From: thewoolleyman at gmail.com (Chad Woolley)
Date: Thu, 2 Apr 2009 09:28:30 -0700
Subject: [Cruisecontrolrb-users] Running cc.rb under Passenger
	(mod_rails) and the builders as Launch Agents
In-Reply-To: <b85742420904020239sc062075k51cd6b0f7933c329@mail.gmail.com>
References: <b85742420904020139s7ffb04d9j7756e0122f8cd5d@mail.gmail.com> 
	<e3af97510904020215p82d94ddhc496e4c1cfc33dec@mail.gmail.com> 
	<b85742420904020239sc062075k51cd6b0f7933c329@mail.gmail.com>
Message-ID: <e3af97510904020928r7da90922h501124c5ae79cdba@mail.gmail.com>

On Thu, Apr 2, 2009 at 2:39 AM, Chris Roos <chris at seagul.co.uk> wrote:
> launch agents as a logged in user at the moment. ?On that note, does
> anyone know how to get around that particular problem (daemon's
> running as root but git access being public key only and the public
> key belongs to a non-root user)?

If you run it as a startup program in the current user, that should
solve it, no?

The daemon has logic to run as a different user as well, but I've only
tried that on Linux.  It works fine there, though, when the script is
run on system init.

From matt at mattwynne.net  Thu Apr  2 15:45:42 2009
From: matt at mattwynne.net (Matt Wynne)
Date: Thu, 2 Apr 2009 20:45:42 +0100
Subject: [Cruisecontrolrb-users] Cancelling a build
In-Reply-To: <e3af97510904011204l3d78c0ffub19b62ad7e73b24a@mail.gmail.com>
References: <0562C1EF-159B-439F-B448-7A7C911B8ADC@mattwynne.net>
	<e3af97510904011204l3d78c0ffub19b62ad7e73b24a@mail.gmail.com>
Message-ID: <04C197D2-78DF-4F52-B812-65742276B748@mattwynne.net>


On 1 Apr 2009, at 20:04, Chad Woolley wrote:

> On Wed, Apr 1, 2009 at 10:24 AM, Matt Wynne <matt at mattwynne.net>  
> wrote:
>> What do other people do to cancel a build?
>>
>> Right now I kill -9 the builder but it seems pretty brutal. Is  
>> there a nicer
>> way?
>
> Not that I know of.  Plus, that still isn't good enough if there are
> subprocesses - they can be orphaned,.
>
> I just checked in some changes to the daemon/daemon_helper.rb init
> script which does have logic to kill all child processes.

So would that mean if I did sudo /etc/init.d/cruise stop it would  
cancel the build immediately rather than waiting for the builders to  
finish?

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




From thewoolleyman at gmail.com  Thu Apr  2 17:30:08 2009
From: thewoolleyman at gmail.com (Chad Woolley)
Date: Thu, 2 Apr 2009 14:30:08 -0700
Subject: [Cruisecontrolrb-users] Cancelling a build
In-Reply-To: <04C197D2-78DF-4F52-B812-65742276B748@mattwynne.net>
References: <0562C1EF-159B-439F-B448-7A7C911B8ADC@mattwynne.net> 
	<e3af97510904011204l3d78c0ffub19b62ad7e73b24a@mail.gmail.com> 
	<04C197D2-78DF-4F52-B812-65742276B748@mattwynne.net>
Message-ID: <e3af97510904021430g59a6149ag8ea14e8f4a9ee625@mail.gmail.com>

On Thu, Apr 2, 2009 at 12:45 PM, Matt Wynne <matt at mattwynne.net> wrote:
> So would that mean if I did sudo /etc/init.d/cruise stop it would cancel the
> build immediately rather than waiting for the builders to finish?

Yes.  That is the desired behavior, in my opinion (when I want to
restart, I want to restart NOW).  You can start the build again after
you restart.

-- Chad

From matt at mattwynne.net  Thu Apr  2 17:59:09 2009
From: matt at mattwynne.net (Matt Wynne)
Date: Thu, 2 Apr 2009 22:59:09 +0100
Subject: [Cruisecontrolrb-users] Cancelling a build
In-Reply-To: <e3af97510904021430g59a6149ag8ea14e8f4a9ee625@mail.gmail.com>
References: <0562C1EF-159B-439F-B448-7A7C911B8ADC@mattwynne.net>
	<e3af97510904011204l3d78c0ffub19b62ad7e73b24a@mail.gmail.com>
	<04C197D2-78DF-4F52-B812-65742276B748@mattwynne.net>
	<e3af97510904021430g59a6149ag8ea14e8f4a9ee625@mail.gmail.com>
Message-ID: <9FF4419A-4524-4D30-99DB-2CFA95248C13@mattwynne.net>


On 2 Apr 2009, at 22:30, Chad Woolley wrote:

> On Thu, Apr 2, 2009 at 12:45 PM, Matt Wynne <matt at mattwynne.net>  
> wrote:
>> So would that mean if I did sudo /etc/init.d/cruise stop it would  
>> cancel the
>> build immediately rather than waiting for the builders to finish?
>
> Yes.  That is the desired behavior, in my opinion (when I want to
> restart, I want to restart NOW).  You can start the build again after
> you restart.

Great, I'll take a look at that, it should be a real boon for us. Are  
you saying it won't kill processes that are spawned by the build though?

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




From thewoolleyman at gmail.com  Thu Apr  2 21:23:30 2009
From: thewoolleyman at gmail.com (Chad Woolley)
Date: Thu, 2 Apr 2009 18:23:30 -0700
Subject: [Cruisecontrolrb-users] Cancelling a build
In-Reply-To: <9FF4419A-4524-4D30-99DB-2CFA95248C13@mattwynne.net>
References: <0562C1EF-159B-439F-B448-7A7C911B8ADC@mattwynne.net> 
	<e3af97510904011204l3d78c0ffub19b62ad7e73b24a@mail.gmail.com> 
	<04C197D2-78DF-4F52-B812-65742276B748@mattwynne.net>
	<e3af97510904021430g59a6149ag8ea14e8f4a9ee625@mail.gmail.com> 
	<9FF4419A-4524-4D30-99DB-2CFA95248C13@mattwynne.net>
Message-ID: <e3af97510904021823g4f3b594cx73a2e9e9977f0363@mail.gmail.com>

On Thu, Apr 2, 2009 at 2:59 PM, Matt Wynne <matt at mattwynne.net> wrote:
> Great, I'll take a look at that, it should be a real boon for us. Are you
> saying it won't kill processes that are spawned by the build though?

It WILL kill all child processes of the builders.  That's the point,
otherwise you have orphaned processes that block subsequent builds
(e.g. selenium server, jsunit server, test app server instances, any
other processes that the build starts).

Why would you want to keep child processes and builders alive when you
restart ccrb?

From matt at mattwynne.net  Fri Apr  3 04:33:03 2009
From: matt at mattwynne.net (Matt Wynne)
Date: Fri, 3 Apr 2009 09:33:03 +0100
Subject: [Cruisecontrolrb-users] Cancelling a build
In-Reply-To: <e3af97510904021823g4f3b594cx73a2e9e9977f0363@mail.gmail.com>
References: <0562C1EF-159B-439F-B448-7A7C911B8ADC@mattwynne.net>
	<e3af97510904011204l3d78c0ffub19b62ad7e73b24a@mail.gmail.com>
	<04C197D2-78DF-4F52-B812-65742276B748@mattwynne.net>
	<e3af97510904021430g59a6149ag8ea14e8f4a9ee625@mail.gmail.com>
	<9FF4419A-4524-4D30-99DB-2CFA95248C13@mattwynne.net>
	<e3af97510904021823g4f3b594cx73a2e9e9977f0363@mail.gmail.com>
Message-ID: <22EA4B50-29B3-4234-A71A-6A87AFE9E3C9@mattwynne.net>


On 3 Apr 2009, at 02:23, Chad Woolley wrote:

> On Thu, Apr 2, 2009 at 2:59 PM, Matt Wynne <matt at mattwynne.net> wrote:
>> Great, I'll take a look at that, it should be a real boon for us.  
>> Are you
>> saying it won't kill processes that are spawned by the build though?
>
> It WILL kill all child processes of the builders.  That's the point,
> otherwise you have orphaned processes that block subsequent builds
> (e.g. selenium server, jsunit server, test app server instances, any
> other processes that the build starts).
>
> Why would you want to keep child processes and builders alive when you
> restart ccrb?

On the contrary, I want them to die, but I just wasn't sure whether  
they would, from something you'd said earlier in the thread.

That's great, I'll check it out. Thanks Chad.

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


From felipero.maillist at gmail.com  Wed Apr  8 10:32:55 2009
From: felipero.maillist at gmail.com (Felipe Rodrigues 02)
Date: Wed, 8 Apr 2009 07:32:55 -0700 (PDT)
Subject: [Cruisecontrolrb-users] CC.rb and Grails multiples projects -
 Problem
Message-ID: <22951778.post@talk.nabble.com>


Hi guys...

When trying to use cruisecontrol.rb with multiples grails projects I have
the problem.
The dir name where the source cod is when building the app is used as
project name by grails. This means that when I have two (or more) projects,
when building, grails will be confused, since all of them will be named
"work" (wich is the name of the directory where the code is). Is there any
way to change that in cruisecontrol.rb, even if I have to change some code
and create my own fork of it?

Thanks,

Felipe Rodrigues

-----
Felipe Rodrigues
http://www.fratech.net
-- 
View this message in context: http://www.nabble.com/CC.rb-and-Grails-multiples-projects---Problem-tp22951778p22951778.html
Sent from the CruiseControl.rb - Users mailing list archive at Nabble.com.


From micah at riseup.net  Wed Apr 29 07:40:34 2009
From: micah at riseup.net (Micah Anderson)
Date: Wed, 29 Apr 2009 07:40:34 -0400
Subject: [Cruisecontrolrb-users] Cancelling a build
References: <0562C1EF-159B-439F-B448-7A7C911B8ADC@mattwynne.net>
	<e3af97510904011204l3d78c0ffub19b62ad7e73b24a@mail.gmail.com>
	<04C197D2-78DF-4F52-B812-65742276B748@mattwynne.net>
	<e3af97510904021430g59a6149ag8ea14e8f4a9ee625@mail.gmail.com>
Message-ID: <877i13ofgt.fsf@pond.riseup.net>

Chad Woolley <thewoolleyman at gmail.com>
writes:

> On Thu, Apr 2, 2009 at 12:45 PM, Matt Wynne <matt at mattwynne.net> wrote:
>> So would that mean if I did sudo /etc/init.d/cruise stop it would cancel the
>> build immediately rather than waiting for the builders to finish?

Where is this fabled initscript? I couldn't find it in the latest git
checkout. 

I've got a build running for 39hours now and need to kill it off, would
be nice if I could cancel the build via the UI!

micah
 


From thewoolleyman at gmail.com  Wed Apr 29 21:34:46 2009
From: thewoolleyman at gmail.com (Chad Woolley)
Date: Wed, 29 Apr 2009 18:34:46 -0700
Subject: [Cruisecontrolrb-users] Cancelling a build
In-Reply-To: <877i13ofgt.fsf@pond.riseup.net>
References: <0562C1EF-159B-439F-B448-7A7C911B8ADC@mattwynne.net> 
	<e3af97510904011204l3d78c0ffub19b62ad7e73b24a@mail.gmail.com> 
	<04C197D2-78DF-4F52-B812-65742276B748@mattwynne.net>
	<e3af97510904021430g59a6149ag8ea14e8f4a9ee625@mail.gmail.com> 
	<877i13ofgt.fsf@pond.riseup.net>
Message-ID: <e3af97510904291834v2231bf2dm1704a02d15a6a6ec@mail.gmail.com>

On Wed, Apr 29, 2009 at 4:40 AM, Micah Anderson <micah at riseup.net> wrote:
> Where is this fabled initscript? I couldn't find it in the latest git
> checkout.

in the /daemon dir.  An init script and helper which it references.
Nonstandard, but in ruby and works cross-platform.

> I've got a build running for 39hours now and need to kill it off, would
> be nice if I could cancel the build via the UI!

Yes it would.  I'll wait on your patch :)

-- Chad

From micah at riseup.net  Thu Apr 30 15:57:34 2009
From: micah at riseup.net (Micah Anderson)
Date: Thu, 30 Apr 2009 15:57:34 -0400
Subject: [Cruisecontrolrb-users] Cancelling a build
References: <0562C1EF-159B-439F-B448-7A7C911B8ADC@mattwynne.net>
	<e3af97510904011204l3d78c0ffub19b62ad7e73b24a@mail.gmail.com>
	<04C197D2-78DF-4F52-B812-65742276B748@mattwynne.net>
	<e3af97510904021430g59a6149ag8ea14e8f4a9ee625@mail.gmail.com>
	<877i13ofgt.fsf@pond.riseup.net>
	<e3af97510904291834v2231bf2dm1704a02d15a6a6ec@mail.gmail.com>
Message-ID: <87zldxnccx.fsf@pond.riseup.net>

Chad Woolley <thewoolleyman at gmail.com>
writes:

> On Wed, Apr 29, 2009 at 4:40 AM, Micah Anderson <micah at riseup.net> wrote:
>> Where is this fabled initscript? I couldn't find it in the latest git
>> checkout.
>
> in the /daemon dir.  An init script and helper which it references.
> Nonstandard, but in ruby and works cross-platform.

Great, thanks!

>> I've got a build running for 39hours now and need to kill it off, would
>> be nice if I could cancel the build via the UI!

Actually it seems like when I kill the builders, the next time a build
starts it too goes on for infinity. 

How can I track this down? I tried running every rake task that is setup
for the build for this project, they all return like normal.

> Yes it would.  I'll wait on your patch :)

dont wait long, i've got to learn the language first :P

micah