Template trigger and dependency relationships

I'm trying to templatize a series of build configurations in a project and have stumbled when attempting to define finish build triggers and snapshot dependencies to other builds that are templates.  To illustrate with an example of what I'd like to do:

Project TProject contains templates TA, TB, TC where:
TA has a snapshot dependency on TB
TA has a finish build trigger on TC

I would like to create a project "XProject" such that:
XProject contains configurations XA, XB, XC where:
XA is an instance of template TA
XB is an instance of template TB
XC is an instance of template TC
XA has a snapshot dependency on XB
XA has a finish build trigger on XC

At some point in the future, I'd like to make a project "YProject" such that:
YProject contains configurations YA, YB, YC where:
YA is an instance of template TA
YB is an instance of template TB
YC is an instance of template TC
YA has a snapshot dependency on YB
YA has a finish build trigger on YC

It seems that my only option is to manually create instances of each build config template and then manually set the triggers and dependencies.  Is there a way to do this automatically?  ultimately, I'd like to have the concept of a "Project Template" where I can instantiate an entire project and its internal trigger and dependency relationships are instantiated as described above as well.

3 comments
Comment actions Permalink

A shorter example.  I have a complicated build and end to end system test project with many internal dependent and triggering build configuration relationships.  The project runs on a particular target hardware system located in one geographic region.  I want to duplicate this TeamCity project along with dependencies and triggers to test on an identical but separate system that requires property changes but maintains overall unity of build configurations.  How do I achieve this without having to hand-reconfigure all dependencies and finshed build triggers?

0
Comment actions Permalink

Figured out how to do this.  I just needed to copy an instance of a project that already references templates rather than attempting to instantiate instances of the templates themselves.

0
Comment actions Permalink

Yeah, I was checking right this solution.

0

Please sign in to leave a comment.