Artifact Dependence on the Same Build Configuration in TeamCity

I would like to set up a TeamCity build that will do incremental builds.

To do this, I want to save the build outputs (DLL files) as artifacts and reuse them each time I build them again (copy the latest artifacts to the build agent before starting the build).

This effectively places the latest build artifacts in the project's output folder, so MSBuild can use these artifacts to determine if it needs to rebuild any of the sources.

I tried to do this, but it seems TeamCity does not allow you to configure artifact dependencies from the same build configuration.

For example, if I have a Build Plugins configuration that generates a collection of DLL modules, I cannot use them as a dependency for the same build configuration ...

Is there any inherent way to overcome this in TeamCity or to create a simple solution?

+4
source share
2 answers

It seems that this is only possible using templates.
You can create a template for the assembly. Then you create an assembly from this template. After that, you add this assembly depending on the artifact from the template. This allows you to use circular dependencies.
I have not found another way.

+3
source

Looks like you can do it now! It seems to work in 9.0.1, and TW-12984 says it should work in 8.1 as well.

+1
source

All Articles