subject:"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 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 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 subscribed to the Google Groups
>> "Jenkins Developers" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to jenkinsci-dev+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit https://groups.google.com/d/ms
>> gid/jenkinsci-dev/81A8BA14-0040-4589-96DE-06C8727C92D9%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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CACGLCJY%3DcD7K6Dsog02Rx5CfYSKDhZYmEWnfHP0VdHrOvf0W6A%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

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 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 subscribed to the Google Groups
> "Jenkins Developers" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/jenkinsci-dev/81A8BA14-0040-4589-96DE-06C8727C92D9%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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CACGLCJZJ42_ja78dOtNY1J_nnw8wcz9M7252_F5K33FcuMtrgQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Not able to release new version of plugin

2017-01-15 Thread Fritz Elfert

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 Id is "foo" in your pom.xml then in your settings.xml it
must me "foo" as well.

Please, at least TRY to understand how this works instead of blindly
trial/error:

If running the deploy, maven does the following:
 1. Looks for a server entry in the distributionManagement section
of the pom, reading the Id of that entry.
 2. Then, using THAT Id, it searches for a server record
with the SAME id in settings.xml in order to find the credentials

Therefore, of course if you REMOVE the Id in the pom.xml and/or
settings.xml, then maven has nothing to search for.
Sounds logical?

Hope this finally helps
 -Fritz

-- 
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/36de6908-f2f0-2faa-0b9a-c6361364d1ec%40fritz-elfert.de.
For more options, visit https://groups.google.com/d/optout.

signature.asc
Description: OpenPGP digital signature

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 subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/81A8BA14-0040-4589-96DE-06C8727C92D9%40beckweb.net.
For more options, visit https://groups.google.com/d/optout.

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 subscribed to the Google Groups
> "Jenkins Developers" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/jenkinsci-dev/F291309B-EEAD-4B76-9A84-0AE4D940A542%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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CACGLCJazGBBq6fhU_NphmzBaYJLTVR5-yu0a9y8vxgFVKr2rZg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
[INFO] Scanning for projects...
[WARNING] The POM for org.eclipse.m2e:lifecycle-mapping:jar:1.0.0 is missing, 
no dependency information available
[WARNING] Failed to retrieve plugin descriptor for 
org.eclipse.m2e:lifecycle-mapping:1.0.0: Plugin 
org.eclipse.m2e:lifecycle-mapping:1.0.0 or one of its dependencies could not be 
resolved: Failure to find org.eclipse.m2e:lifecycle-mapping:jar:1.0.0 in 
https://repo.jenkins-ci.org/public/ was cached in the local repository, 
resolution will not be reattempted until the update interval of 
repo.jenkins-ci.org has elapsed or updates are forced
[INFO] 
[INFO] 
[INFO] Building Chef Sinatra Jenkins plugin 1.14-SNAPSHOT
[INFO] 
[WARNING] The POM for org.eclipse.m2e:lifecycle-mapping:jar:1.0.0 is missing, 
no dependency information available
[WARNING] Failed to retrieve plugin descriptor for 
org.eclipse.m2e:lifecycle-mapping:1.0.0: Plugin 
org.eclipse.m2e:lifecycle-mapping:1.0.0 or one of its dependencies could not be 
resolved: Failure to find org.eclipse.m2e:lifecycle-mapping:jar:1.0.0 in 
https://repo.jenkins-ci.org/public/ was cached in the local repository, 
resolution will not be reattempted until the update interval of 
repo.jenkins-ci.org has elapsed or updates are forced
[INFO] 
[INFO] --- maven-help-plugin:2.2:effective-pom (default-cli) @ 
sinatra-chef-builder ---
[INFO] 
Effective POMs, after inheritance, interpolation, and profiles are applied:
















http://maven.apache.org/POM/4.0.0; 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance; 
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 
http://maven.apache.org/xsd/maven-4.0.0.xsd;>
  4.0.0
  
org.jenkins-ci.plugins
plugin
2.11

  
  org.jenkins-ci.plugins
  sinatra-chef-builder
  1.14-SNAPSHOT
  hpi
  Chef Sinatra Jenkins plugin
  Chef Sinatra Jenkins plugin
  
https://wiki.jenkins-ci.org/display/JENKINS/Chef+Sinatra+Jenkins+Plugin
  2016
  

  MIT License
  http://opensource.org/licenses/MIT

  
  

  irfanjs
  Irfan Sayed
  irfu.sa...@gmail.com

  
  

scm:git:git://github.com/jenkinsci/sinatra-chef-builder-plugin.git

scm:git:g...@github.com:jenkinsci/sinatra-chef-builder-plugin.git
sinatra-chef-builder-1.10
  
  

  https://repo.jenkins-ci.org/releases


  https://repo.jenkins-ci.org/snapshots

  
  


1C
true
1.0
git
1.117
8
8
2.11
1.609.1
1.9.2

true
/win-x64
win-x64/node.exe
4.0.0

2.13.1
UTF-8
UTF-8
UTF-8
true



