Runtime dependency patterns in TC

Does anybody have recommendations for organizing runtime dependencies for packaging or deployment in TeamCity? Say a component has a runtime dependency that it doesn't need during compilation, but a specific build of that component requires some of the artifacts from a specific version of some other component at runtime, so must be present in packaging for the product or in any deployment.

These are non-maven c++ components.

It looks to me like we either have to retrieve these runtime dependencies during each component build at compilation time and deliver them as artifacts with each build of that component, or else we have some downstream build configuration that is hopefully correctly configured to retrieve the right runtime dependency at packaging/deployment time.

Can TC retrieve artifacts as dependencies based on information in, say, a text file found in the artifacts for a built component?


Please sign in to leave a comment.