[Cruisecontrolrb-users] Is CruiseControl.rb for me?

[Chad Woolley]

On Mon, Apr 21, 2008 at 1:32 PM, Eric Hanchrow <eric.hanchrow at gmail.com> wrote:
> Thanks for the quick response, but I don't think externals will work,
>  because I don't want to change the structure of our source tree; doing
>  so would force the developers to change the way they work, and one of
>  my goals is to avoid that.

As Jeremy said, you may try build triggers.  If that doesn't work, I
think svn:externals could definitely work.  We've put a lot of effort
into making sure externals are detected and reported properly in
change detection and changeset reporting, and I think trunk works
mostly pretty well in this area :)

As for having to change the source tree, how about this:  You can have
a separate project, which is only used to build your "kit".  This
project is composed of only externals, which arrange things in the
proper way to achive a build (perhaps with some hacks to your build
process).  Your developers can use the regular repo locations the way
they normally do, this separate project that ties everything together
via externals will only be used by cruise.rb.

Just an idea, let us know if you get it working.

-- Chad