[JIRA] (JENKINS-17219) HTTPS URLs to Git repositories fail with 1.3.0
Nicolas De Loof resolved JENKINS-17219 as Won't Fix HTTPS URLs to Git repositories fail with 1.3.0 git indeed seems to handle both, according to http://stackoverflow.com/questions/11068576/why-do-some-repository-urls-end-in-git-while-others-dont as github gives you URL to be used to connect repository that includes this extension, I'd prefer to close this issue, as I can't really investigate much JGit internals to know how to add support for this. Change By: Nicolas De Loof (16/Mar/13 9:12 PM) Status: Open Resolved Resolution: Won't Fix 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] (JENKINS-17219) HTTPS URLs to Git repositories fail with 1.3.0
Kevin Fleming commented on JENKINS-17219 HTTPS URLs to Git repositories fail with 1.3.0 GitHub (and in my experience, Git in general) does not require the '.git' suffix, and I've been using these URLs for quite some time with no issue. I changed them to use the Git protocol (s/https/git/) and they work fine this morning, still without the .git suffix. I suppose it is possible that something changed on the GitHub end around the same time I upgraded the Git plugin, so I saw an unfortunate coincidence. If it's working in your testing, feel free to close this 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/groups/opt_out.
[JIRA] (JENKINS-17219) HTTPS URLs to Git repositories fail with 1.3.0
Nicolas De Loof commented on JENKINS-17219 HTTPS URLs to Git repositories fail with 1.3.0 didn't you just missed the ".git" in repository URL https://github.com/bloomberg/ci-slave-recipes.git ? https://github.com/bloomberg/ci-slave-recipes/info/refs?service=git-upload-pack indeed doesn't exist, but https://github.com/bloomberg/ci-slave-recipes.git/info/refs?service=git-upload-pack is 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/groups/opt_out.
[JIRA] (JENKINS-17219) HTTPS URLs to Git repositories fail with 1.3.0
Nicolas De Loof commented on JENKINS-17219 HTTPS URLs to Git repositories fail with 1.3.0 I just tried to reproduce this issue, setting a jenkins instance to build https://github.com/bloomberg/ci-slave-recipes.git, and fetch is working fine. Can you please describe your installation ? 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] (JENKINS-17219) HTTPS URLs to Git repositories fail with 1.3.0
Kevin Fleming created JENKINS-17219 HTTPS URLs to Git repositories fail with 1.3.0 Issue Type: Bug Assignee: Nicolas De Loof Components: git Created: 14/Mar/13 9:40 PM Description: After upgrading to 'Jenkins Git Plugin' version 1.3.0, my jobs that specify an HTTPS URL to GitHub fail to clone the repository; changing the URL to the Git protocol solves the issue. The error produced with an HTTPS URL is this: git version 1.7.9.5 ERROR: Problem fetching from origin / origin - could be unavailable. Continuing anyway hudson.plugins.git.GitException: org.eclipse.jgit.api.errors.InvalidRemoteException: Invalid remote: origin at org.jenkinsci.plugins.gitclient.JGitAPIImpl.fetch(JGitAPIImpl.java:212) at hudson.plugins.git.GitAPI.fetch(GitAPI.java:230) at hudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:793) at hudson.plugins.git.GitSCM.access$000(GitSCM.java:57) at hudson.plugins.git.GitSCM$2.invoke(GitSCM.java:1018) at hudson.plugins.git.GitSCM$2.invoke(GitSCM.java:942) at hudson.FilePath.act(FilePath.java:865) at hudson.FilePath.act(FilePath.java:838) at hudson.plugins.git.GitSCM.determineRevisionToBuild(GitSCM.java:942) at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1101) at hudson.model.AbstractProject.checkout(AbstractProject.java:1353) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:683) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:88) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:588) at hudson.model.Run.execute(Run.java:1567) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:237) Caused by: org.eclipse.jgit.api.errors.InvalidRemoteException: Invalid remote: origin at org.eclipse.jgit.api.FetchCommand.call(FetchCommand.java:134) at org.jenkinsci.plugins.gitclient.JGitAPIImpl.fetch(JGitAPIImpl.java:208) ... 17 more Caused by: org.eclipse.jgit.errors.NoRemoteRepositoryException: https://github.com/bloomberg/ci-slave-recipes: https://github.com/bloomberg/ci-slave-recipes/info/refs?service=git-upload-pack not found at org.eclipse.jgit.transport.TransportHttp.connect(TransportHttp.java:465) at org.eclipse.jgit.transport.TransportHttp.openFetch(TransportHttp.java:305) at org.eclipse.jgit.transport.FetchProcess.executeImp(FetchProcess.java:136) at org.eclipse.jgit.transport.FetchProcess.execute(FetchProcess.java:122) at org.eclipse.jgit.transport.Transport.fetch(Transport.java:1104) at org.eclipse.jgit.api.FetchCommand.call(FetchCommand.java:128) ... 18 more ERROR: Could not fetch from any repository FATAL: Could not fetch from any repository hudson.plugins.git.GitException: Could not fetch from any repository at hudson.plugins.git.GitSCM$2.invoke(GitSCM.java:1023) at hudson.plugins.git.GitSCM$2.invoke(GitSCM.java:942) at hudson.FilePath.act(FilePath.java:865) at hudson.FilePath.act(FilePath.java:838) at hudson.plugins.git.GitSCM.determineRevisionToBuild(GitSCM.java:942) at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1101) at hudson.model.AbstractProject.checkout(AbstractProject.java:1353) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:683) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:88) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:588) at hudson.model.Run.execute(Run.java:1567) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:237) Project: Jenkins Priority: Major Reporter: Kevin Fleming
