[RTFACT-9343] Build artifacts path-matching may match the same path for more than one of the build artifacts Created: 17/Feb/16  Updated: 05/Jan/20

Status: Open
Project: Artifactory Binary Repository
Component/s: None
Affects Version/s: 4.5.0
Fix Version/s: None

Type: Bug Priority: High
Reporter: Uriah Levy Assignee: Tamir Hadad
Resolution: Unresolved Votes: 9
Labels: QF, QF-P2

Issue Links:
Duplicate
duplicates RTFACT-8709 License Check Resolved to Wrong Depen... Resolved
is duplicated by RTFACT-18714 Wrong artifact repo path in BuildInfo... Resolved
is duplicated by RTFACT-17062 Add ability to see all repos that hav... Resolved
Relationship
relates to RTFACT-12087 Promotion fails if the artifact exist... Open
relates to RTFACT-6005 Incorrect published modules repo paths Open
is related to RTFACT-12087 Promotion fails if the artifact exist... Open
is related to RTFACT-17239 Delete Builds and Control Build Reten... Open
Sprint: Leap 26, Pam - Quality 3

 Description   

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.


Generated at Wed Feb 19 05:09:14 UTC 2020 using JIRA 7.6.16#76018-sha1:9ed376192612a49536ac834c64177a0fed6290f5.