You might run into the issue seen below when publishing with docker/maven builds containing duplicate artifact entries starting from Artifactory 7.90.15:
24-10-21T22:00:58.1744965Z 2024-10-21 22:00:58.174 [err] [Debug] Usage info sent successfully.
2024-10-21T22:00:58.1745441Z 2024-10-21 22:00:58.174 [err] [Error] Artifactory response: 400
2024-10-21T22:00:58.1745746Z 2024-10-21 22:00:58.174 [err] {
2024-10-21T22:00:58.1745993Z 2024-10-21 22:00:58.174 [err] "errors": [
2024-10-21T22:00:58.1746227Z 2024-10-21 22:00:58.174 [err] {
2024-10-21T22:00:58.1746479Z 2024-10-21 22:00:58.174 [err] "status": 400,
2024-10-21T22:00:58.1746979Z 2024-10-21 22:00:58.174 [err] "message": "Artifact(s) duplicates: sha256__***(**a0347e0***) : 3 time(s)"
2024-10-21T22:00:58.1747341Z 2024-10-21 22:00:58.174 [err] }
2024-10-21T22:00:58.1747564Z 2024-10-21 22:00:58.174 [err] ]
The behavior is caused due to duplicate artifacts attempting to be published and thus the build fails with a 400. In order to control this behavior, starting Artifactory 7.90.15, the below new feature flag was added:
artifactory.build.block.duplicate.entries=false/true
If you wish to stop Artifactory from blocking the publish of duplicate artifacts causing the 400 in your builds, you can set the above property to false.
We can navigate to $JFROG_HOME/etc/artifactory/artifactory.system.properties and apply this property into the artifactory.system.properties file. A restart is required after this change.
After the property has been successfully consumed, we should no longer see the 400 errors causing builds to fail.