multiple simultaneous builds

[Matt Wynne]

Chaos.

Is it possible to prevent ccrb from doing more than one build at once  
for a given project? Because of the lovely database dependency of our  
rails model specs (and, I guess, the acceptance tests too) our build  
is failing when someone pushes before the last build finished, as  
they're fighting over the same database.

Is there a config setting to prevent this, and make the second build  
wait its turn?

By the way - since we switched to the throughtworks main fork for git  
integration, we've had not a whisper of the crazy repeated builds  
problem - flawless performance. Great work guys.

cheers,
Matt
_______________________________________________
Cruisecontrolrb-users mailing list
Cruisecontrolrb-users@...
http://rubyforge.org/mailman/listinfo/cruisecontrolrb-users

[Chad Woolley]

On Tue, Oct 21, 2008 at 10:08 AM, Matt Wynne <matt@...> wrote:

Is there a config setting to prevent this, and make the second build wait its turn?

I think this is what you want in your site_config.rb:

# If you want to only allow one project to build at a time, uncomment this line
# by default, cruise allows multiple projects to build at a time
Configuration.serialize_builds = true

This is in the default site_config.rb, but commented.

-- Chad

_______________________________________________
Cruisecontrolrb-users mailing list
Cruisecontrolrb-users@...
http://rubyforge.org/mailman/listinfo/cruisecontrolrb-users

[Jeremy Lightsmith]

yup, there's a line you can uncomment in site_config.rb (which should be in ~/.cruise/site_config.rb)

it should look like:

Configuration.serialize_builds = true

glad to hear that the thoughtworks repos is doing well for you!

Jeremy

On Tue, Oct 21, 2008 at 10:08 AM, Matt Wynne <matt@...> wrote:

Chaos.

Is it possible to prevent ccrb from doing more than one build at once for a given project? Because of the lovely database dependency of our rails model specs (and, I guess, the acceptance tests too) our build is failing when someone pushes before the last build finished, as they're fighting over the same database.

Is there a config setting to prevent this, and make the second build wait its turn?

By the way - since we switched to the throughtworks main fork for git integration, we've had not a whisper of the crazy repeated builds problem - flawless performance. Great work guys.

cheers,
Matt
_______________________________________________
Cruisecontrolrb-users mailing list
Cruisecontrolrb-users@...
http://rubyforge.org/mailman/listinfo/cruisecontrolrb-users

_______________________________________________
Cruisecontrolrb-users mailing list
Cruisecontrolrb-users@...
http://rubyforge.org/mailman/listinfo/cruisecontrolrb-users

[Ben Greenberg-5]

Hi guys,

Let me first say that CC.rb is a great tool and I have been using is
successfully.

I am wondering if there is a way to have more than one build possibility
for a single code base without having to set up a second project.  The
manual hints at this with the "MyProject.Quick" and
"MyProject.BigBertha" examples when showing how to use case
project.name, but the only way I have gotten this to work is to set up a
separate project using the same source repo.

Is this possible to do?

Thanks,
Ben
_______________________________________________
Cruisecontrolrb-users mailing list
Cruisecontrolrb-users@...
http://rubyforge.org/mailman/listinfo/cruisecontrolrb-users

[Chad Woolley]

On Tue, Oct 21, 2008 at 9:49 PM, Ben Greenberg <mailing_lists@...> wrote:

I am wondering if there is a way to have more than one build possibility for a single code base without having to set up a second project.  The manual hints at this with the "MyProject.Quick" and "MyProject.BigBertha" examples when showing how to use case project.name, but the only way I have gotten this to work is to set up a separate project using the same source repo.

First, I would ask why you don't want to set up a second project?  That's definitely the easiest way.

If you want to use the same project, you could switch on some other variable besides project name (time of day, day of week, phase of the moon).  However, that would be kind of wierd, from the standpoint of having a consistent build.  The specific downside is if a build is green then goes red, you don't know if something broke in your smaller suite, or if something broke in your bigger suite - at least not without looking at the build output.

-- Chad

_______________________________________________
Cruisecontrolrb-users mailing list
Cruisecontrolrb-users@...
http://rubyforge.org/mailman/listinfo/cruisecontrolrb-users

[Matt Wynne]

On 22 Oct 2008, at 05:41, Chad Woolley wrote:

> On Tue, Oct 21, 2008 at 10:08 AM, Matt Wynne <matt@...>  
> wrote:
> Is there a config setting to prevent this, and make the second build  
> wait its turn?
>
> I think this is what you want in your site_config.rb:
>
> # If you want to only allow one project to build at a time,  
> uncomment this line
> # by default, cruise allows multiple projects to build at a time
> Configuration.serialize_builds = true

Thanks guys.

I guess this isn't too much of an issue for us, as we only have two  
projects, but that doesn't actually look like exactly what I want.

I don't care if two different projects build simultaneously, I just  
don't want two builds *for the same project* to be running at the same  
time.

Does that make sense? Is the setting actually doing this, and just not  
clearly documented? Or are we missing a feature?

cheers,
Matt
_______________________________________________
Cruisecontrolrb-users mailing list
Cruisecontrolrb-users@...
http://rubyforge.org/mailman/listinfo/cruisecontrolrb-users

[Ben Greenberg-5]

Thanks, Chad.

What I am really after is the feature in TeamCity that allows you to have different "configurations" of each project.  Each configuration is basically a sub-project under the main project, and can call a different script or target in a script.  But they share the same source code checkout and are logically grouped. So for example you might have Project Foo with Release and Debug configurations that are all grouped together on the console screen.

I can of course achieve the same thing using separate projects, which is what I am doing, and that works fine.

Ben



Chad Woolley wrote:

On Tue, Oct 21, 2008 at 9:49 PM, Ben Greenberg <mailing_lists@...> wrote:

I am wondering if there is a way to have more than one build possibility for a single code base without having to set up a second project.  The manual hints at this with the "MyProject.Quick" and "MyProject.BigBertha" examples when showing how to use case project.name, but the only way I have gotten this to work is to set up a separate project using the same source repo.

First, I would ask why you don't want to set up a second project?  That's definitely the easiest way.

If you want to use the same project, you could switch on some other variable besides project name (time of day, day of week, phase of the moon).  However, that would be kind of wierd, from the standpoint of having a consistent build.  The specific downside is if a build is green then goes red, you don't know if something broke in your smaller suite, or if something broke in your bigger suite - at least not without looking at the build output.

-- Chad

_______________________________________________
Cruisecontrolrb-users mailing list
Cruisecontrolrb-users@...
http://rubyforge.org/mailman/listinfo/cruisecontrolrb-users
  

_______________________________________________
Cruisecontrolrb-users mailing list
Cruisecontrolrb-users@...
http://rubyforge.org/mailman/listinfo/cruisecontrolrb-users

[Martijn van der Woud]

Taken from the CruiseControl Configuration Reference:

The <threads> element can be used to configure the number of threads that CruiseControl can use simultaneously to build projects. This is done through the count attribute. If this element (or one of its parent elements) is not specified, this defaults to 1. This means that only one project will be built at a time. Raise this number if your server has enough resources to build multiple projects simultaneously (especially useful on multi-processor systems). If more projects than the maximum number of threads are scheduled to run at a given moment, the extra projects will be queued.

Jeremy Lightsmith wrote:

yup, there's a line you can uncomment in site_config.rb (which should be in
~/.cruise/site_config.rb)

it should look like:

Configuration.serialize_builds = true