[RTFACT-6388] Promotion doesn't copy/move artifacts with identical sha1 hash values Created: 17/Mar/14  Updated: 14/Nov/17  Resolved: 13/May/15

Status: Resolved
Project: Artifactory Binary Repository
Component/s: Build System
Affects Version/s: 3.1.1.1, 3.4.2
Fix Version/s: 3.3.0, 3.7.0

Type: Bug Priority: Critical
Reporter: Kevin Formsma Assignee: Dan Feldman (Inactive)
Resolution: Fixed Votes: 1
Labels: None

Issue Links:
Duplicate
duplicates RTFACT-5756 Build artifact references update inco... Resolved
Relationship
is related to RTFACT-7018 When 2 or more artifacts with the sam... Resolved
Assigned QA: Daniel Keler

 Description   

We have a ivy module which happens to have multiple artifacts with the same sha1 values. Since upgrading to artifactory 3.1.1.1, when a build is promoted, these artifacts are not copied/moved from the source repository to the target repository. Previously, all the artifacts of the build were copied/moved as expected.

Workaround is to force the sha1 to be different or manually copy these artifacts after our promotion process. This is causing significant additional work for us when promoting a build as we currently cannot make these artifacts have different sha1 values.



 Comments   
Comment by Sharon Alin (Inactive) [ 23/May/14 ]

https://www.jfrog.com/jira/browse/RTFACT-5756

Comment by Kevin Formsma [ 06/Nov/14 ]

Any reason why this was re-opened? The issue has been resolved for us with artifactory 3.4.0 as indicated in RTFACT-5756.

Comment by Roy Zanbel (Inactive) [ 19/Nov/14 ]

Sorry, this was done by mistake, issue was fixed in version 3.3.0

Comment by Kevin Formsma [ 08/Dec/14 ]

This issue is happening for us again since upgrading to 3.4.2; Several artifacts have the same sha1 value and only one of them gets moved during a promotion instead of all artifacts.

Comment by Craig A Bailey [ 09/Dec/14 ]

Is there a defined downgrade path to revert back to the prev version?

Comment by Ariel Seftel [ 11/Dec/14 ]

We have managed to reproduce the issue with version 3.4.2 and looking for the root cause.
We will update this Jira once we will have an estimation for the fix.

Comment by Kevin Formsma [ 05/Feb/15 ]

Any update on the status of this bug?

Comment by Dan Feldman (Inactive) [ 09/May/15 ]

Promotion behavior is fixed to match all build artifact entries (from build info) to all existing artifact paths in Artifactory.

Generated at Thu Dec 12 04:12:10 UTC 2019 using JIRA 7.6.16#76018-sha1:9ed376192612a49536ac834c64177a0fed6290f5.