1.7.7
1.17
4
  
  

  
com.google.code.findbugs
annotations
3.0.0
  
  
net.jcip
jcip-annotations
1.0
  
  
org.jenkins-ci.main
jenkins-core
1.609.1
  
  
org.jenkins-ci.main
jenkins-war
1.609.1
war-for-test
  
  
org.jenkins-ci.main
jenkins-war
1.609.1
war
test
  
  
org.jenkins-ci.main
jenkins-test-harness
2.11
  
  
org.jenkins-ci
test-annotations
1.2
  
  
junit
junit
4.12
  
  
javax.servlet
javax.servlet-api
3.1.0
  
  
javax.servlet
servlet-api
2.4
  
  
org.codehaus.mojo
animal-sniffer-annotations
1.14
  
  
org.codehaus.mojo.signature
java15
1.0
signature
  
  
org.codehaus.mojo.signature
java16

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 emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/F291309B-EEAD-4B76-9A84-0AE4D940A542%40beckweb.net.
For more options, visit https://groups.google.com/d/optout.

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:
> >
> > 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 unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/jenkinsci-dev/20C69A2F-2375-4171-B652-8DC9258CD474%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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CACGLCJarQFdojMvuZrvBzrcZetfRjEETo%2B5r3EYL82ZgeTOMTQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

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 unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/20C69A2F-2375-4171-B652-8DC9258CD474%40beckweb.net.
For more options, visit https://groups.google.com/d/optout.

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 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 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 entry from the pom.xml if I'm correct about this:
>>
>> https://github.com/jenkinsci/plugin-pom/blob/afe60afe46f2466
>> d8d7efc4829e0887cc17e146b/pom.xml#L757
>>
>>
>> --
>> 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 jenkinsci-dev+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit https://groups.google.com/d/ms
>> gid/jenkinsci-dev/B439BE30-8B80-4F54-87EF-5B9F6F1F19D2%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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CACGLCJY-EWdGXX38sYxk7D2AwQHUPRb6N_kQkwh0mh4zcnhHiQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
[INFO] Scanning for projects...
[WARNING] The POM for org.eclipse.m2e:lifecycle-mapping:jar:1.0.0 is missing, 
no dependency information available
[WARNING] Failed to retrieve plugin descriptor for 
org.eclipse.m2e:lifecycle-mapping:1.0.0: Plugin 
org.eclipse.m2e:lifecycle-mapping:1.0.0 or one of its dependencies could not be 
resolved: Failure to find org.eclipse.m2e:lifecycle-mapping:jar:1.0.0 in 
https://repo.jenkins-ci.org/public/ was cached in the local repository, 
resolution will not be reattempted until the update interval of 
repo.jenkins-ci.org has elapsed or updates are forced
[INFO] 
[INFO] 
[INFO] Building Chef Sinatra Jenkins plugin 1.13-SNAPSHOT
[INFO] 
[WARNING] The POM for org.eclipse.m2e:lifecycle-mapping:jar:1.0.0 is missing, 
no dependency information available
[WARNING] Failed to retrieve plugin descriptor for 
org.eclipse.m2e:lifecycle-mapping:1.0.0: Plugin 
org.eclipse.m2e:lifecycle-mapping:1.0.0 or one of its dependencies could not be 
resolved: Failure to find org.eclipse.m2e:lifecycle-mapping:jar:1.0.0 in 
https://repo.jenkins-ci.org/public/ was cached in the local repository, 
resolution will not be reattempted until the update interval of 
repo.jenkins-ci.org has elapsed or updates are forced
[INFO] 
[INFO] --- maven-help-plugin:2.2:effective-pom (default-cli) @ 
sinatra-chef-builder ---
[INFO] 
Effective POMs, after inheritance, interpolation, and profiles are applied:
















http://maven.apache.org/POM/4.0.0; 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance; 
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 
http://maven.apache.org/xsd/maven-4.0.0.xsd;>
  4.0.0
  
org.jenkins-ci.plugins
plugin
2.11

  
  org.jenkins-ci.plugins
  sinatra-chef-builder
  1.13-SNAPSHOT
  hpi
  Chef Sinatra Jenkins plugin
  Chef Sinatra Jenkins plugin
  
https://wiki.jenkins-ci.org/display/JENKINS/Chef+Sinatra+Jenkins+Plugin
  2016
  

  MIT License
  http://opensource.org/licenses/MIT

  
  

  irfanjs
  Irfan Sayed
  irfu.sa...@gmail.com

  
  

scm:git:git://github.com/jenkinsci/sinatra-chef-builder-plugin.git

scm:git:g...@github.com:jenkinsci/sinatra-chef-builder-plugin.git
sinatra-chef-builder-1.10
  
  

  propRel
  https://repo.jenkins-ci.org/releases


  propSnap
  https://repo.jenkins-ci.org/snapshots

  
  


1C
true
1.0
git
1.117
8
8
2.11
1.609.1
1.9.2

true
/win-x64
win-x64/node.exe
4.0.0

2.13.1
UTF-8
UTF-8
UTF-8
true



1.7.7
1.17
4
  
  

  
com.google.code.findbugs
annotations
3.0.0
  
  
net.jcip
jcip-annotations
1.0
  
  
org.jenkins-ci.main
jenkins-core
1.609.1
  
  
org.jenkins-ci.main
jenkins-war
1.609.1
war-for-test
  
  
org.jenkins-ci.main

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 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 entry from the pom.xml if I'm correct about this:
>
> https://github.com/jenkinsci/plugin-pom/blob/
> afe60afe46f2466d8d7efc4829e0887cc17e146b/pom.xml#L757
>
>
> --
> 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 jenkinsci-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/jenkinsci-dev/B439BE30-8B80-4F54-87EF-5B9F6F1F19D2%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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CACGLCJZbkBy-tPDbBZdze3vUwXT1A%3DD1M__Muk%2BusHM%3DDOz_RQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

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 entry from the pom.xml if I'm correct about this:

https://github.com/jenkinsci/plugin-pom/blob/afe60afe46f2466d8d7efc4829e0887cc17e146b/pom.xml#L757


-- 
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/B439BE30-8B80-4F54-87EF-5B9F6F1F19D2%40beckweb.net.
For more options, visit https://groups.google.com/d/optout.

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: 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;>
> > 
> >   irfanjs
> >   ***
> >   java.net-m2-repository
> > 
> >   
> >   http://maven.apache.org/SETTINGS/1.1.0;>
> > 
> >   m.g.o-public
> >   https://repo.jenkins-ci.org/public/
> >   repo.jenkins-ci.org
> > 
> >   
> >   http://maven.apache.org/SETTINGS/1.1.0;>
> > 
> >   
> > true
> >   
> >   
> > 
> >   repo.jenkins-ci.org
> >   https://repo.jenkins-ci.org/public/
> > 
> >   
> >   
> > 
> >   repo.jenkins-ci.org
> >   https://repo.jenkins-ci.org/public/
> > 
> >   
> >   jenkins
> > 
> >   
> >
>
> --
> 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 jenkinsci-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/jenkinsci-dev/C0589EF7-13BC-4F5C-A3DC-3DB79B4E0B3F%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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CACGLCJbU%2BAWxt41QTvbXGfquFSP5MSMNFBuWpHpGuVabGOsAdQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

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;>
> 
>   irfanjs
>   ***
>   java.net-m2-repository
> 
>   
>   http://maven.apache.org/SETTINGS/1.1.0;>
> 
>   m.g.o-public
>   https://repo.jenkins-ci.org/public/
>   repo.jenkins-ci.org
> 
>   
>   http://maven.apache.org/SETTINGS/1.1.0;>
> 
>   
> true
>   
>   
> 
>   repo.jenkins-ci.org
>   https://repo.jenkins-ci.org/public/
> 
>   
>   
> 
>   repo.jenkins-ci.org
>   https://repo.jenkins-ci.org/public/
> 
>   
>   jenkins
> 
>   
> 

-- 
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/C0589EF7-13BC-4F5C-A3DC-3DB79B4E0B3F%40beckweb.net.
For more options, visit https://groups.google.com/d/optout.

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 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 org.eclipse.m2e:lifecycle-mapping:jar:1.0.0 is
> missing, no dependency information available
> [WARNING] Failed to retrieve plugin descriptor for
> org.eclipse.m2e:lifecycle-mapping:1.0.0: Plugin 
> org.eclipse.m2e:lifecycle-mapping:1.0.0
> or one of its dependencies could not be resolved: Failure to find
> org.eclipse.m2e:lifecycle-mapping:jar:1.0.0 in
> https://repo.jenkins-ci.org/public/ was cached in the local repository,
> resolution will not be reattempted until the update interval of
> repo.jenkins-ci.org has elapsed or updates are forced
> [INFO]
>
> [INFO] 
> 
> [INFO] Building Chef Sinatra Jenkins plugin 1.12-SNAPSHOT
> [INFO] 
> 
> [WARNING] The POM for org.eclipse.m2e:lifecycle-mapping:jar:1.0.0 is
> missing, no dependency information available
> [WARNING] Failed to retrieve plugin descriptor for
> org.eclipse.m2e:lifecycle-mapping:1.0.0: Plugin 
> org.eclipse.m2e:lifecycle-mapping:1.0.0
> or one of its dependencies could not be resolved: Failure to find
> org.eclipse.m2e:lifecycle-mapping:jar:1.0.0 in
> https://repo.jenkins-ci.org/public/ was cached in the local repository,
> resolution will not be reattempted until the update interval of
> repo.jenkins-ci.org has elapsed or updates are forced
> [INFO]
> [INFO] --- maven-help-plugin:2.2:effective-settings (default-cli) @
> sinatra-chef-builder ---
> [INFO]
> Effective user-specific configuration settings:
>
> 
> 
> 
> 
> 
> 
> 
>
> 
> 
> 
> 
> 
>
> http://maven.apache.org/POM/4.0.0; xmlns:xsi="
> http://www.w3.org/2001/XMLSchema-instance; xsi:schemaLocation="http://
> maven.apache.org/SETTINGS/1.1.0 http://maven.apache.org/xsd/
> settings-1.1.0.xsd">
>   http://maven.apache.org/SETTINGS/1.1.0
> ">C:\Users\irfanjs\.m2\repository
>   http://maven.apache.org/SETTINGS/1.1.0;>
> 
>   irfanjs
>   ***
>   java.net-m2-repository
> 
>   
>   http://maven.apache.org/SETTINGS/1.1.0;>
> 
>   m.g.o-public
>   https://repo.jenkins-ci.org/public/
>   repo.jenkins-ci.org
> 
>   
>   http://maven.apache.org/SETTINGS/1.1.0;>
> 
>   
> true
>   
>   
> 
>   repo.jenkins-ci.org
>   https://repo.jenkins-ci.org/public/
> 
>   
>   
> 
>   repo.jenkins-ci.org
>   https://repo.jenkins-ci.org/public/
> 
>   
>   jenkins
> 
>   
>   http://maven.apache.org/SETTINGS/1.1.0;>
> org.jenkins-ci.tools
> org.apache.maven.plugins
> org.codehaus.mojo
>   
> 
>
> [INFO] 
> 
> [INFO] BUILD SUCCESS
> [INFO] 
> 
> [INFO] Total time: 8.734 s
> [INFO] Finished at: 2017-01-15T00:53:13-08:00
> [INFO] Final Memory: 20M/50M
> [INFO] 
> 
>
> is there any issue in this ?
> regards,
>
>
> On Sat, Jan 14, 2017 at 10:50 PM, Slide  wrote:
>
>> 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:
>>> > https://groups.google.com/d/msgid/jenkinsci-dev/53CC6ED4-3BB
>>> C-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 into
>>> Artifactory, so that should be fine:
>>> > https://github.com/jenkins-infra/repository-permissions-upda
>>> ter/blob/176a269/permissions/plugin-sinatra-chef-builder.yml
>>> >
>>> > So since the permissions look ok (and aren't needed for SNAPSHOTs
>>> anyway), and you've managed to log in to the Jenkins account app and
>>> Artifactory, I would guess that's something is wrong with your Maven
>>> security config.
>>> > But I don't know much about this stuff — maybe you've defined your
>>> id/password in multiple places, or perhaps Maven shows where it's reading
>>> the credentials from if you use --debug?
>>>
>>> 403 Forbidden is what would be caused by upload permissions.
>>>
>>> 401 Unauthorized means that Maven does not send any credentials to
>>> Artifactory, which then refuses to let anonymous upload something.
>>>

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 org.eclipse.m2e:lifecycle-mapping:jar:1.0.0 is
missing, no dependency information available
[WARNING] Failed to retrieve plugin descriptor for
org.eclipse.m2e:lifecycle-mapping:1.0.0: Plugin
org.eclipse.m2e:lifecycle-mapping:1.0.0 or one of its dependencies could
not be resolved: Failure to find
org.eclipse.m2e:lifecycle-mapping:jar:1.0.0 in
https://repo.jenkins-ci.org/public/ was cached in the local repository,
resolution will not be reattempted until the update interval of
repo.jenkins-ci.org has elapsed or updates are forced
[INFO]

[INFO]

[INFO] Building Chef Sinatra Jenkins plugin 1.12-SNAPSHOT
[INFO]

[WARNING] The POM for org.eclipse.m2e:lifecycle-mapping:jar:1.0.0 is
missing, no dependency information available
[WARNING] Failed to retrieve plugin descriptor for
org.eclipse.m2e:lifecycle-mapping:1.0.0: Plugin
org.eclipse.m2e:lifecycle-mapping:1.0.0 or one of its dependencies could
not be resolved: Failure to find
org.eclipse.m2e:lifecycle-mapping:jar:1.0.0 in
https://repo.jenkins-ci.org/public/ was cached in the local repository,
resolution will not be reattempted until the update interval of
repo.jenkins-ci.org has elapsed or updates are forced
[INFO]
[INFO] --- maven-help-plugin:2.2:effective-settings (default-cli) @
sinatra-chef-builder ---
[INFO]
Effective user-specific configuration settings:















http://maven.apache.org/POM/4.0.0; xmlns:xsi="
http://www.w3.org/2001/XMLSchema-instance; xsi:schemaLocation="
http://maven.apache.org/SETTINGS/1.1.0
http://maven.apache.org/xsd/settings-1.1.0.xsd;>
  http://maven.apache.org/SETTINGS/1.1.0
">C:\Users\irfanjs\.m2\repository
  http://maven.apache.org/SETTINGS/1.1.0;>

  irfanjs
  ***
  java.net-m2-repository

  
  http://maven.apache.org/SETTINGS/1.1.0;>

  m.g.o-public
  https://repo.jenkins-ci.org/public/
  repo.jenkins-ci.org

  
  http://maven.apache.org/SETTINGS/1.1.0;>

  
true
  
  

  repo.jenkins-ci.org
  https://repo.jenkins-ci.org/public/

  
  

  repo.jenkins-ci.org
  https://repo.jenkins-ci.org/public/

  
  jenkins

  
  http://maven.apache.org/SETTINGS/1.1.0;>
org.jenkins-ci.tools
org.apache.maven.plugins
org.codehaus.mojo
  


[INFO]

[INFO] BUILD SUCCESS
[INFO]

[INFO] Total time: 8.734 s
[INFO] Finished at: 2017-01-15T00:53:13-08:00
[INFO] Final Memory: 20M/50M
[INFO]


is there any issue in this ?
regards,


On Sat, Jan 14, 2017 at 10:50 PM, Slide  wrote:

> 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:
>> > 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 into Artifactory, so that
>> should be fine:
>> > https://github.com/jenkins-infra/repository-permissions-
>> updater/blob/176a269/permissions/plugin-sinatra-chef-builder.yml
>> >
>> > So since the permissions look ok (and aren't needed for SNAPSHOTs
>> anyway), and you've managed to log in to the Jenkins account app and
>> Artifactory, I would guess that's something is wrong with your Maven
>> security config.
>> > But I don't know much about this stuff — maybe you've defined your
>> id/password in multiple places, or perhaps Maven shows where it's reading
>> the credentials from if you use --debug?
>>
>> 403 Forbidden is what would be caused by upload permissions.
>>
>> 401 Unauthorized means that Maven does not send any credentials to
>> Artifactory, which then refuses to let anonymous upload something.
>>
>> My guess (unclear to me given how this thread developed) is the server ID
>> in settings.xml does not match the server ID in the pom.xml's
>> distributionManagement.
>>
>> --
>> 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 jenkinsci-dev+unsubscr...@googlegroups.com.
>> To view this discussion on the web

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:
> >
> 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 into Artifactory, so that
> should be fine:
> >
> https://github.com/jenkins-infra/repository-permissions-updater/blob/176a269/permissions/plugin-sinatra-chef-builder.yml
> >
> > So since the permissions look ok (and aren't needed for SNAPSHOTs
> anyway), and you've managed to log in to the Jenkins account app and
> Artifactory, I would guess that's something is wrong with your Maven
> security config.
> > But I don't know much about this stuff — maybe you've defined your
> id/password in multiple places, or perhaps Maven shows where it's reading
> the credentials from if you use --debug?
>
> 403 Forbidden is what would be caused by upload permissions.
>
> 401 Unauthorized means that Maven does not send any credentials to
> Artifactory, which then refuses to let anonymous upload something.
>
> My guess (unclear to me given how this thread developed) is the server ID
> in settings.xml does not match the server ID in the pom.xml's
> distributionManagement.
>
> --
> 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 jenkinsci-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/48C8FEE7-49DB-4208-8AC1-DAC1D0E9114B%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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAPiUgVcCM4QJ9tPxev4_fQJ5uPfwqUvrHZejuu33AgeGb_FufQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Not able to release new version of plugin

2017-01-14 Thread Daniel Beck


