Deploying artifacts that have the same checksum as existing promoted artifacts causes referenced artifacts in promoted builds to update incorrectly.
If you look in the example below, the artifact NerdDinner.zip, NerdDinner.deploy.cmd, NerdDinner.SetParameters.xml are actually promoted artifacts that were previously promoted from the vertafore-dev repo to the vertafore-integration repo. Since then, however, a new build was created that did not meet the promotion criteria and thus remained in the vertafore-dev repo. However, NerdDinner.deploy.cmd and NerdDinner.SetParameters.xml have not changed, and thus have the same checksum as the artifacts that are referenced by the tracer:17 build. The build is incorrectly updating the artifacts to the newly deployed references, and not retaining the previously referenced checksums.
This can cause issues when resolving artifacts. So for example, if you are resolving artifacts from the vertafore-integration repo for build tracer#17, Artifactory will only resolve NerdDinner.zip, when it should really resolve the previously referenced checksums for NerdDinner.deploy.cmd and NerdDinner.SetParameters.xml.
If you look in the tree browser, you will find that the referenced artifacts are still in the correct place.
If you delete all artifacts that were deployed that have the same checksum as the artifacts in this build, then the build will reference the previously referenced checksums correctly.