[JIRA] [git] (JENKINS-22119) Fail to update update git repository with stored credential
Mikkel Larsen commented on JENKINS-22119 Fail to update update git repository with stored credential I can add a bit of information. Rolling back to 1.6.3 solves the problem. I get the error pulling from bitbucket, and it fails for every repo I pull from bitbucket. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git] (JENKINS-22119) Fail to update update git repository with stored credential
Mark Waite commented on JENKINS-22119 Fail to update update git repository with stored credential Thanks for the hint to use bitbucket. I can see the failure if I configure a credential with a username and password for a private bitbucket git repository. If the bitbucket repository is public (which I had been using before), then the clone succeeds. More exploration will be required. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git] (JENKINS-22119) Fail to update update git repository with stored credential
Mark Waite edited a comment on JENKINS-22119 Fail to update update git repository with stored credential Thanks for the hint to use bitbucket. I can see the failure if I configure a credential with a username and password for a private bitbucket git repository. If the bitbucket repository is public (which I had been using before), then the clone succeeds. More exploration will be required. I don't see the same failure if I configure a credential with a username and password for a private github repository. Public github repositories also do not show any issue. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git] (JENKINS-22119) Fail to update update git repository with stored credential
Mark Waite edited a comment on JENKINS-22119 Fail to update update git repository with stored credential Thanks for the hint to use bitbucket. I can see the failure if I configure a credential with a username and password for a private bitbucket git repository. If the bitbucket repository is public (which I had been using before), then the clone succeeds. More exploration will be required. I don't see the same failure if I configure a credential with a username and password for a private github repository. Public github repositories also do not show any issue. Provider Private Repo Public Repo github 1.6.3 (ok) 1.6.3 (ok) bitbucket 1.6.3 (ok) 1.6.3 (ok) github 1.6.4 (ok) 1.6.4 (ok) bitbucket 1.6.4 (bad) 1.6.4 (ok) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git] (JENKINS-22119) Fail to update update git repository with stored credential
Mark Waite edited a comment on JENKINS-22119 Fail to update update git repository with stored credential Thanks for the hint to use bitbucket. I can see the failure if I configure a credential with a username and password for a private bitbucket git repository. If the bitbucket repository is public (which I had been using before), then the clone succeeds. More exploration will be required. I don't see the same failure if I configure a credential with a username and password for a private github repository. Public github repositories also do not show any issue. Provider Private Repo Public Repo github 1.6.3 (ok) 1.6.3 (ok) bitbucket 1.6.3 (ok) 1.6.3 (ok) github 1.6.4 (ok) 1.6.4 (ok) bitbucket 1.6.4 (bad) 1.6.4 (ok) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git] (JENKINS-22119) Fail to update update git repository with stored credential
su shi created JENKINS-22119 Fail to update update git repository with stored credential Issue Type: Bug Affects Versions: current Assignee: Nicolas De Loof Components: git, git-client Created: 11/Mar/14 6:58 AM Description: After upgrade to git plugin 2.0.4, git client plugin 1.6.4 All the jobs with https repository url and using stored credential failed, refer to following log. Downgrade to git:2.0.3, git-client 1.6.3, the issue has gone. 00:00:00.002 Started by user anonymous 00:00:00.003 EnvInject - Loading node environment variables. 00:00:00.004 Building on master in workspace xxx 00:00:00.108 Fetching changes from the remote Git repository 00:00:00.141 Fetching upstream changes from https://xxx.git 00:00:01.667 FATAL: Failed to fetch from https://xxx.git 00:00:01.668 hudson.plugins.git.GitException: Failed to fetch from https://.git 00:00:01.669 at hudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:621) 00:00:01.669 at hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:853) 00:00:01.669 at hudson.plugins.git.GitSCM.checkout(GitSCM.java:878) 00:00:01.669 at hudson.model.AbstractProject.checkout(AbstractProject.java:1414) 00:00:01.669 at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:671) 00:00:01.669 at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:88) 00:00:01.669 at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:580) 00:00:01.669 at hudson.model.Run.execute(Run.java:1676) 00:00:01.669 at hudson.matrix.MatrixBuild.run(MatrixBuild.java:304) 00:00:01.669 at hudson.model.ResourceController.execute(ResourceController.java:88) 00:00:01.669 at hudson.model.Executor.run(Executor.java:231) 00:00:01.669 at hudson.model.OneOffExecutor.run(OneOffExecutor.java:43) 00:00:01.669 Caused by: hudson.plugins.git.GitException: Failed to connect to https://.git using credentials (status = 401) 00:00:01.669 at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.checkCredentials(CliGitAPIImpl.java:1725) 00:00:01.669 at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1030) 00:00:01.669 at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.access$200(CliGitAPIImpl.java:88) 00:00:01.669 at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$1.execute(CliGitAPIImpl.java:219) 00:00:01.669 at hudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:619) 00:00:01.669 ... 11 more Environment: Jenkins 1.553 Mac slave Project: Jenkins Priority: Critical Reporter: su shi This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git] (JENKINS-22119) Fail to update update git repository with stored credential
Mark Waite commented on JENKINS-22119 Fail to update update git repository with stored credential I believe the 401 error code in the stack trace indicates that the request was not authorized by the web server. The git-client-plugin 1.6.4 switched from an obsolete version of an http library to a newer supported version of that http library. It also added support the NTLM credentials and for Team Foundation Server git repositories. If you'd be willing to perform the test, I'd appreciate having you attempt to upgrade just the git-client-plugin, without upgrading git-plugin. If it fails then that will point to changes in git-client-plugin as the most likely cause. If it passes, then it will need to be investigated in both. Does the https server use a self-signed certificate? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git] (JENKINS-22119) Fail to update update git repository with stored credential
su shi commented on JENKINS-22119 Fail to update update git repository with stored credential yes, with only git-client upgraded to 1.6.4, git fetch failed. The server is not using self-signed cert. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git] (JENKINS-22119) Fail to update update git repository with stored credential
su shi commented on JENKINS-22119 Fail to update update git repository with stored credential yes, with only git-client upgraded to 1.6.4, git fetch failed. The server is not using self-signed cert. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git] (JENKINS-22119) Fail to update update git repository with stored credential
Mark Waite commented on JENKINS-22119 Fail to update update git repository with stored credential Thanks. That indicates the problem is likely in the git-client-plugin changes from 1.6.3 to 1.6.4. We'll need you to do deeper investigation to try to narrow the failure modes. Some of the questions which may help narrow the failure modes include: Does the problem also appear on a copy of the failing job? Does the problem also appear on a newly created job using the same git URL and credentials? Does the problem also appear with other https git repositories in your environment? Does the problem also appear for you with https git repositories outside your environment? (like github or bitbucket) Is there a public URL which can be used to see the same problem? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
