[Cruisecontrolrb-users] Keeping CRUISE_DATA_ROUTE under version control
jeremy.lightsmith at gmail.com
Fri Aug 29 12:31:55 EDT 2008
the other file that you need is cruise_config.rb, this is a per project
config file. in general, I'd suggest that it live inside the project
itself, because it's much easier to configure that way. however, you can
also place it in <cruise>/<project_name>/ and in fact there should be one
there that cruise creates for you.
why do you want to do what you're suggesting? I'm with chad, I think it'd
be easier to create a script that recreates the cruise environment on a new
machine and uses files that you have checked into your project. However, I
don't know exactly what you're trying to do, maybe you have a good reason
for doing it the way you're suggesting.
On Fri, Aug 29, 2008 at 8:13 AM, Chad Woolley <thewoolleyman at gmail.com>wrote:
> On Fri, Aug 29, 2008 at 7:25 AM, Matt Wynne <matt at mattwynne.net> wrote:
> > I have a goal to allow any of us on the team to be able to fetch the
> > environment locally and run / hack it, them commit their changes back and
> > able to easily deploy them to the team's shared build environment.
> Instead of moving where CRUISE_DATA_ROOT is, maybe you could just make
> a script which symlinks/copies the files you need from your project to
> the default location of ~/.cruise.
> For example, have a ./setup_ccrb.rb scrpt in your project which will
> clone the git repo, set up the project by issuing the correct .cruise
> add command, and symlink site_config.rb/css. You would have the same
> symlinks in the shared environment. All the symlinked files could
> live in the project - and there shouldn't be many more cruise-related
> files to symlink than site_config and css, right?
> -- Chad
> Cruisecontrolrb-users mailing list
> Cruisecontrolrb-users at rubyforge.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Cruisecontrolrb-users