> 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 the groupId and artifactId from 
> your logs, plus you said that you've logged into Artifactory, so that should 
> be fine:
> https://github.com/jenkins-infra/repository-permissions-updater/blob/176a269/permissions/plugin-sinatra-chef-builder.yml
> 
> So since the permissions look ok (and aren't needed for SNAPSHOTs anyway), 
> and you've managed to log in to the Jenkins account app and Artifactory, I 
> would guess that's something is wrong with your Maven security config.
> But I don't know much about this stuff — maybe you've defined your 
> id/password in multiple places, or perhaps Maven shows where it's reading the 
> credentials from if you use --debug?

403 Forbidden is what would be caused by upload permissions.

401 Unauthorized means that Maven does not send any credentials to Artifactory, 
which then refuses to let anonymous upload something.

My guess (unclear to me given how this thread developed) is the server ID in 
settings.xml does not match the server ID in the pom.xml's 
distributionManagement.

-- 
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/48C8FEE7-49DB-4208-8AC1-DAC1D0E9114B%40beckweb.net.
For more options, visit https://groups.google.com/d/optout.

Re: Not able to release new version of plugin

2017-01-14 Thread Christopher Orr

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 into Artifactory, so
that should be fine:

https://github.com/jenkins-infra/repository-permissions-updater/blob/176a269/permissions/plugin-sinatra-chef-builder.yml

So since the permissions look ok (and aren't needed for SNAPSHOTs
anyway), and you've managed to log in to the Jenkins account app and
Artifactory, I would guess that's something is wrong with your Maven
security config.
But I don't know much about this stuff — maybe you've defined your
id/password in multiple places, or perhaps Maven shows where it's
reading the credentials from if you use --debug?

Regards,
Chris

On 14/01/17 17:56, Irfan Sayed wrote:

OK. Thanks
can you please give me those steps ?
May i request to take that please?

regards,

On Sat, Jan 14, 2017 at 10:12 PM, Slide > wrote:

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 able to release my plugin ?

regards,

On Sat, Jan 14, 2017 at 10:04 PM, Slide > wrote:

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 in
jenkins-ci org, following was the original discussion:
https://issues.jenkins-ci.org/browse/HOSTING-59

we had changed the JIRA component and plugin name to
align the proper artifactID and all.
is this issue due to this ?

Regards,

On Sat, Jan 14, 2017 at 7:25 PM, Irfan Sayed
> wrote:

Yes i do have SNAPSHOT version in the POM.
mvn deploy command also failing with the same error ..
i am still not getting what is the issue

regards,

On Sat, Jan 14, 2017 at 7:14 PM, Slide
> wrote:

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

https://repo.jenkins-ci.org/snapshots

propRel

https://repo.jenkins-ci.org/releases

run the same command: mvn clean package deploy
same error : "401 unauthorized"

regards,

On Sat, Jan 14, 2017 at 1:46 AM, Baptiste
Mathus > wrote:

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"

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 able to release my plugin ?
>
> regards,
>
>
>
>
> On Sat, Jan 14, 2017 at 10:04 PM, Slide  wrote:
>
> 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 in jenkins-ci org, following
> was the original discussion:
> https://issues.jenkins-ci.org/browse/HOSTING-59
>
> we had changed the JIRA component and plugin name to align the proper
> artifactID and all.
> is this issue due to this ?
>
> Regards,
>
>
> On Sat, Jan 14, 2017 at 7:25 PM, Irfan Sayed  wrote:
>
> Yes i do have SNAPSHOT version in the POM.
> mvn deploy command also failing with the same error ..
> i am still not getting what is the issue
>
> regards,
>
>
> On Sat, Jan 14, 2017 at 7:14 PM, Slide  wrote:
>
> 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
> https://repo.jenkins-ci.org/snapshots
>
> 
> 
>  propRel
>  https://repo.jenkins-ci.org/releases
> 
>   
>
> run the same command: mvn clean package deploy
> same error : "401 unauthorized"
>
> regards,
>
>
> On Sat, Jan 14, 2017 at 1:46 AM, Baptiste Mathus  wrote:
>
> 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 :
>
> Yes . i am able to login to :
> https://accounts.jenkins.io/login?from=%2Fmyself%2F
> i uploaded public key as well on above link and tried again releasing.
> but still the same error
>
> Regards,
>
>
> On Sat, Jan 14, 2017 at 3:59 AM, Slide  wrote:
>
> 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, 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] Installing
> C:\sinatra-chef-builder-plugin\target\sinatra-chef-builder
>   .hpi to
> C:\Users\irfanjs\.m2\repository\org\jenkins-ci\plugins\sinatra-chef-buil
>
> der\1.10\sinatra-chef-builder-1.10.hpi
> [INFO] Installing C:\sinatra-chef-builder-plugin\pom.xml to
> C:\Users\irfanjs
>
> \.m2\repository\org\jenkins-ci\plugins\sinatra-chef-builder\1.10\sinatra-chef-bu
>   ilder-1.10.pom
> [INFO] Installing
> C:\sinatra-chef-builder-plugin\target\sinatra-chef-builder
>   .jar to
> C:\Users\irfanjs\.m2\repository\org\jenkins-ci\plugins\sinatra-chef-buil
>
> der\1.10\sinatra-chef-builder-1.10.jar
> [INFO]
> -
> ---
> [INFO] BUILD SUCCESS
> [INFO]
> -
> ---
> [INFO] Total time: 02:35 min
> [INFO] Finished at: 2017-01-13T11:36:47-08:00
> [INFO] Final Memory: 62M/167M
> [INFO]
> -
> ---
> [INFO] Checking in modified POMs...
> [INFO] Executing: cmd.exe /X /C "git add -- pom.xml"
> [INFO] Working directory: C:\sinatra-chef-builder-plugin
> [INFO] Executing: cmd.exe /X /C "git rev-parse --show-toplevel"
> [INFO] Working directory: C:\sinatra-chef-builder-plugin
> [INFO] Executing: cmd.exe /X /C "git status --porcelain ."
> [INFO] Working directory: C:\sinatra-chef-builder-plugin
> [WARNING] Ignoring unrecognized line: ?? pom.xml.releaseBackup
> [WARNING] Ignoring unrecognized line: ?? release.properties
>

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 in jenkins-ci org, following
> was the original discussion:
> https://issues.jenkins-ci.org/browse/HOSTING-59
>
> we had changed the JIRA component and plugin name to align the proper
> artifactID and all.
> is this issue due to this ?
>
> Regards,
>
>
> On Sat, Jan 14, 2017 at 7:25 PM, Irfan Sayed  wrote:
>
> Yes i do have SNAPSHOT version in the POM.
> mvn deploy command also failing with the same error ..
> i am still not getting what is the issue
>
> regards,
>
>
> On Sat, Jan 14, 2017 at 7:14 PM, Slide  wrote:
>
> 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
> https://repo.jenkins-ci.org/snapshots
>
> 
> 
>  propRel
>  https://repo.jenkins-ci.org/releases
> 
>   
>
> run the same command: mvn clean package deploy
> same error : "401 unauthorized"
>
> regards,
>
>
> On Sat, Jan 14, 2017 at 1:46 AM, Baptiste Mathus  wrote:
>
> 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 :
>
> Yes . i am able to login to :
> https://accounts.jenkins.io/login?from=%2Fmyself%2F
> i uploaded public key as well on above link and tried again releasing.
> but still the same error
>
> Regards,
>
>
> On Sat, Jan 14, 2017 at 3:59 AM, Slide  wrote:
>
> 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, 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] Installing
> C:\sinatra-chef-builder-plugin\target\sinatra-chef-builder
>   .hpi to
> C:\Users\irfanjs\.m2\repository\org\jenkins-ci\plugins\sinatra-chef-buil
>
> der\1.10\sinatra-chef-builder-1.10.hpi
> [INFO] Installing C:\sinatra-chef-builder-plugin\pom.xml to
> C:\Users\irfanjs
>
> \.m2\repository\org\jenkins-ci\plugins\sinatra-chef-builder\1.10\sinatra-chef-bu
>   ilder-1.10.pom
> [INFO] Installing
> C:\sinatra-chef-builder-plugin\target\sinatra-chef-builder
>   .jar to
> C:\Users\irfanjs\.m2\repository\org\jenkins-ci\plugins\sinatra-chef-buil
>
> der\1.10\sinatra-chef-builder-1.10.jar
> [INFO]
> -
> ---
> [INFO] BUILD SUCCESS
> [INFO]
> -
> ---
> [INFO] Total time: 02:35 min
> [INFO] Finished at: 2017-01-13T11:36:47-08:00
> [INFO] Final Memory: 62M/167M
> [INFO]
> -
> ---
> [INFO] Checking in modified POMs...
> [INFO] Executing: cmd.exe /X /C "git add -- pom.xml"
> [INFO] Working directory: C:\sinatra-chef-builder-plugin
> [INFO] Executing: cmd.exe /X /C "git rev-parse --show-toplevel"
> [INFO] Working directory: C:\sinatra-chef-builder-plugin
> [INFO] Executing: cmd.exe /X /C "git status --porcelain ."
> [INFO] Working directory: C:\sinatra-chef-builder-plugin
> [WARNING] Ignoring unrecognized line: ?? pom.xml.releaseBackup
> [WARNING] Ignoring unrecognized line: ?? release.properties
> [WARNING] Ignoring unrecognized line: ?? target/
> [INFO] Executing: cmd.exe /X /C "git commit --verbose -F
> C:\Users\irfanjs\AppDat
>   a\Local\Temp\maven-scm-1195565814.commit pom.xml"
> [INFO] Working directory: C:\sinatra-chef-builder-plugin
> [INFO] Executing: cmd.exe /X /C "git symbolic-ref HEAD"
> [INFO] Working directory: C:\sinatra-chef-builder-plugin
> [INFO] Executing: cmd.exe /X /C "git push
>

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
> https://repo.jenkins-ci.org/snapshots
>
> 
> 
>  propRel
>  https://repo.jenkins-ci.org/releases
> 
>   
>
> run the same command: mvn clean package deploy
> same error : "401 unauthorized"
>
> regards,
>
>
> On Sat, Jan 14, 2017 at 1:46 AM, Baptiste Mathus  wrote:
>
> 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 :
>
> Yes . i am able to login to :
> https://accounts.jenkins.io/login?from=%2Fmyself%2F
> i uploaded public key as well on above link and tried again releasing.
> but still the same error
>
> Regards,
>
>
> On Sat, Jan 14, 2017 at 3:59 AM, Slide  wrote:
>
> 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, 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] Installing
> C:\sinatra-chef-builder-plugin\target\sinatra-chef-builder
>   .hpi to
> C:\Users\irfanjs\.m2\repository\org\jenkins-ci\plugins\sinatra-chef-buil
>
> der\1.10\sinatra-chef-builder-1.10.hpi
> [INFO] Installing C:\sinatra-chef-builder-plugin\pom.xml to
> C:\Users\irfanjs
>
> \.m2\repository\org\jenkins-ci\plugins\sinatra-chef-builder\1.10\sinatra-chef-bu
>   ilder-1.10.pom
> [INFO] Installing
> C:\sinatra-chef-builder-plugin\target\sinatra-chef-builder
>   .jar to
> C:\Users\irfanjs\.m2\repository\org\jenkins-ci\plugins\sinatra-chef-buil
>
> der\1.10\sinatra-chef-builder-1.10.jar
> [INFO]
> -
> ---
> [INFO] BUILD SUCCESS
> [INFO]
> -
> ---
> [INFO] Total time: 02:35 min
> [INFO] Finished at: 2017-01-13T11:36:47-08:00
> [INFO] Final Memory: 62M/167M
> [INFO]
> -
> ---
> [INFO] Checking in modified POMs...
> [INFO] Executing: cmd.exe /X /C "git add -- pom.xml"
> [INFO] Working directory: C:\sinatra-chef-builder-plugin
> [INFO] Executing: cmd.exe /X /C "git rev-parse --show-toplevel"
> [INFO] Working directory: C:\sinatra-chef-builder-plugin
> [INFO] Executing: cmd.exe /X /C "git status --porcelain ."
> [INFO] Working directory: C:\sinatra-chef-builder-plugin
> [WARNING] Ignoring unrecognized line: ?? pom.xml.releaseBackup
> [WARNING] Ignoring unrecognized line: ?? release.properties
> [WARNING] Ignoring unrecognized line: ?? target/
> [INFO] Executing: cmd.exe /X /C "git commit --verbose -F
> C:\Users\irfanjs\AppDat
>   a\Local\Temp\maven-scm-1195565814.commit pom.xml"
> [INFO] Working directory: C:\sinatra-chef-builder-plugin
> [INFO] Executing: cmd.exe /X /C "git symbolic-ref HEAD"
> [INFO] Working directory: C:\sinatra-chef-builder-plugin
> [INFO] Executing: cmd.exe /X /C "git push
> g...@github.com/jenkinsci/sinatra-chef-
> builder-plugin.git
> refs/heads/master:refs/heads/master"
> [INFO] Working directory: C:\sinatra-chef-builder-plugin
> [INFO]
> 
> [INFO] BUILD FAILURE
> [INFO]
> 
> [INFO] Total time: 03:37 min
> [INFO] Finished at: 2017-01-13T11:36:48-08:00
> [INFO] Final Memory: 16M/39M
> [INFO]
> 
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-release-plugin:2.5
> .3:prepare (default-cli) on project
> sinatra-chef-builder: Unable to commit files
> [ERROR] Provider message:
> [ERROR] The git-push command failed.
> [ERROR] Command output:
> [ERROR] fatal:

