A Build Info containing a dependency/artifact which has the same checksum of some other artifact OR dependency may result in two artifacts racing for the same target path in promotion.
Steps to reproduce:
1. Create a project in Jenkins and build to 'libs-snapshot-local'
2. Run release staging to 'libs-release-local'
3. Run 'copy' build promotion to 'ext-release-local'
4. Go to published modules view in Artifactory, the repo paths are from libs-release-local and ext-release-local
The published modules view searches for artifacts with a specific checksums that have a specific build.name and build.number property, since the promotion copied the artifacts and not moved them, the artifacts are the same on both repositories, and the search could turn up with artifacts from both repositories.
- duplicates
-
RTFACT-8709 License Check Resolved to Wrong Dependency
- Done
- is duplicated by
-
RTFACT-18714 Wrong artifact repo path in BuildInfo when uploading binary identical artifacts
- Done
-
RTFACT-17062 Add ability to see all repos that have artifacts from a build in the build browser UI
-
- Done
-
- is related to
-
RTFACT-17239 Delete Builds and Control Build Retention REST API ignore artifacts properties build.name and build.number
- Backlog
- relates to
-
RTFACT-12087 Promotion fails if the artifact exists twice in the artifacts section
- Open
-
RTFACT-6005 Incorrect published modules repo paths
- Open