Re: Not able to release new version of plugin

Awesome !!! you are rock it has resolved. I am able to upload new version . BUILD got success Thanks all for all your tremendous support and co-operation Regards, On Mon, Jan 16, 2017 at 12:23 AM, Irfan Sayed wrote: > sorry. my mistake > i apologize. > i ran the command

Re: Not able to release new version of plugin

sorry. my mistake i apologize. i ran the command again. will give you result in few min regards, On Sun, Jan 15, 2017 at 10:40 AM, Daniel Beck wrote: > > > On 15.01.2017, at 19:08, Irfan Sayed wrote: > > > > I have just removed the ID in the

Re: Not able to release new version of plugin

On 15.01.2017 19:08, Irfan Sayed wrote: > No. still the issue. > I have just removed the ID in the distributionManagement from POM and Daniel wrote "CHANGE the IDs of distributionManagement as well.". He did NOT wrote REMOVE them. Of course they MUST exist AND equal in both files. Eg.: If the

Re: Not able to release new version of plugin

> On 15.01.2017, at 19:08, Irfan Sayed wrote: > > I have just removed the ID in the distributionManagement from POM WHY? WHY remove it altogether after being told to change it to the same value as something else? I give up. -- You received this message because you are

Re: Not able to release new version of plugin

PFA Regards, On Sun, Jan 15, 2017 at 10:33 AM, Daniel Beck wrote: > > > On 15.01.2017, at 19:08, Irfan Sayed wrote: > > > > still same unauthorized issue > > > > What's the effective POM now? > > -- > You received this message because you are

Re: Not able to release new version of plugin

> On 15.01.2017, at 19:08, Irfan Sayed wrote: > > still same unauthorized issue > What's the effective POM now? -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving

Re: Not able to release new version of plugin

No. still the issue. I have just removed the ID in the distributionManagement from POM and build again still same unauthorized issue regards, On Sun, Jan 15, 2017 at 11:24 PM, Daniel Beck wrote: > > > On 15.01.2017, at 18:34, Irfan Sayed wrote: > > > >

Re: Not able to release new version of plugin

> On 15.01.2017, at 18:34, Irfan Sayed wrote: > > Can you please quickly review and see any issue. > Change the IDs of distributionManagement as well. -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To

Re: Not able to release new version of plugin

Still no luck. same issue. I have attached effective POM and effective settings. Can you please quickly review and see any issue. Regards, On Sun, Jan 15, 2017 at 9:02 AM, Irfan Sayed wrote: > Ok. Thanks > Let me remove that entry and tray again > > Regards, > > > On

Re: Not able to release new version of plugin

Ok. Thanks Let me remove that entry and tray again Regards, On Sun, Jan 15, 2017 at 10:24 PM, Daniel Beck wrote: > > > On 15.01.2017, at 17:52, Irfan Sayed wrote: > > > > so what would be the correct ID ? > > java.net-m2-repository OR

Re: Not able to release new version of plugin

> On 15.01.2017, at 17:52, Irfan Sayed wrote: > > so what would be the correct ID ? > java.net-m2-repository OR repo.jenkins-ci.org ?? > Doesn't matter, just needs to match. FWIW recent parent POMs used maven.jenkins-ci.org, so you may be able to just remove that

Re: Not able to release new version of plugin

Thanks Daniel. so what would be the correct ID ? java.net-m2-repository OR repo.jenkins-ci.org ?? Regards On Sun, Jan 15, 2017 at 10:19 PM, Daniel Beck wrote: > The password is defined for the repo ID: java.net-m2-repository > The upload goes to the repo ID:

Re: Not able to release new version of plugin

The password is defined for the repo ID: java.net-m2-repository The upload goes to the repo ID: repo.jenkins-ci.org Am I missing something here? Isn't this the problem? > On 15.01.2017, at 10:05, Irfan Sayed wrote: > > http://maven.apache.org/SETTINGS/1.1.0;> > >

Re: Not able to release new version of plugin

