Affects Version/s: 2.4.6
Fix Version/s: None
Jenkins LTS 1.625.3 on Debian GNU/Linux , Builds on Windows 2008 R2 + Debian GNU/Linux , Oracle Java 8u74
When using generic Artifactory integration, uploading of entiry directory structures of maven2/3 artifacts may fail due to existing checksum files.
We're using some quite complex freestyle jobs depending on generic Artifactory integration for artifact upload to our instances of Artifactory Pro.
Some of those jobs consist of a combination of shell scripts and multiple Maven invocations (partially Maven invocation happens by thirdparty build tools we can't change/configure), deploying to a local directory which gets configured as source for uploads to Artifactory.
When those maven invocations of thirdparty tools deploy artifacts to the upload directory, checksum files (sha1 and md5) get deployed alongside the artifacts they belong to.
The generic Artifactory integration regularly stumbles across those checksum files, trying to upload them before uploading the corresponding artifact.
That way uploading of checksum files gets denied by error 409 due to no artifact being uploaded before that checksum file
By now we worked around this issue by deleting all checksum files as an explicit build step before uploading of artifacts happens.
It would be nice if generic Artifactory integration would check the file name of files being uploaded, identifying checksum files as such and then try to find and upload the artifact file before uploading the checksum file.