HTTP 401 is usually sent when you're not authenticating at all. Check your credentials. Remember, for the Maven repo, you need to use your jenkins-ci.org account credentials, not GitHub.
On 15.07.2015, at 01:18, 'Wei Zheng' via Jenkins Developers <[email protected]> wrote: > Hi, > > Today when I tried to release a new version of my plugin using "mvn > release:prepare release:perform", it eventually failed with the following > error message: > > The new code has been pushed to the repo (i.e. with the updated version in > pom.xml), but the hpi file is not uploaded to the right place. I am trying to > update from version 0.1 to 0.2, but under here only version 0.1 exists: > http://repo.jenkins-ci.org/releases/org/jenkins-ci/plugins/google-container-registry-auth/, > and http://mirrors.jenkins-ci.org/plugins/google-container-registry-auth/. > > Is this a problem on my side? Or on the server side? How should I fix it? > > Thanks! > Wei > > [INFO] Uploading: > http://maven.jenkins-ci.org:8081/content/repositories/releases/org/jenkins-ci/plugins/google-container-registry-auth/0.2/google-container-registry-auth-0.2.pom > [INFO] 2/7 KB > [INFO] 4/7 KB > [INFO] 6/7 KB > [INFO] 7/7 KB > [INFO] > [INFO] [INFO] > ------------------------------------------------------------------------ > [INFO] [INFO] BUILD FAILURE > [INFO] [INFO] > ------------------------------------------------------------------------ > [INFO] [INFO] Total time: 30.126 s > [INFO] [INFO] Finished at: 2015-07-14T16:05:57-07:00 > [INFO] [INFO] Final Memory: 91M/1377M > [INFO] [INFO] > ------------------------------------------------------------------------ > [INFO] [ERROR] Failed to execute goal > org.apache.maven.plugins:maven-deploy-plugin:2.6:deploy (default-deploy) on > project google-container-registry-auth: Failed to deploy artifacts: Could not > transfer artifact > org.jenkins-ci.plugins:google-container-registry-auth:hpi:0.2 from/to > maven.jenkins-ci.org > (http://maven.jenkins-ci.org:8081/content/repositories/releases): Failed to > transfer file: > http://maven.jenkins-ci.org:8081/content/repositories/releases/org/jenkins-ci/plugins/google-container-registry-auth/0.2/google-container-registry-auth-0.2.hpi. > Return code is: 401, ReasonPhrase: Unauthorized. -> [Help 1] > [INFO] [ERROR] > [INFO] [ERROR] To see the full stack trace of the errors, re-run Maven with > the -e switch. > [INFO] [ERROR] Re-run Maven using the -X switch to enable full debug logging. > [INFO] [ERROR] > [INFO] [ERROR] For more information about the errors and possible solutions, > please read the following articles: > [INFO] [ERROR] [Help 1] > http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException > [INFO] > ------------------------------------------------------------------------ > [INFO] BUILD FAILURE > [INFO] > ------------------------------------------------------------------------ > > > > -- > You received this message because you are subscribed to the Google Groups > "Jenkins Developers" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/jenkinsci-dev/CA%2BnSbNu5XzQQgWe1mc51BJ9pVCGJTnrbSyVitURtdVUS_oafZg%40mail.gmail.com. > For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/8C6BD669-2F05-44D4-B0BB-6C3DF5022D96%40beckweb.net. For more options, visit https://groups.google.com/d/optout.