Re: Not able to release new version of plugin

2017-01-14 Thread Baptiste Mathus

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 :

> Yes . i am able to login to : https://accounts.jenkins.io/
> login?from=%2Fmyself%2F
> i uploaded public key as well on above link and tried again releasing.
> but still the same error
>
> Regards,
>
>
> On Sat, Jan 14, 2017 at 3:59 AM, Slide  wrote:
>
>> 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, 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] Installing 
>>> C:\sinatra-chef-builder-plugin\target\sinatra-chef-builder
>>>   .hpi to
>>> C:\Users\irfanjs\.m2\repository\org\jenkins-ci\plugins\sinatra-chef-buil
>>>
>>> der\1.10\sinatra-chef-builder-1.10.hpi
>>> [INFO] Installing C:\sinatra-chef-builder-plugin\pom.xml to
>>> C:\Users\irfanjs
>>> 
>>> \.m2\repository\org\jenkins-ci\plugins\sinatra-chef-builder\1.10\sinatra-chef-bu
>>>   ilder-1.10.pom
>>> [INFO] Installing 
>>> C:\sinatra-chef-builder-plugin\target\sinatra-chef-builder
>>>   .jar to
>>> C:\Users\irfanjs\.m2\repository\org\jenkins-ci\plugins\sinatra-chef-buil
>>>
>>> der\1.10\sinatra-chef-builder-1.10.jar
>>> [INFO] 
>>> -
>>>   ---
>>> [INFO] BUILD SUCCESS
>>> [INFO] 
>>> -
>>>   ---
>>> [INFO] Total time: 02:35 min
>>> [INFO] Finished at: 2017-01-13T11:36:47-08:00
>>> [INFO] Final Memory: 62M/167M
>>> [INFO] 
>>> -
>>>   ---
>>> [INFO] Checking in modified POMs...
>>> [INFO] Executing: cmd.exe /X /C "git add -- pom.xml"
>>> [INFO] Working directory: C:\sinatra-chef-builder-plugin
>>> [INFO] Executing: cmd.exe /X /C "git rev-parse --show-toplevel"
>>> [INFO] Working directory: C:\sinatra-chef-builder-plugin
>>> [INFO] Executing: cmd.exe /X /C "git status --porcelain ."
>>> [INFO] Working directory: C:\sinatra-chef-builder-plugin
>>> [WARNING] Ignoring unrecognized line: ?? pom.xml.releaseBackup
>>> [WARNING] Ignoring unrecognized line: ?? release.properties
>>> [WARNING] Ignoring unrecognized line: ?? target/
>>> [INFO] Executing: cmd.exe /X /C "git commit --verbose -F
>>> C:\Users\irfanjs\AppDat
>>>   a\Local\Temp\maven-scm-1195565814.commit pom.xml"
>>> [INFO] Working directory: C:\sinatra-chef-builder-plugin
>>> [INFO] Executing: cmd.exe /X /C "git symbolic-ref HEAD"
>>> [INFO] Working directory: C:\sinatra-chef-builder-plugin
>>> [INFO] Executing: cmd.exe /X /C "git push g...@github.com/jenkinsci/sinat
>>> ra-chef-
>>> builder-plugin.git refs/heads/master:refs/heads/master"
>>> [INFO] Working directory: C:\sinatra-chef-builder-plugin
>>> [INFO] 
>>> 
>>> [INFO] BUILD FAILURE
>>> [INFO] 
>>> 
>>> [INFO] Total time: 03:37 min
>>> [INFO] Finished at: 2017-01-13T11:36:48-08:00
>>> [INFO] Final Memory: 16M/39M
>>> [INFO] 
>>> 
>>> [ERROR] Failed to execute goal 
>>> org.apache.maven.plugins:maven-release-plugin:2.5
>>>   .3:prepare
>>> (default-cli) on project sinatra-chef-builder: Unable to commit files
>>> [ERROR] Provider message:
>>> [ERROR] The git-push command failed.
>>> [ERROR] Command output:
>>> [ERROR] fatal: 'g...@github.com/jenkinsci/sinatra-chef-builder-plugin.git'
>>> does n   ot
>>> appear to be a git repository
>>> [ERROR] fatal: Could not read from remote repository.
>>> [ERROR]
>>> [ERROR] Please make sure you have the correct access rights
>>> [ERROR] and the repository exists.
>>> [ERROR] -> [Help 1]
>>> [ERROR]
>>> [ERROR] To see the full

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, 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] Installing
> C:\sinatra-chef-builder-plugin\target\sinatra-chef-builder
>   .hpi to
> C:\Users\irfanjs\.m2\repository\org\jenkins-ci\plugins\sinatra-chef-buil
>
> der\1.10\sinatra-chef-builder-1.10.hpi
> [INFO] Installing C:\sinatra-chef-builder-plugin\pom.xml to
> C:\Users\irfanjs
>
> \.m2\repository\org\jenkins-ci\plugins\sinatra-chef-builder\1.10\sinatra-chef-bu
>   ilder-1.10.pom
> [INFO] Installing
> C:\sinatra-chef-builder-plugin\target\sinatra-chef-builder
>   .jar to
> C:\Users\irfanjs\.m2\repository\org\jenkins-ci\plugins\sinatra-chef-buil
>
> der\1.10\sinatra-chef-builder-1.10.jar
> [INFO]
> -
> ---
> [INFO] BUILD SUCCESS
> [INFO]
> -
> ---
> [INFO] Total time: 02:35 min
> [INFO] Finished at: 2017-01-13T11:36:47-08:00
> [INFO] Final Memory: 62M/167M
> [INFO]
> -
> ---
> [INFO] Checking in modified POMs...
> [INFO] Executing: cmd.exe /X /C "git add -- pom.xml"
> [INFO] Working directory: C:\sinatra-chef-builder-plugin
> [INFO] Executing: cmd.exe /X /C "git rev-parse --show-toplevel"
> [INFO] Working directory: C:\sinatra-chef-builder-plugin
> [INFO] Executing: cmd.exe /X /C "git status --porcelain ."
> [INFO] Working directory: C:\sinatra-chef-builder-plugin
> [WARNING] Ignoring unrecognized line: ?? pom.xml.releaseBackup
> [WARNING] Ignoring unrecognized line: ?? release.properties
> [WARNING] Ignoring unrecognized line: ?? target/
> [INFO] Executing: cmd.exe /X /C "git commit --verbose -F
> C:\Users\irfanjs\AppDat
>   a\Local\Temp\maven-scm-1195565814.commit pom.xml"
> [INFO] Working directory: C:\sinatra-chef-builder-plugin
> [INFO] Executing: cmd.exe /X /C "git symbolic-ref HEAD"
> [INFO] Working directory: C:\sinatra-chef-builder-plugin
> [INFO] Executing: cmd.exe /X /C "git push
> g...@github.com/jenkinsci/sinatra-chef-
> builder-plugin.git
> refs/heads/master:refs/heads/master"
> [INFO] Working directory: C:\sinatra-chef-builder-plugin
> [INFO]
> 
> [INFO] BUILD FAILURE
> [INFO]
> 
> [INFO] Total time: 03:37 min
> [INFO] Finished at: 2017-01-13T11:36:48-08:00
> [INFO] Final Memory: 16M/39M
> [INFO]
> 
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-release-plugin:2.5
> .3:prepare (default-cli) on project
> sinatra-chef-builder: Unable to commit files
> [ERROR] Provider message:
> [ERROR] The git-push command failed.
> [ERROR] Command output:
> [ERROR] fatal: 'g...@github.com/jenkinsci/sinatra-chef-builder-plugin.git'
> does n   ot
> appear to be a git repository
> [ERROR] fatal: Could not read from remote repository.
> [ERROR]
> [ERROR] Please make sure you have the correct access rights
> [ERROR] and the repository exists.
> [ERROR] -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the
> -e swit   ch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions,
> please rea   d
> the following articles:
> [ERROR] [Help 1]
> http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureExc
> eption
>
> irfanjs@host-10 MINGW64 /c/sinatra-chef-builder-plugin (master)
> $
>
> regards,
>
>
> On Fri, Jan 13, 2017 at 11:10 AM, Slide  wrote:
>
> 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

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] Installing
C:\sinatra-chef-builder-plugin\target\sinatra-chef-builder
  .hpi to
