|author||Jose Fonseca <email@example.com>||2016-01-24 18:33:58 +0000|
|committer||Jose Fonseca <firstname.lastname@example.org>||2016-02-03 19:37:19 +0000|
appveyor: Bump shallow clone depth.
To prevent build failures when a large patch series is committed, like happened in https://ci.appveyor.com/project/jrfonseca-fdo/mesa/build/322 due to 10 commits between dac2964f3ebd96d5ac227984ab0cd79c2c3b2a1a and 6f428328d34bed16edb8709e4a117eb710d7893d where submitted before the build slave started the git clone. 100 commits should be bigger than any patch series seen in practice, and it takes practically the same time to download as 5 commits. Reviewed-by: Roland Scheidegger <email@example.com>
Diffstat (limited to 'appveyor.yml')
1 files changed, 9 insertions, 2 deletions
diff --git a/appveyor.yml b/appveyor.yml
index 68cc368a3a1..bf7ac752857 100644
@@ -6,7 +6,7 @@
# - Select Git and fill in the Git clone URL
# - Setup a Git hook as explained in
-# - Check 'Settings > General > Skip branches without appveyor'
+# - Check 'Settings > General > Skip branches without appveyor.yml'
# - Check 'Settings > General > Rolling builds'
# - Setup the global or project notifications to your liking
@@ -24,7 +24,14 @@ branches:
+# Don't download the full Mesa history to speed up cloning. However the clone
+# depth must not be too small, otherwise builds might fail when lots of patches
+# are committed in succession, because the desired commit is not found on the
+# truncated history.
+# See also:
+# - https://www.appveyor.com/blog/2014/06/04/shallow-clone-for-git-repositories