access for violations-plugin
Locked
access for violations-plugin
 
|
Hi all,
My yearly attempt to update the violations plugin has come. I have updated my github account and checked my jenkins account. I can pull and push to the github repository and can build the plugin (after switching back to jdk6). However, I am unable to release using: mvn release:prepare release:perform and mvn release:prepare release:perform -Dusername=peterkittreilly -Dpassword=<current one> I get Failed to deploy artifacts: Could not transfer artifact org.jenkins-ci.plugins:violations:hpi:0.7.12 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/violations/0.7.12/violations-0.7.12.hpi. Return code is: 401, ReasonPhrase:Unauthorized Could someone with good karma have a look please? Peter |
Re: access for violations-plugin
|
Hi, * use ssh (I tried releasing using https many times without much luck) Then you should be able to release without specifying any user or passwd parameter. Note that I'm not pretending https and having non aligned account doesn't work. It's just simpler to use the mainstream recommended configuration. And it actually worked fine for me. Hth. Le 10 oct. 2012 17:09, "Peter Reilly" <[hidden email]> a écrit :
Hi all, |
Re: access for violations-plugin
|
In reply to this post by Peter Reilly-2
Peter if you are still stuck give me a note and we can do a book swap, coffee, and fix your maven ;-)
On Wednesday, 10 October 2012, Peter Reilly wrote: Hi all, |
Re: access for violations-plugin
|
|
In reply to this post by Baptiste MATHUS-2
I have aligned the keys and passwords - but no luck.
Peter On Wed, Oct 10, 2012 at 5:13 PM, Baptiste Mathus <[hidden email]> wrote: > Hi, > Having gone through our plugin release recently, I would advise the > following: > > * use ssh (I tried releasing using https many times without much luck) > * update your confluence and "aligned" JIRA account to use the same id and > password as on github) > * register if not done yet your ssh pub key on both github and > jenkins-ci.org account. > > Then you should be able to release without specifying any user or passwd > parameter. > > Note that I'm not pretending https and having non aligned account doesn't > work. It's just simpler to use the mainstream recommended configuration. And > it actually worked fine for me. > > Hth. > Cheers > > Le 10 oct. 2012 17:09, "Peter Reilly" <[hidden email]> a écrit > : > >> Hi all, >> >> My yearly attempt to update the violations plugin has come. >> >> I have updated my github account and checked my jenkins account. >> >> I can pull and push to the github repository and can build the plugin >> (after switching back to jdk6). >> >> However, I am unable to release using: >> mvn release:prepare release:perform >> and >> mvn release:prepare release:perform -Dusername=peterkittreilly >> -Dpassword=<current one> >> >> >> I get >> >> Failed to deploy artifacts: Could not transfer artifact >> org.jenkins-ci.plugins:violations:hpi:0.7.12 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/violations/0.7.12/violations-0.7.12.hpi. >> Return code is: 401, ReasonPhrase:Unauthorized >> >> >> Could someone with good karma have a look please? >> >> Peter |
Re: access for violations-plugin
|
|
In reply to this post by stephenconnolly
Not in town any more (sad face).
I have the peterkittreilly user name at jenkins and at github and am using the same user key. I clone using git clone [hidden email]:jenkinsci/violations-plugin.git and am able to push commits. mvn release:prepare release:perform compiles and is able to upload to http://maven.jenkins-ci.org:8081/content/repositories/releases/org/jenkins-ci/plugins/violations/0.7.14/violations-0.7.14.hpi But then fails with: INFO] [INFO] Uploading: http://maven.jenkins-ci.org:8081/content/repositories/releases/org/jenkins-ci/plugins/violations/0.7.14/violations-0.7.14.pom [INFO] 2/4 KB [INFO] 4/4 KB [INFO] [INFO] [INFO] ------------------------------------------------------------------------ [INFO] [INFO] BUILD FAILURE [INFO] [INFO] ------------------------------------------------------------------------ [INFO] [INFO] Total time: 53.036s [INFO] [INFO] Finished at: Fri Oct 12 15:11:15 IST 2012 [INFO] [INFO] Final Memory: 39M/506M [INFO] [INFO] ------------------------------------------------------------------------ [INFO] [ERROR] Failed to execute goal org.apache.maven.plugins:maven-deploy-plugin:2.5:deploy (default-deploy) on project violations: Failed to deploy artifacts: Could not transfer artifact org.jenkins-ci.plugins:violations:hpi:0.7.14 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/violations/0.7.14/violations-0.7.14.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] My unix user name is 'peter' - would this make a difference? My .m2/settings.xml is: <settings> <pluginGroups> <pluginGroup>org.jenkins-ci.tools</pluginGroup> </pluginGroups> <profiles> <!-- Give access to Jenkins plugins --> <profile> <id>jenkins</id> <activation> <activeByDefault>true</activeByDefault> <!-- change this to false, if you don't like to have it on per default --> </activation> <repositories> <repository> <id>repo.jenkins-ci.org</id> <url>http://repo.jenkins-ci.org/public/</url> </repository> </repositories> <pluginRepositories> <pluginRepository> <id>repo.jenkins-ci.org</id> <url>http://repo.jenkins-ci.org/public/</url> </pluginRepository> </pluginRepositories> </profile> </profiles> </settings> .i.e. a cargo cult copy of the settings in the jenkins plugin page. Peter On Wed, Oct 10, 2012 at 6:07 PM, Stephen Connolly <[hidden email]> wrote: > Peter if you are still stuck give me a note and we can do a book swap, > coffee, and fix your maven ;-) > > > On Wednesday, 10 October 2012, Peter Reilly wrote: >> >> Hi all, >> >> My yearly attempt to update the violations plugin has come. >> >> I have updated my github account and checked my jenkins account. >> >> I can pull and push to the github repository and can build the plugin >> (after switching back to jdk6). >> >> However, I am unable to release using: >> mvn release:prepare release:perform >> and >> mvn release:prepare release:perform -Dusername=peterkittreilly >> -Dpassword=<current one> >> >> >> I get >> >> Failed to deploy artifacts: Could not transfer artifact >> org.jenkins-ci.plugins:violations:hpi:0.7.12 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/violations/0.7.12/violations-0.7.12.hpi. >> Return code is: 401, ReasonPhrase:Unauthorized >> >> >> Could someone with good karma have a look please? >> >> Peter |
Re: access for violations-plugin
|
Did you specify user and password in the settings.xml file?
Ulli Am 12.10.2012 um 16:22 schrieb Peter Reilly <[hidden email]>: > Not in town any more (sad face). > > > I have the peterkittreilly user name at jenkins and at github and am using > the same user key. > > I clone using > git clone [hidden email]:jenkinsci/violations-plugin.git > > and am able to push commits. > > mvn release:prepare release:perform > > compiles and is able to upload to > http://maven.jenkins-ci.org:8081/content/repositories/releases/org/jenkins-ci/plugins/violations/0.7.14/violations-0.7.14.hpi > > > But then fails with: > INFO] > [INFO] Uploading: > http://maven.jenkins-ci.org:8081/content/repositories/releases/org/jenkins-ci/plugins/violations/0.7.14/violations-0.7.14.pom > [INFO] 2/4 KB > [INFO] 4/4 KB > [INFO] > [INFO] [INFO] ------------------------------------------------------------------------ > [INFO] [INFO] BUILD FAILURE > [INFO] [INFO] ------------------------------------------------------------------------ > [INFO] [INFO] Total time: 53.036s > [INFO] [INFO] Finished at: Fri Oct 12 15:11:15 IST 2012 > [INFO] [INFO] Final Memory: 39M/506M > [INFO] [INFO] ------------------------------------------------------------------------ > [INFO] [ERROR] Failed to execute goal > org.apache.maven.plugins:maven-deploy-plugin:2.5:deploy > (default-deploy) on project violations: Failed to deploy artifacts: > Could not transfer artifact > org.jenkins-ci.plugins:violations:hpi:0.7.14 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/violations/0.7.14/violations-0.7.14.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] > > > My unix user name is 'peter' - would this make a difference? > > My .m2/settings.xml is: > > <settings> > <pluginGroups> > <pluginGroup>org.jenkins-ci.tools</pluginGroup> > </pluginGroups> > > <profiles> > <!-- Give access to Jenkins plugins --> > <profile> > <id>jenkins</id> > <activation> > <activeByDefault>true</activeByDefault> <!-- change this to > false, if you don't like to have it on per default --> > </activation> > <repositories> > <repository> > <id>repo.jenkins-ci.org</id> > <url>http://repo.jenkins-ci.org/public/</url> > </repository> > </repositories> > <pluginRepositories> > <pluginRepository> > <id>repo.jenkins-ci.org</id> > <url>http://repo.jenkins-ci.org/public/</url> > </pluginRepository> > </pluginRepositories> > </profile> > </profiles> > </settings> > > .i.e. a cargo cult copy of the settings in the jenkins plugin page. > > Peter > > On Wed, Oct 10, 2012 at 6:07 PM, Stephen Connolly > <[hidden email]> wrote: >> Peter if you are still stuck give me a note and we can do a book swap, >> coffee, and fix your maven ;-) >> >> >> On Wednesday, 10 October 2012, Peter Reilly wrote: >>> >>> Hi all, >>> >>> My yearly attempt to update the violations plugin has come. >>> >>> I have updated my github account and checked my jenkins account. >>> >>> I can pull and push to the github repository and can build the plugin >>> (after switching back to jdk6). >>> >>> However, I am unable to release using: >>> mvn release:prepare release:perform >>> and >>> mvn release:prepare release:perform -Dusername=peterkittreilly >>> -Dpassword=<current one> >>> >>> >>> I get >>> >>> Failed to deploy artifacts: Could not transfer artifact >>> org.jenkins-ci.plugins:violations:hpi:0.7.12 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/violations/0.7.12/violations-0.7.12.hpi. >>> Return code is: 401, ReasonPhrase:Unauthorized >>> >>> >>> Could someone with good karma have a look please? >>> >>> Peter |
Re: access for violations-plugin
|
|
No,
Where is that set in the settings.xml file. Also, I would rather use the ssh public/private key instead of user names and passwords. Peter On Fri, Oct 12, 2012 at 3:56 PM, Ulli Hafner <[hidden email]> wrote: > Did you specify user and password in the settings.xml file? > > Ulli > > Am 12.10.2012 um 16:22 schrieb Peter Reilly <[hidden email]>: > >> Not in town any more (sad face). >> >> >> I have the peterkittreilly user name at jenkins and at github and am using >> the same user key. >> >> I clone using >> git clone [hidden email]:jenkinsci/violations-plugin.git >> >> and am able to push commits. >> >> mvn release:prepare release:perform >> >> compiles and is able to upload to >> http://maven.jenkins-ci.org:8081/content/repositories/releases/org/jenkins-ci/plugins/violations/0.7.14/violations-0.7.14.hpi >> >> >> But then fails with: >> INFO] >> [INFO] Uploading: >> http://maven.jenkins-ci.org:8081/content/repositories/releases/org/jenkins-ci/plugins/violations/0.7.14/violations-0.7.14.pom >> [INFO] 2/4 KB >> [INFO] 4/4 KB >> [INFO] >> [INFO] [INFO] ------------------------------------------------------------------------ >> [INFO] [INFO] BUILD FAILURE >> [INFO] [INFO] ------------------------------------------------------------------------ >> [INFO] [INFO] Total time: 53.036s >> [INFO] [INFO] Finished at: Fri Oct 12 15:11:15 IST 2012 >> [INFO] [INFO] Final Memory: 39M/506M >> [INFO] [INFO] ------------------------------------------------------------------------ >> [INFO] [ERROR] Failed to execute goal >> org.apache.maven.plugins:maven-deploy-plugin:2.5:deploy >> (default-deploy) on project violations: Failed to deploy artifacts: >> Could not transfer artifact >> org.jenkins-ci.plugins:violations:hpi:0.7.14 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/violations/0.7.14/violations-0.7.14.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] >> >> >> My unix user name is 'peter' - would this make a difference? >> >> My .m2/settings.xml is: >> >> <settings> >> <pluginGroups> >> <pluginGroup>org.jenkins-ci.tools</pluginGroup> >> </pluginGroups> >> >> <profiles> >> <!-- Give access to Jenkins plugins --> >> <profile> >> <id>jenkins</id> >> <activation> >> <activeByDefault>true</activeByDefault> <!-- change this to >> false, if you don't like to have it on per default --> >> </activation> >> <repositories> >> <repository> >> <id>repo.jenkins-ci.org</id> >> <url>http://repo.jenkins-ci.org/public/</url> >> </repository> >> </repositories> >> <pluginRepositories> >> <pluginRepository> >> <id>repo.jenkins-ci.org</id> >> <url>http://repo.jenkins-ci.org/public/</url> >> </pluginRepository> >> </pluginRepositories> >> </profile> >> </profiles> >> </settings> >> >> .i.e. a cargo cult copy of the settings in the jenkins plugin page. >> >> Peter >> >> On Wed, Oct 10, 2012 at 6:07 PM, Stephen Connolly >> <[hidden email]> wrote: >>> Peter if you are still stuck give me a note and we can do a book swap, >>> coffee, and fix your maven ;-) >>> >>> >>> On Wednesday, 10 October 2012, Peter Reilly wrote: >>>> >>>> Hi all, >>>> >>>> My yearly attempt to update the violations plugin has come. >>>> >>>> I have updated my github account and checked my jenkins account. >>>> >>>> I can pull and push to the github repository and can build the plugin >>>> (after switching back to jdk6). >>>> >>>> However, I am unable to release using: >>>> mvn release:prepare release:perform >>>> and >>>> mvn release:prepare release:perform -Dusername=peterkittreilly >>>> -Dpassword=<current one> >>>> >>>> >>>> I get >>>> >>>> Failed to deploy artifacts: Could not transfer artifact >>>> org.jenkins-ci.plugins:violations:hpi:0.7.12 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/violations/0.7.12/violations-0.7.12.hpi. >>>> Return code is: 401, ReasonPhrase:Unauthorized >>>> >>>> >>>> Could someone with good karma have a look please? >>>> >>>> Peter > |
Re: access for violations-plugin
|
See https://wiki.jenkins-ci.org/display/JENKINS/Hosting+Plugins#HostingPlugins-Releasingtojenkinsci.org for the <server> entry you need in ~/.m2/settings.xml. Unfortunately, this part of the deployment relies on HTTP PUT, and it doesn't support public key authentication. On 10/12/2012 08:17 AM, Peter Reilly wrote: > No, > > Where is that set in the settings.xml file. > Also, I would rather use the ssh public/private key instead of > user names and passwords. > > Peter > > > On Fri, Oct 12, 2012 at 3:56 PM, Ulli Hafner <[hidden email]> wrote: >> Did you specify user and password in the settings.xml file? >> >> Ulli >> >> Am 12.10.2012 um 16:22 schrieb Peter Reilly <[hidden email]>: >> >>> Not in town any more (sad face). >>> >>> >>> I have the peterkittreilly user name at jenkins and at github and am using >>> the same user key. >>> >>> I clone using >>> git clone [hidden email]:jenkinsci/violations-plugin.git >>> >>> and am able to push commits. >>> >>> mvn release:prepare release:perform >>> >>> compiles and is able to upload to >>> http://maven.jenkins-ci.org:8081/content/repositories/releases/org/jenkins-ci/plugins/violations/0.7.14/violations-0.7.14.hpi >>> >>> >>> But then fails with: >>> INFO] >>> [INFO] Uploading: >>> http://maven.jenkins-ci.org:8081/content/repositories/releases/org/jenkins-ci/plugins/violations/0.7.14/violations-0.7.14.pom >>> [INFO] 2/4 KB >>> [INFO] 4/4 KB >>> [INFO] >>> [INFO] [INFO] ------------------------------------------------------------------------ >>> [INFO] [INFO] BUILD FAILURE >>> [INFO] [INFO] ------------------------------------------------------------------------ >>> [INFO] [INFO] Total time: 53.036s >>> [INFO] [INFO] Finished at: Fri Oct 12 15:11:15 IST 2012 >>> [INFO] [INFO] Final Memory: 39M/506M >>> [INFO] [INFO] ------------------------------------------------------------------------ >>> [INFO] [ERROR] Failed to execute goal >>> org.apache.maven.plugins:maven-deploy-plugin:2.5:deploy >>> (default-deploy) on project violations: Failed to deploy artifacts: >>> Could not transfer artifact >>> org.jenkins-ci.plugins:violations:hpi:0.7.14 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/violations/0.7.14/violations-0.7.14.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] >>> >>> >>> My unix user name is 'peter' - would this make a difference? >>> >>> My .m2/settings.xml is: >>> >>> <settings> >>> <pluginGroups> >>> <pluginGroup>org.jenkins-ci.tools</pluginGroup> >>> </pluginGroups> >>> >>> <profiles> >>> <!-- Give access to Jenkins plugins --> >>> <profile> >>> <id>jenkins</id> >>> <activation> >>> <activeByDefault>true</activeByDefault> <!-- change this to >>> false, if you don't like to have it on per default --> >>> </activation> >>> <repositories> >>> <repository> >>> <id>repo.jenkins-ci.org</id> >>> <url>http://repo.jenkins-ci.org/public/</url> >>> </repository> >>> </repositories> >>> <pluginRepositories> >>> <pluginRepository> >>> <id>repo.jenkins-ci.org</id> >>> <url>http://repo.jenkins-ci.org/public/</url> >>> </pluginRepository> >>> </pluginRepositories> >>> </profile> >>> </profiles> >>> </settings> >>> >>> .i.e. a cargo cult copy of the settings in the jenkins plugin page. >>> >>> Peter >>> >>> On Wed, Oct 10, 2012 at 6:07 PM, Stephen Connolly >>> <[hidden email]> wrote: >>>> Peter if you are still stuck give me a note and we can do a book swap, >>>> coffee, and fix your maven ;-) >>>> >>>> >>>> On Wednesday, 10 October 2012, Peter Reilly wrote: >>>>> >>>>> Hi all, >>>>> >>>>> My yearly attempt to update the violations plugin has come. >>>>> >>>>> I have updated my github account and checked my jenkins account. >>>>> >>>>> I can pull and push to the github repository and can build the plugin >>>>> (after switching back to jdk6). >>>>> >>>>> However, I am unable to release using: >>>>> mvn release:prepare release:perform >>>>> and >>>>> mvn release:prepare release:perform -Dusername=peterkittreilly >>>>> -Dpassword=<current one> >>>>> >>>>> >>>>> I get >>>>> >>>>> Failed to deploy artifacts: Could not transfer artifact >>>>> org.jenkins-ci.plugins:violations:hpi:0.7.12 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/violations/0.7.12/violations-0.7.12.hpi. >>>>> Return code is: 401, ReasonPhrase:Unauthorized >>>>> >>>>> >>>>> Could someone with good karma have a look please? >>>>> >>>>> Peter >> > -- Kohsuke Kawaguchi | CloudBees, Inc. | http://cloudbees.com/ Try Nectar, our professional version of Jenkins |
«
Return to Jenkins dev
|
1 view|%1 views
Loading...
| Powered by Nabble | Edit this page |