Ever since upgrading to 1.442, I'm unable to deploy packages up in to my Maven repository hosted in Nexus.

      org.apache.maven.artifact.deployer.ArtifactDeploymentException: Failed to deploy artifacts: Could not transfer artifact com.company.core:dbt-core:jar:1.0.0-20111207.203519-81 from/to com.company.sandbox

      Nexus is returning a 401 response code and I've ensured my credentials are indeed valid.

          [JENKINS-12031] Maven deploys fail after upgrade to 1.442

          Mark Maun added a comment -

          I've also seen this issue. We upgraded from 1.408 to 1.457 on a Beta server and we are seeing the same issue. The compilation is successful but on transferring the artifact to Nexus it's returning a 401 unauthorized message and failing. The settings.xml has not changed and file transfers were working great with 1.408.

          I'm using Maven 3.0.4. I even got on a support call with Sonatype and was able to transfer the artifacts directly, just not using Jenkins.

          Mark Maun added a comment - I've also seen this issue. We upgraded from 1.408 to 1.457 on a Beta server and we are seeing the same issue. The compilation is successful but on transferring the artifact to Nexus it's returning a 401 unauthorized message and failing. The settings.xml has not changed and file transfers were working great with 1.408. I'm using Maven 3.0.4. I even got on a support call with Sonatype and was able to transfer the artifacts directly, just not using Jenkins.

          evernat added a comment -

          Is it reproduced with a recent Jenkins version?

          evernat added a comment - Is it reproduced with a recent Jenkins version?

          evernat added a comment -

          No response from the reporter, so resolving as incomplete.

          evernat added a comment - No response from the reporter, so resolving as incomplete.

            Unassigned Unassigned
            jplock Justin Plock
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: