Comments on: Configuring Projects on Multiple Instances of Cruise Control .Net

By: admin

admin — Tue, 15 Sep 2009 06:36:47 +0000

Thanks, Anders

By: Anders Juul

Anders Juul — Tue, 15 Sep 2009 04:27:34 +0000

Nice article, thanks for sharing!
As for Elads comment (I know it’s old ), I’m using scoping and reuse blocks in my ccnet.config – it can be really neat. Checkout http://confluence.public.thoughtworks.org/display/CCNET/Configuration+Preprocessor . Write to me at andersjuulsfirma at gmail dot com for a copy of my configuration.

By: Reusing Cruise Control .Net Configurations on the Same Instance « The Simple Part

Sat, 05 Jul 2008 14:59:04 +0000

[...] post follows up from my previous post, Configuring Projects on Multiple Instances of Cruise Control .Net. In one of the comments to this post, Elad asked if it was possible to reuse configuration files on [...]

By: karlagius

karlagius — Thu, 03 Jul 2008 08:11:48 +0000

Hi Elad, thanks for your comment.

I see how that would be useful, but I’m not quite sure it’s supported. I’ll look into it though

By: Elad

Elad — Wed, 02 Jul 2008 12:33:53 +0000

Thanks, this article was useful indeed. How about the following:
Suppose I want to re-use the same project twice in the same CCNet.config file but with different ‘parameters’. For example, I want to run the same build script – once on a development branch and then on a release branch. I’d like to use a single CC server for both projects and of course, I don’t want to duplicate the project item contents. Is this doable?

By: karlagius

karlagius — Wed, 11 Jun 2008 08:01:28 +0000

Ouch! You’re right :$ Mixed up the nant and msbuild properties file. The MsBuild properties file is actually an xml file – corrected the post above.

Many thanks for pointing this out

By: questate

questate — Tue, 10 Jun 2008 23:20:08 +0000

RE: Externalize all paths in your build script to a properties file

not sure how you did this, a properties file w/ key and value cannot be imported in MSbuild using the method you displayed. User gets error “The imported project file could not be loaded. Data at the root
level is invalid. Line 1, position 1.”