Hi, Please suggest if what can be done . i verified again all troubleshooting step but all seems OK. Regards, On Sun, Jan 15, 2017 at 2:35 PM, Irfan Sayed wrote: > Thanks Christopher. > howver, i tried plaintext and encrypted password as well but still no luck > i

Re: Not able to release new version of plugin

Thanks Christopher. howver, i tried plaintext and encrypted password as well but still no luck i enabled the debug mode but still it does not have any specific hint/clue here is the effective settings [INFO] Scanning for projects... [WARNING] The POM for

Re: Not able to release new version of plugin

The pom.xml has http instead of https for the Jenkins maven repos. On Sat, Jan 14, 2017, 18:50 Daniel Beck wrote: > > > On 14.01.2017, at 18:39, Christopher Orr wrote: > > > > Since last month, no special permissions are needed to upload SNAPSHOTs: > > >

Re: Not able to release new version of plugin

> On 14.01.2017, at 18:39, Christopher Orr wrote: > > Since last month, no special permissions are needed to upload SNAPSHOTs: > https://groups.google.com/d/msgid/jenkinsci-dev/53CC6ED4-3BBC-4FAD-A197-10AD7F922A34%40beckweb.net > > The permissions look correct here, and match

Re: Not able to release new version of plugin

Since last month, no special permissions are needed to upload SNAPSHOTs: https://groups.google.com/d/msgid/jenkinsci-dev/53CC6ED4-3BBC-4FAD-A197-10AD7F922A34%40beckweb.net The permissions look correct here, and match the groupId and artifactId from your logs, plus you said that you've logged

Re: Not able to release new version of plugin

One thing to try would be to add another user to the upload permissions app and see if they can do a snapshot release. On Sat, Jan 14, 2017, 09:37 Irfan Sayed wrote: > Thanks Slide. > anyone has any other suggestions/workaround ? > if this is not resolved, how will i be

Re: Not able to release new version of plugin

I've been wondering the same thing but I am not sure. I wonder if there is any sort of log on the server that someone with those privileges could look at. I'm out of ideas sadly. On Sat, Jan 14, 2017, 07:09 Irfan Sayed wrote: > When i requested initially for hosting plugin

Re: Not able to release new version of plugin

If your version has SNAPSHOT in it, you don't need to add anything. Snapshots are automatically deployed to the correct place I believe. On Sat, Jan 14, 2017, 05:52 Irfan Sayed wrote: > OK. i made the POM changes in my plugin and added following: > > >propSnap

Re: Not able to release new version of plugin

Also, quick tip: you can stop trying to release, but only do "mvn deploy" to see if you can deploy snapshots, because this is the thing that is failing for you. Github pushes seem to work, only artifacts have an in issue IIUC. Le 14 janv. 2017 9:59 AM, "Irfan Sayed" a écrit

Re: Not able to release new version of plugin

Oh, I missed your message about the typo before I hit send. Are you able to login to https://accounts.jenkins.io/login?from=%2Fmyself%2F with the username/password combo that you have in your settings.xml? On Fri, Jan 13, 2017, 15:17 Slide wrote: > From the same console,

Re: Not able to release new version of plugin

>From the same console, can you do something like this: https://help.github.com/articles/testing-your-ssh-connection/ On Fri, Jan 13, 2017 at 12:55 PM Irfan Sayed wrote: made the scm section changes and committed. here is the build output log: ef-builder --- [INFO]

Re: Not able to release new version of plugin

Well, the SCM section doesn't match with the repo url: https://github.com/jenkinsci/sinatra-chef-builder-plugin is the repo URL, but the scm section has scm:git:git://github.com/jenkinsci/chefbuilder-plugin.git scm:git:ssh:// g...@github.com/jenkinsci/chefbuilder-plugin.git

Re: Not able to release new version of plugin

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 wrote: > Ok. thanks. > Let me remove below line and commit. > 1.106 > > so you mean, the

Re: Not able to release new version of plugin

