Fredric Lonngren edited a comment on Bug JENKINS-17055

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.
 
 

Reply via email to