[JIRA] (JENKINS-59973) rtUpload / rtDownload fail with HTTP 401 / 403

[benoit.donne...@gmail.com (JIRA)]

Title: Message Title

Benoit Donneaux commented on JENKINS-59973   Re: rtUpload / rtDownload fail with HTTP 401 / 403 We ran in the same problem with v3.4.1 for Maven projects in Jenkins 2.190.2 (LTS): 10:05:03 [INFO] Deploying artifact: https://xxx.jar 10:05:06 [ERROR] org.jfrog.build.extractor.maven.BuildInfoRecorder.sessionEnded() listener has failed: 10:05:06 java.lang.RuntimeException: Error occurred while publishing artifact to Artifactory: /var/lib/jenkins/workspace/Card Node Snapshot/xxx.jar. 10:05:06 Skipping deployment of remaining artifacts (if any) and build info. 10:05:06 at org.jfrog.build.extractor.maven.BuildDeploymentHelper.deployArtifacts (BuildDeploymentHelper.java:303) 10:05:06 at org.jfrog.build.extractor.maven.BuildDeploymentHelper.deploy (BuildDeploymentHelper.java:103) 10:05:06 at org.jfrog.build.extractor.maven.BuildInfoRecorder.sessionEnded (BuildInfoRecorder.java:173) 10:05:06 at org.apache.maven.lifecycle.internal.DefaultExecutionEventCatapult.fire (DefaultExecutionEventCatapult.java:64) 10:05:06 at org.apache.maven.lifecycle.internal.DefaultExecutionEventCatapult.fire (DefaultExecutionEventCatapult.java:42) 10:05:06 at org.apache.maven.lifecycle.internal.LifecycleStarter.execute (LifecycleStarter.java:137) 10:05:06 at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305) 10:05:06 at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192) 10:05:06 at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105) 10:05:06 at org.jvnet.hudson.maven3.launcher.Maven35Launcher.main (Maven35Launcher.java:130) ... 10:05:06 Caused by: java.io.IOException: Failed to deploy file. Status code: 401 Response message: Artifactory returned the following errors: 10:05:06 Unauthorized Status code: 401 Downgrading to v3.3.x worked around the issue for us too. I kind of feel this is related to picking up the right credentials. Our jobs do not 'Override default deployer credentials' and rely on the ~/.m2/settings.xml file being populated with those. But so far, I've not managed to work around this issue by changing the credential settings of the job. Looking at the recent commits, I wonder if this one could be the culprit: [HAP-1219] folder scoped credentials for deploy step (#171) Add Comment   This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202777.1572351580000.5548.1574428020236%40Atlassian.JIRA.