Cruisecontrolrb users - May 2007 - Forcing builders to run sequentially

Hi All --

I have several builds running under CC.rb that deploy and test against
shared, remote server. Unfortunately, the common server sags and frequently
fails if there are too many builds hitting it.

By default, builders run in parallel. I need them to run sequentially.
Anyone know if there is there an existing hook for this? Alternately, if I
need to code this, pointers on where to look in the CC.rb code base would be
appreciated. (ie: what controls a builder''s life cycle).

Thanks in advance,
Levi
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://rubyforge.org/pipermail/cruisecontrolrb-users/attachments/20070521/1e6da35a/attachment.html

Levi Cook wrote:
> Hi All --
> 
> I have several builds running under CC.rb that deploy and test against
> shared, remote server. Unfortunately, the common server sags and
> frequently fails if there are too many builds hitting it.
> 
> By default, builders run in parallel. I need them to run sequentially.
> Anyone know if there is there an existing hook for this? Alternately, if
> I need to code this, pointers on where to look in the CC.rb code base
> would be appreciated. (ie: what controls a builder''s life cycle).
I would definitely be interested in this as well. In my case there is
one physical project with 3 virtual projects in ccnet. One project just
compiles, other runs smoke tests, the third runs the complete regression
test suite.

Since all the three are located at the same location, and need to
start/stop tomcat for some tests, I need to have them run sequentially,
fortunately there was a plugin available for ccnet that allowed me to do
this.

Is there any way this can be achieved in cc.rb ?

-- 
Ketan Padegaonkar
I blog... therefore I am... http://ketan.padegaonkar.name/

<taniwha> i''d solve a windows key problem with fdisk :)

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: OpenPGP digital signature
Url :
http://rubyforge.org/pipermail/cruisecontrolrb-users/attachments/20070522/09926122/attachment.bin

> Levi Cook wrote:
> > By default, builders run in parallel. I need them to run sequentially.
I would just hack it in.

Every builder grabs an exclusive lock on some file (the same for all
three builders) before the build, or just waits until it can grab that
lock.

By the way, this can be pluginized, too.

Best regards,
Alex

Alexey Verkhovsky wrote:
>> Levi Cook wrote:
>>> By default, builders run in parallel. I need them to run
sequentially.
> 
> I would just hack it in.
> 
> Every builder grabs an exclusive lock on some file (the same for all
> three builders) before the build, or just waits until it can grab that
> lock.
> 
> By the way, this can be pluginized, too.
Cool, just what I''d expected.

How about a HOWTO on how to hack together a plugin? Not many people
(like me) understand ruby/rails and would like some pointers on how I
should go about putting my own stuff in.

I''m having a hard time just fixing the issue of a hardcoded
"nextBuildTime" in index_cctray.rxml to make it return something
useful
from the ProjectScheduler or whatever. This is needed for the CCTray
that I''ve put together. It connects to cc.rb, but cc.rb has issues with
date formatting :(

-- 
Ketan Padegaonkar
I blog... therefore I am... http://ketan.padegaonkar.name/

* Linux Viruscan.....
  Windows 95 found.  Remove it? (Y/y)
	-- Unknown source

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: OpenPGP digital signature
Url :
http://rubyforge.org/pipermail/cruisecontrolrb-users/attachments/20070522/086358be/attachment-0001.bin