Is it possible to use Artifactory as a dependency source and still achieve change and nested dependency information? That is, can Artifactory be a transparent artifact dependency in a TeamCity build?
In particular I wonder if we can publish artifacts to Artifactory and then consume them in another build, as a build dependency, and still achieve:
- Notification: Ability to email build notification to authors of changes in the build (since last, as per normal TeamCity to TeamCity (TC-TC) dependency behaviour)
- Reproduce build: Ability to be able perform custom build from RCS (git) history and use stored Artifact artifacts.
I suppose I'm asking how far the latest Artifactory integration goes to integrate Artifactory to work as a TeamCity artifact dependency.