Ok. thanks. Let me remove below line and commit. 1.106 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

Re: Not able to release new version of plugin

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 wrote: > Thanks Slide. > Can you please tell

Re: Not able to release new version of plugin

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

Re: Not able to release new version of plugin

One question, why are you overriding the hpi plugin version? https://github.com/jenkinsci/sinatra-chef-builder-plugin/blob/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 wrote: >

Re: Not able to release new version of plugin

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

Re: Not able to release new version of plugin

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 wrote: > hi, > can someone please help. > I am stuck totally. > > regards, > > > On Fri, Jan

Re: Not able to release new version of plugin

hi, can someone please help. I am stuck totally. regards, On Fri, Jan 13, 2017 at 3:15 PM, Irfan Sayed 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

Re: Not able to release new version of plugin

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: java.net-m2-repository irfanjs $encryptedpassword still it throws the

Re: Not able to release new version of plugin

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

Re: Not able to release new version of plugin

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

Re: Not able to release new version of plugin

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 wrote: > Hi, > I have created the PR request : > https://github.com/irfanjs/chefbuilder/pull/1 > > Can you

Re: Not able to release new version of plugin

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:

Re: Not able to release new version of plugin

> On 11.01.2017, at 17:34, Irfan Sayed 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 ? --

Re: Not able to release new version of plugin

Hi Baptiste, Can you please suggest ? i am able to push the changes using my username and using pass-wordless authentication not getting why "unauthorized" error is coming. i verified settings.xml as well regards, On Wed, Jan 11, 2017 at 5:14 PM, Irfan Sayed wrote: > Hi,

Re: Not able to release new version of plugin

Hi, The issue of having wrong URL in the maven release preparation is now resolved. i am getting correct URL. however, now "401 unauthorized" error is coming i have uploaded correct public key in the github and able to push the code properly. do i need to do any another setting to get rid of

Re: Not able to release new version of plugin

Thanks Baptiste. I have created public gist and uploaded all data there. https://gist.github.com/irfanjs/1e0315588d1e55dbbd28cc415fc4d157 please have a look. Regards, irfan On Mon, Jan 9, 2017 at 11:28 AM, Baptiste Mathus wrote: > You're not helpable this way. Please

Re: Not able to release new version of plugin

You're not helpable this way. Please describe what you did, and put the necessary data in gist.github.com or something. Like the error you're having. Is this really still the same error? You probably have something wrong locally or so you didn't push, because right now your pom.xml seems correct.

Re: Not able to release new version of plugin

Hi Baptiste, Can you please help Regards, Irfan On Mon, Jan 9, 2017 at 12:08 PM, Irfan Sayed wrote: > Hi Baptiste, > I tried creating settings.xml and try to perform the release. still the > issue persist. > Effective POM also looks OK. > > > >

Re: Not able to release new version of plugin

Hi Baptiste, I tried creating settings.xml and try to perform the release. still the issue persist. Effective POM also looks OK. maven.jenkins-ci.org https://repo.jenkins-ci.org/releases/ maven.jenkins-ci.org https://repo.jenkins-ci.org/snapshots/

Re: Not able to release new version of plugin

Sorry. while experimenting, that modification left as it is. i fixed that and uploaded new version. please have a look further , please find the attached settings.xml as well Regards, On Sun, Jan 8, 2017 at 2:44 AM, Baptiste Mathus wrote: > Your current pom.xml is not even

Re: Not able to release new version of plugin

Your current pom.xml is not even valid from a Maven PoV. You commented out the artifactId for one. So I don't know what you're testing right now, but no, this is not what is on your repo because that immediately

Re: Not able to release new version of plugin

Thanks. Yes. I did remove the DistributionManagement from my POM. Please refer here actual code. This is the latest code which i would like to release https://github.com/jenkinsci/sinatra-chef-builder-plugin Regards, On Fri, Jan 6, 2017 at 9:27 PM, Baptiste Mathus wrote: >

Re: Not able to release new version of plugin

