tag:help.appveyor.com,2012-11-13:/discussions/problems/2479-default-depth50-instead-of-the-whole-commit-historyAppVeyor: Discussion 2018-10-19T08:17:19Ztag:help.appveyor.com,2012-11-13:Comment/373700662015-07-13T16:02:41Z2015-07-13T16:02:41ZDefault -depth=50 instead of the whole commit history<div><p>Will fix that later today.</p>
<ul>
<li>Feodor</li>
</ul></div>Feodor Fitsnertag:help.appveyor.com,2012-11-13:Comment/373700662015-07-13T18:37:27Z2015-07-13T18:37:27ZDefault -depth=50 instead of the whole commit history<div><p>Did some other stuff change with the default clone command? I'm
also having issues building a repo that worked fine last week. My
last succesful build had this:</p>
<p>git clone -q --branch=master <a>git://github.com/daveaglick/daveaglick.git</a>
C:\projects\daveaglick</p>
<p>But now the clone looks like this:</p>
<p>git clone -q --depth=50 --branch=master <a href="https://github.com/daveaglick/daveaglick.git">https://github.com/daveaglick/daveaglick.git</a>
C:\projects\daveaglick</p></div>davetag:help.appveyor.com,2012-11-13:Comment/373700662015-07-13T18:44:35Z2015-07-13T18:44:35ZDefault -depth=50 instead of the whole commit history<div><p>Protocol changed from <code>git</code> to <code>https</code> as
it adds security (though I don't think this could be an issue).
Other than that nothing changed besides depth. You've been running
on a new environment since June 27.</p></div>Feodor Fitsnertag:help.appveyor.com,2012-11-13:Comment/373700662015-07-13T18:50:07Z2015-07-13T18:50:07ZDefault -depth=50 instead of the whole commit history<div><p>Thanks - I also wouldn't think the protocol change would make a
difference. Just notice it and was wondering if anything else
changed.</p>
<p>I run some git commands in my build script (specifically, I
check out the "gh-pages" branch) and was getting confusing errors
about the branch not existing (though it does). I suspect that if
it was created prior to the current depth of 50, that might be the
culprit.</p>
<p>I'll sit tight until the fix for depth is in and try it again.
Thanks for the quick response.</p></div>davetag:help.appveyor.com,2012-11-13:Comment/373700662015-07-13T18:50:38Z2015-07-13T18:50:38ZDefault -depth=50 instead of the whole commit history<div><p>Thanks, Feodor!</p></div>filiptag:help.appveyor.com,2012-11-13:Comment/373700662015-07-14T02:44:00Z2015-07-14T02:44:00ZDefault -depth=50 instead of the whole commit history<div><p>OK, the fix has been deployed.</p></div>Feodor Fitsnertag:help.appveyor.com,2012-11-13:Comment/373700662015-07-14T11:50:10Z2015-07-14T11:50:10ZDefault -depth=50 instead of the whole commit history<div><p>Thank you very much, Feodor! Default depth value now works fine,
but now AppVeyor cannot recognize Entity Framework references. Is
that a bug?<br>
<a href="https://ci.appveyor.com/project/gius/def/build/0.2.0-unstable.73+73%20(Build%2059)">
https://ci.appveyor.com/project/gius/def/build/0.2.0-unstable.73+73...</a></p></div>filiptag:help.appveyor.com,2012-11-13:Comment/373700662015-07-14T13:16:19Z2015-07-14T13:16:19ZDefault -depth=50 instead of the whole commit history<div><p>Might be NuGet.org availability hiccups. Use cache to reduce
dependency on <a>
that: http://www.appveyor.com/docs/nuget#dealing-with-intermittent-...</a></p>
<ul>
<li>Feodor</li>
</ul></div>Feodor Fitsnertag:help.appveyor.com,2012-11-13:Comment/373700662015-07-14T13:50:08Z2015-07-14T13:50:08ZDefault -depth=50 instead of the whole commit history<div><p>FYI - fixing the depth resolved my own issue. Once again,
thanks!</p></div>davetag:help.appveyor.com,2012-11-13:Comment/373700662015-07-14T14:38:20Z2015-07-14T14:38:20ZDefault -depth=50 instead of the whole commit history<div><p>I tried to re-run the build after a few hours and it seems to
have fixed itself (or someone else at AppVeyor fixed it). :) Thanks
again! Closing this thread.</p></div>filip