Jenkins scripted pipeline breaks while uploading the maven Artifact to Artifactory with 404 error

0
votes

I am using Jenkins's scripted pipeline and while uploading the Artifacts to Artifactory I am getting an error.

This is the code from my Jenkins scripted pipeline:

stage('Build') {

    rtMaven.run pom: 'java-proj/pom.xml', goals: '-X clean install', buildInfo: buildInfo;
}

The error which I am getting is:

[main] DEBUG org.jfrog.build.extractor.maven.BuildInfoClientBuilder - Failed checksum deploy of checksum 'xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx' with statusCode: 404

It uploads the artifacts half way and then somehow, it gets non zero exit code and it breaks the pipeline build.

I am using this Jfrog doc for reference and following exact syntax.

Thanks, G

1
jenkins-pipelineartifactory

1 Answers

1
votes

Not sure if it’s the same issue, but I’ve seen this when one of the artifacts is a .md5, .sha1, or .sha256 extension. When such an artifact gets uploaded, artifactory appears to treat it as a checksum of an existing artifact in the repository. If an artifact of the same name without the hash extension does not exist then a 404 is thrown.