On Fri, Aug 29, 2008 at 7:25 AM, Matt Wynne <[EMAIL PROTECTED]> wrote: > I have a goal to allow any of us on the team to be able to fetch the build > environment locally and run / hack it, them commit their changes back and be > 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 [email protected] http://rubyforge.org/mailman/listinfo/cruisecontrolrb-users
