[JIRA] [git-client] (JENKINS-20196) Failed to connect to URL (status = 404)
Flavio Donzé commented on JENKINS-20196 Failed to connect to URL (status = 404) The new exception I posted above (fatal: Authentication failed for 'https://usern...@bitbucket.org/scodi/tools.git/) seems to be a different problem than the original issue. I noticed that my password contains a "!", which is changed into "%21", this leads to the "Authentication failed" exception. Using the "configured credentials" works fine, alone or with the multiple SCM plugin. 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/groups/opt_out.
[JIRA] [git-client] (JENKINS-20196) Failed to connect to URL (status = 404)
Mark Waite commented on JENKINS-20196 Failed to connect to URL (status = 404) You might try defining a test job which uses only Git with your bitbucket repository. If that clones successfully, then the problem is likely an interaction between the multiple SCM plugin and the Git plugin. If that doesn't clone successfully, then you might try placing the user name and password as a credential in Jenkins, then reference the credential from the job definition. 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/groups/opt_out.
[JIRA] [git-client] (JENKINS-20196) Failed to connect to URL (status = 404)
Flavio Donzé commented on JENKINS-20196 Failed to connect to URL (status = 404) "Multiple SCMs plugin" version 0.3 I do have some old credentials in the "manage jenkins" area, but I'm not using them in the job. 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/groups/opt_out.
[JIRA] [git-client] (JENKINS-20196) Failed to connect to URL (status = 404)
Mark Waite commented on JENKINS-20196 Failed to connect to URL (status = 404) Did you configure a credential for that bitbucket repository from the "Manage Jenkins" page, then use that credential from within the job definition? What version of the multiple SCM plugin are you using? My understanding is that there is a bug in the multiple SCM plugin 0.3 which causes it to not work correctly with the git plugin. 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/groups/opt_out.
[JIRA] [git-client] (JENKINS-20196) Failed to connect to URL (status = 404)
Flavio Donzé commented on JENKINS-20196 Failed to connect to URL (status = 404) I just updated to "GIT plugin" 2.0.3 and "GIT client plugin" 1.6.3. Getting the following output: Cloning repository https://username:passw...@bitbucket.org/scodi/tools.git Fetching upstream changes from https://usern...@bitbucket.org/scodi/tools.git ERROR: Error cloning remote repo 'origin' hudson.plugins.git.GitException: Command "git fetch --tags --progress https://usern...@bitbucket.org/scodi/tools.git +refs/heads/:refs/remotes/origin/" returned status code 128: stdout: stderr: fatal: Authentication failed for 'https://usern...@bitbucket.org/scodi/tools.git/' at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1173) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1043) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.access$200(CliGitAPIImpl.java:74) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$1.execute(CliGitAPIImpl.java:207) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$2.execute(CliGitAPIImpl.java:358) at hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:847) at hudson.plugins.git.GitSCM.checkout(GitSCM.java:880) at org.jenkinsci.plugins.multiplescms.MultiSCM.checkout(MultiSCM.java:118) at hudson.model.AbstractProject.checkout(AbstractProject.java:1411) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:651) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:88) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:560) at hudson.model.Run.execute(Run.java:1670) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:231) ERROR: null 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/groups/opt_out.
[JIRA] [git-client] (JENKINS-20196) Failed to connect to URL (status = 404)
Mark Waite resolved JENKINS-20196 as Fixed Failed to connect to URL (status = 404) Closing the bug report after 7 days without a response. I have verified that a bitbucket repository URL with the user name and password embedded work correctly. Change By: Mark Waite (25/Feb/14 1:09 AM) Status: Open Resolved Resolution: Fixed 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/groups/opt_out.
[JIRA] [git-client] (JENKINS-20196) Failed to connect to URL (status = 404)
Mark Waite closed JENKINS-20196 as Fixed Failed to connect to URL (status = 404) Change By: Mark Waite (25/Feb/14 1:10 AM) Status: Resolved Closed 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/groups/opt_out.
[JIRA] [git-client] (JENKINS-20196) Failed to connect to URL (status = 404)
Mark Waite commented on JENKINS-20196 Failed to connect to URL (status = 404) Is this still an issue with git-plugin 2.0.1 and git-client-plugin 1.6.2? I'm able to insert the bitbucket user name and password into my https URL and it works as expected. I used https://markewaite:mypassw...@bitbucket.org/markewaite/git-client-plugin.git to check that works. 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/groups/opt_out.
[JIRA] [git-client] (JENKINS-20196) Failed to connect to URL (status = 404)
Derek Hansen commented on JENKINS-20196 Failed to connect to URL (status = 404) Same problem on windows. Downgrading to git-client 1.3.0 and git-plugin 1.5.0 worked 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/groups/opt_out.
[JIRA] [git-client] (JENKINS-20196) Failed to connect to URL (status = 404)
Jonathan Brecher commented on JENKINS-20196 Failed to connect to URL (status = 404) Same problem here. Possibly related to JENKINS-20533, JENKINS-19974. 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/groups/opt_out.
