[JIRA] [git-client-plugin] (JENKINS-21116) Git Publisher does not use Credentials

mail@andrey-belyaevskiy.ru (JIRA)

unread,

Sep 17, 2015, 10:08:02 AM9/17/15

to jenkinsc...@googlegroups.com

Andrey Belyaevskiy reopened an issue

Perhaps, I faced to same issue

 
                                                    Recording test results
 > /usr/bin/git tag -l 184 # timeout=10
 > /usr/bin/git tag -a -f -m Jenkins Git plugin tagging with 184 184 # timeout=10
Pushing tag 184 to repo origin
using GIT_SSH to set credentials 
 > /usr/bin/git --version # timeout=10
 > /usr/bin/git -c core.askpass=true push ssh://g...@sk-stash.lss.emc.com:7999/par/parseq.git 184 -f
ERROR: Failed to push tag 184 to origin
hudson.plugins.git.GitException: Command "/usr/bin/git -c core.askpass=true push ssh://g...@sk-stash.lss.emc.com:7999/par/parseq.git 184 -f" returned status code 128:
stdout: 
stderr: fatal: remote error: Insufficient permissions
You do not have permission to push to the repository Parseq in project PARSEQ
fatal: Could not read from remote repository.
 
                                                

on versions Git plugin 2.4.0, git client plugin 1.19.0, jenkins 1.581

Jenkins /

JENKINS-21116

Git Publisher does not use Credentials

Change By:	Andrey Belyaevskiy
Resolution:	Fixed
Status:	Closed Reopened

Add Comment

This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)

mail@andrey-belyaevskiy.ru (JIRA)

unread,

Sep 17, 2015, 10:09:01 AM9/17/15

to jenkinsc...@googlegroups.com

Andrey Belyaevskiy edited a comment on

JENKINS-21116

Re: Git Publisher does not use Credentials

Perhaps, I faced to same issue

{code}

Recording test results
> /usr/bin/git tag -l 184 # timeout=10
> /usr/bin/git tag -a -f -m Jenkins Git plugin tagging with 184 184 # timeout=10
Pushing tag 184 to repo origin
using GIT_SSH to set credentials
> /usr/bin/git --version # timeout=10

> /usr/bin/git -c core.askpass=true push ssh://git@sk-stash. lss url . emc. com:7999/par/ parseq prsq .git 184 -f

ERROR: Failed to push tag 184 to origin

hudson.plugins.git.GitException: Command "/usr/bin/git -c core.askpass=true push ssh://git@sk-stash. lss url . emc. com:7999/par/parseq.git 184 -f" returned status code 128:

stdout:
stderr: fatal: remote error: Insufficient permissions

You do not have permission to push to the repository Parseq Prsq in project PARSEQ PRSQ

fatal: Could not read from remote repository.

{code}

on versions Git plugin 2.4.0, git client plugin 1.19.0, jenkins 1.581

Add Comment

mark.earl.waite@gmail.com (JIRA)

unread,

Sep 17, 2015, 10:36:01 AM9/17/15

to jenkinsc...@googlegroups.com

Mark Waite commented on

JENKINS-21116

Re: Git Publisher does not use Credentials

Andrey Belyaevskiy I doubt this bug has reappeared.

I'm using git plugin 2.4.0 and git client plugin 1.19.0 on multiple machines, with each of them pushing changes to an ssh authenticated central repository. I believe many other users are doing the same with that version of the plugin. The plugin stats show that version 2.4.0 is installed in over 21000 installations and this is quite a common use case.

You may want to investigate other possible causes for the failure to push that tag.

As you investigate further, could you update this bug report with your results? I was tempted to immediately mark the issue as resolved, but thought it should wait for you to do some further investigation.

Add Comment

mail@andrey-belyaevskiy.ru (JIRA)

unread,

Sep 18, 2015, 7:06:04 AM9/18/15

to jenkinsc...@googlegroups.com

Andrey Belyaevskiy closed an issue as Not A Defect

I found that my key I use for repo clone have read only access in Stash repository as described in http://stackoverflow.com/questions/32627821/push-tag-to-stash-for-successfull-build-in-jenkins-fails-with-code-128-and-error/32643868#32643868. After I changed key to RW one all works fine.

I'm Sorry for wrong re-open.

Jenkins /

JENKINS-21116

Git Publisher does not use Credentials

Change By:	Andrey Belyaevskiy
Status:	Reopened Closed
Resolution:	Not A Defect

Add Comment

mark.earl.waite@gmail.com (JIRA)

unread,

Sep 18, 2015, 7:12:04 AM9/18/15

to jenkinsc...@googlegroups.com

Mark Waite reopened an issue

Jenkins /

JENKINS-21116

Git Publisher does not use Credentials

Change By:	Mark Waite
Resolution:	Not A Defect
Status:	Closed Reopened
Assignee:	Nicolas De Loof Mark Waite

Add Comment

mark.earl.waite@gmail.com (JIRA)

unread,

Sep 18, 2015, 7:17:08 AM9/18/15

to jenkinsc...@googlegroups.com

Mark Waite resolved as Fixed

Thanks for the update. I'm glad that it is still fixed.

I dream of someday finding a way to provide better diagnostics for permission errors. Most permission errors can have multiple causes, and the process to evaluate to root cause can be quite complex, but it seems like it would be possible, and would be much more user friendly if several possible causes could be suggested.

In your case, the root cause analysis would need to realize that reading the repository was successful, but writing the repository failed. In other cases, the problem could be an incorrect private key, or the wrong public key being registered with the server, or the wrong host key being recorded on the client, or many other causes.

Jenkins /