Affects Version/s: None
Fix Version/s: None
Published modules view on copied promoted builds shows some of the artifacts repo paths from the staged repository and some of the paths from the promoted repository.
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.