Made the changes and committed. command used: mvn release:prepare release:perform still the same issue: "401 unauthorized"
regards, On Sat, Jan 14, 2017 at 12:08 AM, Irfan Sayed <[email protected]> wrote: > Ok. thanks. > Let me remove below line and commit. > <hpi-plugin.version>1.106</hpi-plugin.version> > > so you mean, the curent scm section look OK? > should i mention any username and password in the settings.xml? > is mvn release:prepare release:perform command is enough? > > regards, > > > > > On Fri, Jan 13, 2017 at 11:57 PM, Slide <[email protected]> wrote: > >> You shouldn't need to specify an hpi plugin version at all, it will be >> handled in the parent pom. When I click on the repo you have in your >> previous email it takes me to a different name. >> >> On Fri, Jan 13, 2017, 10:52 Irfan Sayed <[email protected]> wrote: >> >>> Thanks Slide. >>> Can you please tell me what should be the hpi plugin version in POM.xml? >>> i will make necessary change and commit. >>> further, git scm info is the same which i kept when i released the >>> initial version. can you please tell me then what should be the correct >>> link? >>> >>> please let me know >>> Regards, >>> >>> >>> On Fri, Jan 13, 2017 at 11:16 PM, Slide <[email protected]> wrote: >>> >>> One question, why are you overriding the hpi plugin version? >>> https://github.com/jenkinsci/sinatra-chef-builder-plugin/blo >>> b/master/pom.xml#L15 >>> >>> Also, it looks like the git scm info in the pom.xml is for an old repo >>> link? >>> >>> On Fri, Jan 13, 2017 at 9:29 AM Irfan Sayed <[email protected]> >>> wrote: >>> >>> Sure Thanks >>> Let me explain: >>> >>> My current development environment: >>> 1: windows box >>> 2: eclipse MARs release >>> 3: java 1.8 >>> 4: maven version: 3.3.9 >>> 5: fixed all the findbugs issues >>> >>> plugin details: >>> Chef sinatra jenkins plugin: >>> current version: 1.3 >>> >>> Release process: >>> this is the first time i am uploading the new version of my plugin >>> Installed git bash >>> my github account and jenkins account is same >>> created the public/private key pair >>> uploaded the public key to the github. >>> settings.xml is taken from the link: https://wiki.jenkins-ci. >>> org/display/JENKINS/Plugin+tutorial >>> >>> troubleshooting steps i did: >>> i followed most instruction in the URL: https://wiki.jenkins-ci.org/di >>> splay/JENKINS/Hosting+Plugins >>> >>> 1: hard-coded username and password in the settings section in >>> settings.xml >>> 2: pass the username/password in the mvn release command >>> 3: able to push the latest changes in the github without asking for >>> password >>> 4: run the command mvn help:effective-settings to get the effective >>> settings to check the distributionManagement tag. it seems OK >>> 5: my plugin POM is updated with Jenkins parent plugin POM : >>> https://github.com/jenkinsci/plugin-pom >>> 6: effective POM is also seems OK >>> 7:get the encrypted password from the repo.jenkins-ci.org and paste in >>> the settings.xml instead of plain text password. >>> 8: created the PR request for the review >>> 9: followed the instruction in the : https://github.com/jenkins-i >>> nfra/repository-permissions-updater >>> >>> actual commands : >>> git clone https://github.com/jenkinsci/sinatra-chef-builder-plugin.git >>> git add pom.xml src >>> git commit -m "new version" >>> git push origin master >>> >>> final release command: >>> mvn release:prepare release:perform >>> >>> i am getting "401 unauthorized error" >>> please suggest >>> >>> Regards, >>> >>> >>> >>> >>> >>> >>> On Fri, Jan 13, 2017 at 9:16 PM, Slide <[email protected]> wrote: >>> >>> This is a pretty long thread, would it be possible for you to sum up >>> where you are currently stuck, what you have tried and so forth? >>> >>> On Fri, Jan 13, 2017 at 8:19 AM Irfan Sayed <[email protected]> >>> wrote: >>> >>> hi, >>> can someone please help. >>> I am stuck totally. >>> >>> regards, >>> >>> >>> On Fri, Jan 13, 2017 at 3:15 PM, Irfan Sayed <[email protected]> >>> wrote: >>> >>> Further update: >>> I got the Encrypted password of my account and put it in the >>> settings.xml as well. >>> https://repo.jenkins-ci.org/webapp/#/profile >>> >>> here is the snippet from settings.xml: >>> >>> <servers> >>> <server> >>> <id>java.net-m2-repository</id> <!-- For parent 1.397 or newer; >>> before this use id java.net-m2-repository --> >>> <username>irfanjs</username> >>> <password>$encryptedpassword</password> >>> </server> >>> </servers> >>> >>> still it throws the unauthorized error. >>> can someone please provide me the access to release plugin ? >>> regards, >>> >>> >>> >>> >>> On Thu, Jan 12, 2017 at 11:25 PM, Irfan Sayed <[email protected]> >>> wrote: >>> >>> As i am troubleshooting further, just wanted to confirm, if my ID : >>> "irfanjs" has valid deploy artifact/release plugin permission to jenkins-ci >>> org? >>> Hi Baptiste/Daniel, >>> Can i Request you to please have a look on the same. >>> >>> Regards, >>> >>> >>> On Thu, Jan 12, 2017 at 11:15 PM, Irfan Sayed <[email protected]> >>> wrote: >>> >>> further update: >>> i started ssh-agent and imported the private key of the github account. >>> my github account and jenkins-ci account is same. >>> aftrer that, added username and password in the ~/.m2/settings.xml file >>> and run the command: >>> "mvn release:prepare release:perform" >>> >>> still the same issue : "401 unauthorized" >>> >>> Regards, >>> >>> >>> On Thu, Jan 12, 2017 at 6:47 PM, Irfan Sayed <[email protected]> >>> wrote: >>> >>> Hi, >>> Please suggest... >>> i tried passing username and password as well in the maven release >>> command but no luck >>> >>> Regards, >>> >>> >>> On Thu, Jan 12, 2017 at 12:47 PM, Irfan Sayed <[email protected]> >>> wrote: >>> >>> Hi, >>> I have created the PR request : >>> https://github.com/irfanjs/chefbuilder/pull/1 >>> >>> Can you please review the same ? >>> i made changes directly into master branch. so i guess no need to merge >>> anything. >>> >>> I understand that i dont have plugin release upload permission. >>> >>> i followed the below link: >>> https://github.com/jenkins-infra/repository-permissions-updater >>> >>> and verified that YAML file exist for my plugin with correct content. >>> please let me know if i need to request anything more so that i can >>> upload new release >>> >>> Regards, >>> >>> >>> On Wed, Jan 11, 2017 at 8:56 AM, Irfan Sayed <[email protected]> >>> wrote: >>> >>> Thanks. >>> Let me thoroughly have a look and update >>> >>> Regards, >>> >>> >>> On Wed, Jan 11, 2017 at 10:07 PM, Daniel Beck <[email protected]> wrote: >>> >>> >>> > On 11.01.2017, at 17:34, Irfan Sayed <[email protected]> wrote: >>> > >>> > not getting why "unauthorized" error is coming >>> >>> Have you looked into all of the suggestions in the 12th note at >>> https://wiki.jenkins-ci.org/display/JENKINS/Hosting+Plugins# >>> HostingPlugins-Workingaroundcommonissues ? >>> >>> -- >>> 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/ms >>> gid/jenkinsci-dev/7956E78F-980D-44AE-BDCF-D3509E827702%40beckweb.net. >>> 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/ms >>> gid/jenkinsci-dev/CACGLCJb-iR9LRoDpCGcwACSakU-MMkOrX5QpQGpe- >>> 9uUkAQBpQ%40mail.gmail.com >>> <https://groups.google.com/d/msgid/jenkinsci-dev/CACGLCJb-iR9LRoDpCGcwACSakU-MMkOrX5QpQGpe-9uUkAQBpQ%40mail.gmail.com?utm_medium=email&utm_source=footer> >>> . >>> 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/ms >>> gid/jenkinsci-dev/CAPiUgVf5NzjAnMDxVgwFRSxrqn8oTtcxTiLMhcr5r >>> XfEzLtnNQ%40mail.gmail.com >>> <https://groups.google.com/d/msgid/jenkinsci-dev/CAPiUgVf5NzjAnMDxVgwFRSxrqn8oTtcxTiLMhcr5rXfEzLtnNQ%40mail.gmail.com?utm_medium=email&utm_source=footer> >>> . >>> >>> >>> 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/ms >>> gid/jenkinsci-dev/CACGLCJbbu1TS5%2B-ZGMWFJTu5N_TzOx1S% >>> 3DwMa46%2B%2B9USFMYAXfg%40mail.gmail.com >>> <https://groups.google.com/d/msgid/jenkinsci-dev/CACGLCJbbu1TS5%2B-ZGMWFJTu5N_TzOx1S%3DwMa46%2B%2B9USFMYAXfg%40mail.gmail.com?utm_medium=email&utm_source=footer> >>> . >>> 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/ms >>> gid/jenkinsci-dev/CAPiUgVfMDLYiswKyP%3D9yHuQLHts9Cn%2B5AbgFJ >>> wuiOJUxq0YvBg%40mail.gmail.com >>> <https://groups.google.com/d/msgid/jenkinsci-dev/CAPiUgVfMDLYiswKyP%3D9yHuQLHts9Cn%2B5AbgFJwuiOJUxq0YvBg%40mail.gmail.com?utm_medium=email&utm_source=footer> >>> . >>> >>> >>> 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/ms >>> gid/jenkinsci-dev/CACGLCJYr4kxHR%3De5Z%2B36UMZ1BDf3%2Bw%3DPg >>> ZWhocg5VfWH%3DgGk1w%40mail.gmail.com >>> <https://groups.google.com/d/msgid/jenkinsci-dev/CACGLCJYr4kxHR%3De5Z%2B36UMZ1BDf3%2Bw%3DPgZWhocg5VfWH%3DgGk1w%40mail.gmail.com?utm_medium=email&utm_source=footer> >>> . >>> 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/ms >> gid/jenkinsci-dev/CAPiUgVfyKti_dOOdyDsAAH%3D6ZbAJV1PN_ >> WpSoEsn4DtKLLiawA%40mail.gmail.com >> <https://groups.google.com/d/msgid/jenkinsci-dev/CAPiUgVfyKti_dOOdyDsAAH%3D6ZbAJV1PN_WpSoEsn4DtKLLiawA%40mail.gmail.com?utm_medium=email&utm_source=footer> >> . >> >> 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/CACGLCJb8f%3D54-TMTUuBn4g5sYvu1CovnoAkvA0EAeDsMqFeFew%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