C:\Users\irfanjs\.m2\repository\org\jenkins-ci\plugins\sinatra-chef-buil

der\1.10\sinatra-chef-builder-1.10.hpi
[INFO] Installing C:\sinatra-chef-builder-plugin\pom.xml to
C:\Users\irfanjs

\.m2\repository\org\jenkins-ci\plugins\sinatra-chef-builder\1.10\sinatra-chef-bu
  ilder-1.10.pom
[INFO] Installing
C:\sinatra-chef-builder-plugin\target\sinatra-chef-builder
  .jar to
C:\Users\irfanjs\.m2\repository\org\jenkins-ci\plugins\sinatra-chef-buil

der\1.10\sinatra-chef-builder-1.10.jar
[INFO]
-
---
[INFO] BUILD SUCCESS
[INFO]
-
---
[INFO] Total time: 02:35 min
[INFO] Finished at: 2017-01-13T11:36:47-08:00
[INFO] Final Memory: 62M/167M
[INFO]
-
---
[INFO] Checking in modified POMs...
[INFO] Executing: cmd.exe /X /C "git add -- pom.xml"
[INFO] Working directory: C:\sinatra-chef-builder-plugin
[INFO] Executing: cmd.exe /X /C "git rev-parse --show-toplevel"
[INFO] Working directory: C:\sinatra-chef-builder-plugin
[INFO] Executing: cmd.exe /X /C "git status --porcelain ."
[INFO] Working directory: C:\sinatra-chef-builder-plugin
[WARNING] Ignoring unrecognized line: ?? pom.xml.releaseBackup
[WARNING] Ignoring unrecognized line: ?? release.properties
[WARNING] Ignoring unrecognized line: ?? target/
[INFO] Executing: cmd.exe /X /C "git commit --verbose -F
C:\Users\irfanjs\AppDat
  a\Local\Temp\maven-scm-1195565814.commit pom.xml"
[INFO] Working directory: C:\sinatra-chef-builder-plugin
[INFO] Executing: cmd.exe /X /C "git symbolic-ref HEAD"
[INFO] Working directory: C:\sinatra-chef-builder-plugin
[INFO] Executing: cmd.exe /X /C "git push
g...@github.com/jenkinsci/sinatra-chef-
  builder-plugin.git
