Thank you Ullrich. I was using a wrong password. On Wednesday, September 24, 2014 2:34:35 AM UTC-7, Ullrich Hafner wrote: > > Did you use your Jenkins ID and password (credentials are different in > GitHub). > > Am 24.09.2014 um 01:40 schrieb Mohsen Vakilian <[email protected] > <javascript:>>: > > I do have push access to the github repo but not the jenkins-ci.org repo. > The command "mvn release:prepare release:perform" gives me the following > error message: > > [INFO] Uploading: > http://maven.jenkins-ci.org:8081/content/repositories/releases/org/jenkins-ci/plugins/google-storage-plugin/0.7/google-storage-plugin-0.7.pom > [INFO] [ERROR] Failed to execute goal > org.apache.maven.plugins:maven-deploy-plugin:2.6:deploy (default-deploy) on > project google-storage-plugin: Failed to deploy artifacts: Could not > transfer artifact org.jenkins-ci.plugins:google-storage-plugin:hpi:0.7 > 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-storage-plugin/0.7/google-storage-plugin-0.7.hpi. > > Return code is: 401, ReasonPhrase: Unauthorized. -> [Help 1] > > If the maintainers of google-storage-plugin can give me the permission to > publish the new version of the plugin to jenkins-ci.org, would you please > send me the instructions that they have to follow? > > On Tuesday, September 23, 2014 3:13:27 PM UTC-7, Christopher wrote: >> >> On 09/23/2014 10:57 PM, Mohsen Vakilian wrote: >> > Here are the information required for publishing plugins to >> > jenkins-ci.org as listed at >> > >> https://wiki.jenkins-ci.org/display/JENKINS/Hosting+Plugins#HostingPlugins-Requesthosting >> >> > >> > your GitHub plugin name=google-storage-plugin >> > your personal GitHub ID (to use GitHub)=reprogrammer >> > jenkins-ci.org account ID=reprogrammer >> > The existing GitHub repository to fork (if you have >> > one)=https://github.com/jenkinsci/google-storage-plugin >> >> Those wiki instructions are for publishing a *new* plugin. >> >> While I see you've already received access, committed to and published a >> new version of the plugin, the normal procedure for existing plugins is >> to send a pull request first, or speak with the maintainer. >> >> Regards, >> Chris >> >> > -- > 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] <javascript:>. > 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]. For more options, visit https://groups.google.com/d/optout.
