[JIRA] (JENKINS-17055) Git 1.2: only one remote is actually added
Nicolas De Loof resolved JENKINS-17055 as Fixed Git 1.2: only one remote is actually added Change By: Nicolas De Loof (16/Mar/13 9:42 PM) 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] (JENKINS-17055) Git 1.2: only one remote is actually added
Tomasz Bartczak commented on JENKINS-17055 Git 1.2: only one remote is actually added @Frederic Lonngren you're right the problem is on fetch. I see that the problem on fetch has its root cause in not having a Remote Git defined. Making Jenkins clone all remotes may be not very effective, but ensures remotes are added. I don't know why they are not added. In normal flow they should be added https://github.com/jenkinsci/git-plugin/blob/master/src/main/java/hudson/plugins/git/GitSCM.java#L792 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-17055) Git 1.2: only one remote is actually added
Tomasz Bartczak edited a comment on JENKINS-17055 Git 1.2: only one remote is actually added @Fredric Lonngren you're right the problem is on fetch. I see that the problem on fetch has its root cause in not having a Remote Git defined. Making Jenkins clone all remotes may be not very effective, but ensures remotes are added. I don't know why they are not added. In normal flow they should be added https://github.com/jenkinsci/git-plugin/blob/master/src/main/java/hudson/plugins/git/GitSCM.java#L792 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-17055) Git 1.2: only one remote is actually added
Fredric Lonngren commented on JENKINS-17055 Git 1.2: only one remote is actually added I got my error at fetch, not clone. I keep my workspace between builds and let git do a clean, so no need for cloning. From my 1.2.0-output above I get the log-output Fetching changes from 2 remote Git repositories @ https://github.com/jenkinsci/git-plugin/blob/master/src/main/java/hudson/plugins/git/GitSCM.java#L966 and then goes into the fetch for-loop @ https://github.com/jenkinsci/git-plugin/blob/master/src/main/java/hudson/plugins/git/GitSCM.java#L971 where I for the second repo get the error-output ERROR: Problem fetching from tcm_repo / tcm_repo - could be unavailable. Continuing anyway stacktrace @ https://github.com/jenkinsci/git-plugin/blob/master/src/main/java/hudson/plugins/git/GitSCM.java#L796 . 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-17055) Git 1.2: only one remote is actually added
Tomasz Bartczak
edited a comment on JENKINS-17055
Git 1.2: only one remote is actually added
I have the same issue - Ubuntu 12.04, Jenkins 1.504, Git 1.2.0
When I specify two remotes, only one gets cloned, and I get an error on git fetch.
I looked at the code and I think the problem is here:
GitSCM.java starting line 993
for (RemoteConfig rc : repos) {
final String expandedReference = environment.expand(reference);
try {
git.clone(rc.getURIs().get(0).toPrivateString(), rc.getName(), useShallowClone, expandedReference);
successfullyCloned = true;
break;
the last break stops cloning next repo after first succesfull clone of any repo.
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-17055) Git 1.2: only one remote is actually added
lemmster commented on JENKINS-17055 Git 1.2: only one remote is actually added I can confirm that removing the break stmt fixes the issue for me. 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-17055) Git 1.2: only one remote is actually added
Fredric Lonngren commented on JENKINS-17055 Git 1.2: only one remote is actually added I have the same issue using two remote repos. First one works, second fails. Both are using ssh. Works with 1.1.26: Building in workspace /local/hudson-build/workspace/TCM_Builds_beta Checkout:TCM_Builds_beta / /local/hudson-build/workspace/TCM_Builds_beta - hudson.remoting.LocalChannel@1d0540c Using strategy: Default Last Built Revision: Revision 900242706776d7f77f28da58bc33d0a88fd3d764 (origin/foo_dev) Fetching changes from [org.eclipse.jgit.transport.RemoteConfig@35cf9c, org.eclipse.jgit.transport.RemoteConfig@d1258b] remote Git repositories Fetching upstream changes from ssh://iptcm-git.epk.ericsson.se:29418/foo-bar-dev/bar-team Fetching upstream changes from ssh://iptcm-git.epk.ericsson.se:29418/tcm/builds Seen branch in repository origin/HEAD Not working with 1.2.0 Building in workspace /local/hudson-build/workspace/TCM_Builds_beta Checkout:TCM_Builds_beta / /local/hudson-build/workspace/TCM_Builds_beta - hudson.remoting.LocalChannel@d53153 Using strategy: Default Last Built Revision: Revision e55cce57f3e954e5e554014f0ba64fa45ed70acb (origin/foo_dev) Fetching changes from 2 remote Git repositories Fetching upstream changes from origin Fetching upstream changes from tcm_repo ERROR: Problem fetching from tcm_repo / tcm_repo - could be unavailable. Continuing anyway hudson.plugins.git.GitException: Command "git fetch -t tcm_repo +refs/heads/*:refs/remotes/tcm_repo/*" returned status code 128: stdout: stderr: fatal: 'tcm_repo' does not appear to be a git repository fatal: Could not read from remote repository. 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-17055) Git 1.2: only one remote is actually added
Fredric Lonngren edited a comment on JENKINS-17055 Git 1.2: only one remote is actually added I have the same issue using two remote repos. First one works, second fails. Both are using ssh. Works with 1.1.26: Building in workspace /local/hudson-build/workspace/TCM_Builds_beta Checkout:TCM_Builds_beta / /local/hudson-build/workspace/TCM_Builds_beta - hudson.remoting.LocalChannel@1d0540c Using strategy: Default Last Built Revision: Revision 900242706776d7f77f28da58bc33d0a88fd3d764 (origin/foo_dev) Fetching changes from [org.eclipse.jgit.transport.RemoteConfig@35cf9c, org.eclipse.jgit.transport.RemoteConfig@d1258b] remote Git repositories Fetching upstream changes from ssh://iptcm-git.epk.ericsson.se:29418/foo-bar-dev/bar-team Fetching upstream changes from ssh://iptcm-git.epk.ericsson.se:29418/tcm/builds Seen branch in repository origin/HEAD Not working with 1.2.0 Building in workspace /local/hudson-build/workspace/TCM_Builds_beta Checkout:TCM_Builds_beta / /local/hudson-build/workspace/TCM_Builds_beta - hudson.remoting.LocalChannel@d53153 Using strategy: Default Last Built Revision: Revision e55cce57f3e954e5e554014f0ba64fa45ed70acb (origin/foo_dev) Fetching changes from 2 remote Git repositories Fetching upstream changes from origin Fetching upstream changes from tcm_repo ERROR: Problem fetching from tcm_repo / tcm_repo - could be unavailable. Continuing anyway hudson.plugins.git.GitException: Command "git fetch -t tcm_repo +refs/heads/*:refs/remotes/tcm_repo/*" returned status code 128: stdout: stderr: fatal: 'tcm_repo' does not appear to be a git repository fatal: Could not read from remote repository. Back on 1.1.26 for now. 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-17055) Git 1.2: only one remote is actually added
Fredric Lonngren edited a comment on JENKINS-17055 Git 1.2: only one remote is actually added I have the same issue using two remote repos. First one works, second fails. Both are using ssh. Works with 1.1.26: Building in workspace /local/hudson-build/workspace/TCM_Builds_beta Checkout:TCM_Builds_beta / /local/hudson-build/workspace/TCM_Builds_beta - hudson.remoting.LocalChannel@1d0540c Using strategy: Default Last Built Revision: Revision 900242706776d7f77f28da58bc33d0a88fd3d764 (origin/foo_dev) Fetching changes from [org.eclipse.jgit.transport.RemoteConfig@35cf9c, org.eclipse.jgit.transport.RemoteConfig@d1258b] remote Git repositories Fetching upstream changes from ssh://iptcm-git.epk.ericsson.se:29418/foo-bar-dev/bar-team Fetching upstream changes from ssh://iptcm-git.epk.ericsson.se:29418/tcm/builds Seen branch in repository origin/HEAD Not working with 1.2.0 Building in workspace /local/hudson-build/workspace/TCM_Builds_beta Checkout:TCM_Builds_beta / /local/hudson-build/workspace/TCM_Builds_beta - hudson.remoting.LocalChannel@d53153 Using strategy: Default Last Built Revision: Revision e55cce57f3e954e5e554014f0ba64fa45ed70acb (origin/foo_dev) Fetching changes from 2 remote Git repositories Fetching upstream changes from origin Fetching upstream changes from tcm_repo ERROR: Problem fetching from tcm_repo / tcm_repo - could be unavailable. Continuing anyway hudson.plugins.git.GitException: Command "git fetch -t tcm_repo +refs/heads/*:refs/remotes/tcm_repo/*" returned status code 128: stdout: stderr: fatal: 'tcm_repo' does not appear to be a git repository fatal: Could not read from remote repository. Please make sure you have the correct access rights and the repository exists. at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:772) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommand(CliGitAPIImpl.java:738) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.fetch(CliGitAPIImpl.java:159) at hudson.plugins.git.GitSCM$2.invoke(GitSCM.java:1023) at hudson.plugins.git.GitSCM$2.invoke(GitSCM.java:941) at hudson.FilePath.act(FilePath.java:865) at hudson.FilePath.act(FilePath.java:838) at hudson.plugins.git.GitSCM.determineRevisionToBuild(GitSCM.java:941) at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1113) and-so-on Back on 1.1.26 for now. 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-17055) Git 1.2: only one remote is actually added
Tomasz Bartczak
commented on JENKINS-17055
Git 1.2: only one remote is actually added
I have the same issue - Ubuntu 12.04, Jenkins 1.504, Git 1.2.0
When I specify two remotes, only one gets cloned, and I get an error on git fetch.
I looked at the code and I think the problem is here:
GitSCM.java starting line 993
for (RemoteConfig rc : repos) {
final String expandedReference = environment.expand(reference);
try {
git.clone(rc.getURIs().get(0).toPrivateString(), rc.getName(), useShallowClone, expandedReference);
successfullyCloned = true;
break;
the last break stops cloning after first succesfull clone of all repos.
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-17055) Git 1.2: only one remote is actually added
acdha created JENKINS-17055 Git 1.2: only one remote is actually added Issue Type: Bug Assignee: Nicolas De Loof Components: git Created: 04/Mar/13 4:44 PM Description: I have a project configured with two remotes. One uses SSH and the other uses HTTPS: ssh://site-u...@platinum.example.org/opt/site https://git.example.org/site.git Both of these work from the command-line (e.g. "git clone …") and both worked with 1.1.26. With 1.2, only the SSH remote is added (e.g. "git remote show" will only list that remote – and it's always the SSH remote, no matter what order I create the remotes in the config. Builds will fail with this error: git --version git version 1.8.1.5 Fetching upstream changes from ssh-remote Fetching upstream changes from https-remote ERROR: Problem fetching from https-remote / https-remote - could be unavailable. Continuing anyway. hudson.plugins.git.GitException: Command "git fetch -t https-remote +refs/heads/*:refs/remotes/https-remote/*" returned status code 128: stdout: stderr: fatal: 'https-remote' does not appear to be a git repository fatal: Could not read from remote repository. Please make sure you have the correct access rights and the repository exists. at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:772) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommand(CliGitAPIImpl.java:738) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.fetch(CliGitAPIImpl.java:160) at hudson.plugins.git.GitSCM$2.invoke(GitSCM.java:1023) at hudson.plugins.git.GitSCM$2.invoke(GitSCM.java:941) at hudson.FilePath.act(FilePath.java:865) at hudson.FilePath.act(FilePath.java:838) at hudson.plugins.git.GitSCM.determineRevisionToBuild(GitSCM.java:941) at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1113) at hudson.model.AbstractProject.checkout(AbstractProject.java:1342) 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) I've reverted back to 1.1.26 for the moment. Environment: Ubuntu 12.04 Project: Jenkins Priority: Major Reporter: acdha 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.
