Sorry for the confusion, but my questions were about the new method. I have installed 1.4 release for the new pre-processor and have had great success within a single server. What I am trying to do now is create some general include files that can be included by multiple servers and only overriding variables where necessary. What I was thinking (with the heading) was define all the variables in 1 file (so that I can add to it without having to include new files every time I create a new project type for all servers) then a second which uses them all. So I can include the first, override any variables (re- scope) and then include the second file which uses them. But then as I was typing I came across a few other possibilities which I listed above.
Again thanks for any help in advance. Arieh On Oct 24, 8:14 am, "Brendan Crosser-McGay" <[EMAIL PROTECTED]> wrote: > I've had lots of success with the approach Ruben suggests here Arieh. You > can make templates of templates of templates with preprocessor code. > > I even installed a copy of CCnet on my own machine just to test how far I > could push the preprocessor blocks, and I found it incredibly useful for > reducing complexity of the config file in almost every respect. > > -Brendan > > On Thu, Oct 23, 2008 at 12:32 AM, Ruben Willems <[EMAIL PROTECTED]>wrote: > > > Hi > > > take a look at > > >http://confluence.public.thoughtworks.org/display/CCNET/Configuration... > > 1.4 release or higher is required > > > with kind regards > > Ruben Willems > > > On Thu, Oct 23, 2008 at 9:26 AM, Arieh Schneier <[EMAIL PROTECTED]>wrote: > > >> Is there a way I can have multiple sections inside an included file. > > >> I have a number of servers running the same projects with very slight > >> differences on each (basically a different config of the same > >> projects). But I want to have some options which have a default > >> setting unless I specifically change it for that server. > > >> What I was thinking was, create an include file that has all the > >> defaults that I can then overwrite if I want. At the moment I have to > >> have a separate file for every default that I want to set, and then > >> include that file from every server. I would like to be able to just > >> have 1 default file (so that I can modify and add values to it without > >> having to modify every servers config to include the new default). > > >> An example of why I need it, is that most of the projects are not > >> automatically built, but on 1 of the servers we want to have a set of > >> triggers for 1 of the projects (this project will be on each server). > > >> A couple of ways (not sure if currently possible) to solve my problem, > >> in order of preference: > >> 1) Be able to define and XML Reference only if it isn't already > >> defined (so I can have the default set in my included file, but be > >> able to override it before including the file). > >> 3) Have a branch type section, eg if 'somevalue' is true then include > >> the next set of statements. > >> 2) Have a section which is basically ignored, so that multiple > >> sections can be defined within the same include file (have a defaults > >> file which I include at the start, and can add to whenever I have a > >> new default). > > >> I hope I was clear enough in explaining what I am trying to achieve. > > >> Thankyou in advance. > > >> Arieh
