close fullscreen

Idea

Cruise Control+status
closed
help edit space_dashboard

Cruise Control+priority
low
help edit space_dashboard

Cruise Control+tag
Design
help edit space_dashboard

 

Cruise Control+issues

help edit space_dashboard

We are using Cruise Control to run continuous integration, and we need support for this out of the box, so you can just add a repo/branch to Cruise Control and have the builds start.

 

Cruise Control+solution

help edit space_dashboard

Add cruise_config.rb to the root directory of the repo and add support scripts.

 

 

help edit space_dashboard

I have this more or less worked out on the format_renderer branch,  but I want to make this independently.

 

The way it work now, you have to untar script/crz_sample_config.tgz in ~/.cruise/projects, then the config in the repo will work.  I want to move the scripts into script, but I want to get some input on the 'spec' before finalizing it.

  1. Where do you want the config files?  At first I was thinking shared files in ~/.cruise/projects and per-instance ones in ~/.cruise/projects/<instance name>/, but now I think they should all go in the build working directory.
  2. How do you want to configure things like which database, which Rails version, etc.


Not sure what else to tag this - Is it Tests-related?

  --John Abbe.....Mon Jan 31 12:31:43 -0800 2011


I think we're bailing on this in favor of Jenkins

  --Ethan McCutchen.....2013-02-25 00:21:52 +0000

Cruise Control+discussed in support tickets

help edit space_dashboard

Cruise Control+relevant user stories

help edit space_dashboard