Comments on: Refactor your configuration file

By: 2008 in posts — The Build Doctor

2008 in posts — The Build Doctor — Tue, 30 Dec 2008 15:32:42 +0000

[...] Refactor your configuration file This one really seemed to strike a [...]

By: simpsonjulian

simpsonjulian — Tue, 04 Nov 2008 15:45:46 +0000

John,

What help do you need?

Julian.

By: John

John — Tue, 04 Nov 2008 12:28:03 +0000

But this doesn’t help much with ant scripting.

By: Julian

Julian — Mon, 25 Aug 2008 20:30:00 +0000

Anon,

You can template out projects more: if every configuration detail is derived from the project name, there’s a way to template out the whole shebang. The ${project.name} value is lazily loaded, so it becomes dynamic. Not sure if I have the example any more – let me mull it over.

By: Anonymous

Anonymous — Wed, 20 Aug 2008 08:30:00 +0000

I notice that both chico and groucho project configs are identical barring the project name...

This matches my configuration where I regularly add/remove live branches to the configuration and have to copy/paste previous project configs.

What would be really cool is if I could pass in the project name like this -

Then I would only have to maintain one project config.

By: Julian

Julian — Tue, 08 Apr 2008 21:58:00 +0000

Sean,

You're right. I have used them to great effect with things like the email publishers. I'll update the post some time soon.

Thank you!

Best

Julian.

By: Sean M.

Sean M. — Mon, 07 Apr 2008 16:40:00 +0000

No mention of plugin preconfiguration? Don't build without 'em.

By: Ben

Ben — Mon, 03 Mar 2008 14:27:00 +0000

Is there a way to force it to fail if it cannot read an included file? Otherwise someone could delete an included file and some projects will stop being monitored/built.

By: Julian

Julian — Mon, 03 Mar 2008 13:38:00 +0000

Hi Ben,

You can define objects in the parent file and have them visible to projects that are included from that parent file. I don’t have a working copy of CruiseControl on me at the moment to test that, but I *think* it ought to work.

The validator that I wrote just calls CruiseControl’s own config system to read the file, so it will just read the included files. It shouldn’t fail the build if a project file is missing. I quite like that because it means that even if you can’t convince somebody to edit the XML file when they remove a project, most people will be okay to delete the file.

Slightly annoying at validation time, however

Best

Julian

By: Ben

Ben — Mon, 03 Mar 2008 08:49:00 +0000

I have a couple of questions:

1. Is the include.project really an include? We have defined "plugins" as project templates, so if these are defined in the parent file and the projects listed in the imported files, then presumably it will be read in OK?

2. Does the CruiseControl Validator you posted about a little while ago work with included files?