Re: Not able to release new version of plugin

[Slide]

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

[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

[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

[Slide]

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

[Slide]

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

[Slide]

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

[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