Hi, I have to say "Template" is not quite the right word but I can't currently think of a better one..
We have quite a few builds that are based on the same "template", they are all clones of a particular build I have called "Generic_Ivy_Module_Template". All these jobs are identical to the generic one aside from a handful of changes, such as the location of the source code and project name. All good so far. If I decide to make a change to the master "Template" and make this change effective for all its clones then I need to go into each and every clone and update them. Yes I know I can change the config.xml using a global search and replace - actually that is often what I do. However it would be really cool to have a better mechanism, ideally where there was some sort of master job and any changes to that we automatically used by the clones. Something like this may exist and I have missed it. Incidentally I have multiple "templates". Thanks
