Snapshot dependencies and VCS roots

Given I have a build chain like this:
"Compile" -> "Deploy to test" -> "Deploy to prod", where "Deploy to test" is snapshot dependent on "Compile" and "Deploy to prod" is snapshot dependent on "Deploy to test". Both "Deploy to test" and "Deploy to prod" has an artifact dependency on "Compile".

I have environment configuration files for "Test" and "Prod" in source control. What I want is to be able to always get the latest version of these configuration files so that I can change them without going through the whole chain once again. This would also enable me to add more environments and deploy to them using an existing chain instance. I would like to specify a VCS root that is configured to ignore the snapshot. Is this possible to do in some way?

Thanks.

3 comments
Comment actions Permalink

Hi Gøran,

There is no such ability at the moment. May be you can use artifact dependencies instead of snapshot ones?

0
Comment actions Permalink

I already have artifact dependencies. Both "Deploy to test" and "Deploy to prod" has an artifact dependency on "Compile" in addition to the snapshot dependencies ("Compile" -> "Deploy to test" -> "Deploy to prod"). Are you talking about having a separate "build" for configuration files and set up an artifact dependency for the last successful of that build configuration? That actually could work... Another solution is to put all environment configuration parameters inside the build configuration. However, I will then loose source control for those parameters. It all come down to the fact that I want TeamCity to be a little more native about release managment.  

Thanks.

0
Comment actions Permalink

I meant you can probably have only artifacts dependency (and no snapshot dependency) if you want to
- use latest deployment options for deploying builds
- be able to select different builds (not necessarily the latest one) for deployment

> It all come down to the fact that I want TeamCity to be a little more native about release managment.  
This is a bit too general and I would appreciate if you can detail the specific issues/abilities that you need and which cannot be achieved with the current functionality.

0

Please sign in to leave a comment.