Using TeamCity, how to manually launch DEPLOY against a previously built and tested build launch?

Question

Using TeamCity 6.5, I'm trying to figure out how to configure manual deployment for a specific build run, if possible.

What I would like to do is to execute the already built and tested TeamCity launch (you need to deploy only artifacts - this is not a web application or site), and the MSBuild step is called to publish artifacts for somewhere else.

Answer 1

You can do what you want by setting Artifact Dependency between the configurations in which you want to perform manual deployment and where you created the built-in artifacts.

Once you configure the artifact dependency, click on the Run custom build ellipse next to the Run custom build button for configuration. Here you will have a part of Artifacts dependencies , where it will be indicated that the configuration on which this configuration is performed depends and will also have a drop-down list from which you can select a specific version of another configuration from which you can get artifacts. Click here to start your own build.

See here http://confluence.jetbrains.net/display/TCD65/Triggering+a+Custom+Build for more details.

Answer 2

You can think about it a little back. You probably need a build configuration that uses the previously known successful build (in terms of TC, it has a snapshot dependency) and then runs another build designed to remove artifacts. Pretty easy to do by switching output directories to MSBuild.

Answer 3

The most “integrated” way I could think of would be to add a deployment configuration dependency that depends on the last pinned assembly for the dependent configuration. Then, you simply don’t insert the new assemblies in the dependent configuration and push the one you want and start the deployment ... This is a little silly and might not work very well if you depend on pinned assemblies for anything else in the dependent configuration.

Another built-in way to do this is to add an artifact dependency using a specific build number. The disadvantage of this method is that at any time when you want to deploy another assembly, you will need to manually edit the assembly number of the artifact dependencies, and then click run.