refs/heads/master:refs/heads/master"
[INFO] Working directory: C:\sinatra-chef-builder-plugin
[INFO]

[INFO] BUILD FAILURE
[INFO]

[INFO] Total time: 03:37 min
[INFO] Finished at: 2017-01-13T11:36:48-08:00
[INFO] Final Memory: 16M/39M
[INFO]

[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-release-plugin:2.5
.3:prepare (default-cli) on project
sinatra-chef-builder: Unable to commit files
[ERROR] Provider message:
[ERROR] The git-push command failed.
[ERROR] Command output:
[ERROR] fatal: 'g...@github.com/jenkinsci/sinatra-chef-builder-plugin.git'
does n   ot
appear to be a git repository
[ERROR] fatal: Could not read from remote repository.
[ERROR]
[ERROR] Please make sure you have the correct access rights
[ERROR] and the repository exists.
[ERROR] -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e
swit   ch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions,
please rea   d
the following articles:
[ERROR] [Help 1]
http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureExc
  eption

irfanjs@host-10 MINGW64 /c/sinatra-chef-builder-plugin (master)
$

regards,


On Fri, Jan 13, 2017 at 11:10 AM, Slide  wrote:

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
http://github.com/jenkinsci/chefbuilder-plugin
HEAD

The URL's clearly don't match.


The SCM section for the token-macro-plugin that I maintain is like this:


scm:git:git://github.com/jenkinsci/token-macro-plugin.git
scm:git:g...@github.com:
jenkinsci/token-macro-plugin.git
HEAD

Can you post a build log of the current runs after the changes?

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
http://github.com/jenkinsci/chefbuilder-plugin
HEAD

The URL's clearly don't match.


The SCM section for the token-macro-plugin that I maintain is like this:


scm:git:git://github.com/jenkinsci/token-macro-plugin.git
scm:git:g...@github.com:
jenkinsci/token-macro-plugin.git
HEAD

Can you post a build log of the current runs after the changes?

On Fri, Jan 13, 2017 at 11:38 AM Irfan Sayed  wrote:

> 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  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  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  wrote:
>
> 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:
>
> 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/display/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-infra/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  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  wrote:
>
> 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 is the snippet from settings.xml:
>
> 
> 
>   java.net-m2-repository 
>   irfanjs
>   $encryptedpassword
> 
>   
>
> 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 
> 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

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 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  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  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  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 
>>> 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  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 
>>> wrote:
>>>
>>> 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 is the snippet from settings.xml:
>>>
>>> 
>>> 
>>>   java.net-m2-repository 
>>>   irfanjs
>>>   $encryptedpassword
>>> 
>>>   
>>>
>>> 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 
>>> 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 
>>> wrote:
>>>
>>> further update:
>>> i started ssh-agent and imported the private key

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  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  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  wrote:
>>
>> 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:
>>
>> 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/
>> display/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-
>> infra/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  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  wrote:
>>
>> 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 is the snippet from settings.xml:
>>
>> 
>> 
>>   java.net-m2-repository 
>>   irfanjs
>>   $encryptedpassword
>> 
>>   
>>
>> 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 
>> 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 
>> 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 
>> wrote:
>>
>> Hi,
>> Please

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 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  wrote:
>
> 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:
>
> 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/display/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-infra/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  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  wrote:
>
> 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 is the snippet from settings.xml:
>
> 
> 
>   java.net-m2-repository 
>   irfanjs
>   $encryptedpassword
> 
>   
>
> 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 
> 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 
> 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  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 
> 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

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
Regards,


On Fri, Jan 13, 2017 at 11:16 PM, Slide  wrote:

> 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:
>
>> 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/
>> display/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-
>> infra/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  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  wrote:
>>
>> 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 is the snippet from settings.xml:
>>
>> 
>> 
>>   java.net-m2-repository 
>>   irfanjs
>>   $encryptedpassword
>> 
>>   
>>
>> 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 
>> 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 
>> 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 
>> 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 
>> 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

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:

> 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/display/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-infra/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  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  wrote:
>
> 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 is the snippet from settings.xml:
>
> 
> 
>   java.net-m2-repository 
>   irfanjs
>   $encryptedpassword
> 
>   
>
> 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 
> 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 
> 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  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 
> 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  wrote:
>
> Thanks.
> Let me thoroughly have a look and update
>
> Regards,
>
>
> On Wed, Jan 11, 2017 at 10:07 PM, Daniel Beck  wrote:
>
>
> > On 11.01.2017, at 17:34, Irfan Sayed  wrote:
> >
> > not getting why "unauthorized" error is coming
>
> Have you looked into all of the

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 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/display/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-infra/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  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  wrote:
>
>> 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 is the snippet from settings.xml:
>>
>> 
>> 
>>   java.net-m2-repository 
>>   irfanjs
>>   $encryptedpassword
>> 
>>   
>>
>> 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 
>> 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 
>> 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 
>> 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 
>> 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 
>> wrote:
>>
>> Thanks.
>> Let me thoroughly have a look and update
>>
>> Regards,
>>
>>
>> On Wed, Jan 11, 2017 at 10:07 PM, Daniel Beck  wrote:
>>
>>
>> > 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 ?
>>
>> --
>> 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

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 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 is the snippet from settings.xml:
>
> 
> 
>   java.net-m2-repository 
>   irfanjs
>   $encryptedpassword
> 
>   
>
> 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 
> 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 
> 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  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 
> 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  wrote:
>
> Thanks.
> Let me thoroughly have a look and update
>
> Regards,
>
>
> On Wed, Jan 11, 2017 at 10:07 PM, Daniel Beck  wrote:
>
>
> > 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
> ?
>
> --
> 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 jenkinsci-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/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 jenkinsci-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/CACGLCJb-iR9LRoDpCGcwACSakU-MMkOrX5QpQGpe-9uUkAQBpQ%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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAPiUgVf5NzjAnMDxVgwFRSxrqn8oTtcxTiLMhcr5rXfEzLtnNQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

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 is the snippet from settings.xml:
>
> 
> 
>   java.net-m2-repository 
>   irfanjs
>   $encryptedpassword
> 
>   
>
> 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 
> 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 
>> 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 
>>> 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 
 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 
> wrote:
>
>> Thanks.
>> Let me thoroughly have a look and update
>>
>> Regards,
>>
>>
>> On Wed, Jan 11, 2017 at 10:07 PM, Daniel Beck  wrote:
>>
>>>
>>> > 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 ?
>>>
>>> --
>>> 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 jenkinsci-dev+unsubscr...@googlegroups.com.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/jenkinsci-dev/7956E78F-980
>>> D-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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CACGLCJb-iR9LRoDpCGcwACSakU-MMkOrX5QpQGpe-9uUkAQBpQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Not able to release new version of plugin