Nick Pellow wrote:
> Hi Erik,
> We managed to get CruiseControl working with 20 projects at the same time
> without having to change one build file. Since each of our
> projects already had standard targets Ant was powerful enough to handle the
> SCM integration. We just needed to write a wrapper build file that took
> System Properties from the cruise instance and did all the cruise specifc
> work.
> This means each of our projects is still "cruise agnostic".
> It works well for us!
>
> Regards,
> Nick.
Yes, this is exactly what we do as well. I have a cruise-build.xml that
does the <cvs> checkout and <ant>'s to the main build file - so our main
build has nothing about CruiseControl in it.
And with some clever use of property overriding you can have
<junitreport> reports written to a web accessible directory with no
changes to the main build, just when run with CC do things get put in
different places to facilitate reporting.
Erik
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