Can you create a branch or a PR against your repo so that we check actual code/thing? Also, did you *remove* the distributionManagement part from your pom as I said? 2017-01-06 15:08 GMT+01:00 Irfan Sayed : > I changed the version from 2.3 to 2.5 , but still it refers to

Re: Not able to release new version of plugin

I changed the version from 2.3 to 2.5 , but still it refers to old repo. then i again changed to more updated version of plugin POM : 2.11 , still the same issue... in the effective POM, there is no entry with 8081 port i have checked the .m2/settings.xml file as well, there is also not any old

Re: Not able to release new version of plugin

> On 06.01.2017, at 14:26, Irfan Sayed wrote: > > 2.3 > The first response you got linked to: https://wiki.jenkins-ci.org/display/JENKINS/Hosting+Plugins#HostingPlugins-Workingaroundcommonissues And it says: > … or update to the parent plugins POM 2.5 or newer

Re: Not able to release new version of plugin

Sorry. actually i was confused. i red again and i guess i have to make following changes and did that. I made these changes in my plugin POM org.jenkins-ci.plugins plugin 2.3 1.609.1 1.106 is this seems correct now? but in the Plugin.POM file , i got following

Re: Not able to release new version of plugin

Irfan, seems like my mail went through looking at the archive. So please read it, and click on the link... We are spending time trying to help, so please at least read the link we provide. Thank you 2017-01-06 11:55 GMT+01:00 Irfan Sayed : > Thanks. > > any specific wiki

Re: Not able to release new version of plugin

Thanks. any specific wiki to refer how to upgrade the version of Parent POM to 2.x ? I have removed the DistributionManagement entry from my plugin POM. Regards, On Fri, Jan 6, 2017 at 12:38 AM, Oliver Gondža wrote: > On 2017-01-06 08:37, Irfan Sayed wrote: > >>

Re: Not able to release new version of plugin

On 2017-01-06 08:37, Irfan Sayed wrote: Thanks. In the effective POM, i have following: java.net-m2-repository http://maven.jenkins-ci.org/content/repositories/releases/ maven.jenkins-ci.org

Re: Not able to release new version of plugin

Upgrade to the 2.x version of the parent pom + remove the distributionManagement tag from your pom. https://github.com/jenkinsci/plugin-pom (Note : unrelated to upgrading to 2.x core baseline) Cheers Le 6 janv. 2017 8:37 AM, "Irfan Sayed" a écrit : > Thanks. > In the

Re: Not able to release new version of plugin

Thanks. In the effective POM, i have following: java.net-m2-repository http://maven.jenkins-ci.org/content/repositories/releases/ maven.jenkins-ci.org http://maven.jenkins-ci.org:8081/content/repositories/snapshots github-pages

Re: Not able to release new version of plugin

> On 05.01.2017, at 15:15, Irfan Sayed wrote: > > still the same error Unsurprising given that this still referenced the host name that has been shut down. -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To

Re: Not able to release new version of plugin

Thanks Daniel. i added following in plugin POM: java.net-m2-repository http://maven.jenkins-ci.org/content/repositories/releases/ still the same error. i am not getting from where it is picking up that url and port number. in my settings.xml as well this URL is not

Re: Not able to release new version of plugin

> On 05.01.2017, at 15:02, Irfan Sayed wrote: > > In my plugins POM, i have already this: What about distributionManagement? -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop

Re: Not able to release new version of plugin

Thanks Daniel. In my plugins POM, i have already this: repo.jenkins-ci.org http://repo.jenkins-ci.org/public/ repo.jenkins-ci.org http://repo.jenkins-ci.org/public/ is this not correct ? Regards, On Thu, Jan 5, 2017 at 5:57 AM, Daniel Beck

Re: Not able to release new version of plugin

> On 05.01.2017, at 14:49, Irfan Sayed wrote: > > it seems that URL : > http://maven.jenkins-ci.org:8081/content/repositories/releases is not working. > Can someone please suggest ? Second item at