![]() |
|
|
|
|
Change By:
|
Greg MacDonald
(06/Aug/14 10:46 PM)
|
|
Description:
|
I've setup a local reference repo using "git clone --mirror <url>", and entered the directory correctly in "Path of the reference repo to use during clone" in under the advanced clone options. But my clones are still taking
15 minutes
awhile
and I'm not getting any indication that reference repository is being used in the console output. I was expecting something like git clone --reference. I've tried it with and without the shallow clone setting and it appears to behave the same.
Either this is broken or there's no indication that it's working. The gui help says that if it can't find the directory it fails silently. I would much rather have an error so I know it's working or not.
Here's the console output, I can see it's doing the shallow clone but not the reference.
{code}
Cloning the remote Git repository
Using shallow clone
Cloning repository g...@github.com:foobar/ThirdParty.git
> git init c:\jenkins\jobs\SharedThirdParty\workspace # timeout=120
Fetching upstream changes from g...@github.com:foobar/ThirdParty.git
> git --version # timeout=120
> git fetch --tags --progress g...@github.com:foobar/ThirdParty.git +refs/heads/*:refs/remotes/origin/* --depth=1
> git config remote.origin.url g...@github.com:foobar/ThirdParty.git # timeout=120
> git config remote.origin.fetch +refs/heads/*:refs/remotes/origin/* # timeout=120
> git config remote.origin.url g...@github.com:foobar/ThirdParty.git # timeout=120
Fetching upstream changes from g...@github.com:foobar/ThirdParty.git
> git fetch --tags --progress g...@github.com:foobar/ThirdParty.git +refs/heads/*:refs/remotes/origin/*
> git rev-parse "origin/master^{commit}" # timeout=120
Checking out Revision 24b28fd7a27a13ca8c6b184c1aded3604a0e7f00 (origin/master)
> git config core.sparsecheckout # timeout=120
> git checkout -f 24b28fd7a27a13ca8c6b184c1aded3604a0e7f00
> git rev-list 24b28fd7a27a13ca8c6b184c1aded3604a0e7f00 # timeout=120
{code}
|
|
|
|
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.
