From: Michal Nowak <mnowak@isc.org>
Date: Mon, 7 Nov 2022 16:50:10 +0000 (+0100)
Subject: Verify Git repo validity
X-Git-Tag: v9.19.8~62^2
X-Git-Url: http://git.ipfire.org/gitweb/?a=commitdiff_plain;h=be83e203cec9e1b70392ffc6e293f90c92d77624;p=thirdparty%2Fbind9.git

Verify Git repo validity

This check should help catching issues like [1] early.

[1] https://gitlab.isc.org/isc-projects/bind9/-/wikis/%22main%22-branch-partial-history-rewrite-in-August-2022
---

diff --git a/.gitlab-ci.yml b/.gitlab-ci.yml
index 8ca368d0f95..dffb57e0b7b 100644
--- a/.gitlab-ci.yml
+++ b/.gitlab-ci.yml
@@ -1408,6 +1408,22 @@ stress:rpz:freebsd12:amd64:
     variables:
       - $CI_COMMIT_TAG || ($BIND_STRESS_TEST_OS =~ /freebsd/i && $BIND_STRESS_TEST_MODE =~ /rpz/i && $BIND_STRESS_TEST_ARCH =~ /amd64/i)
 
+# git fsck operates over the whole repository and is sufficient to schedule it
+# only in one branch, preferably "main". GitLab's clone strategy prevents us
+# from using the "bind9" repo clone; we need to clone it ourselves.
+fsck:
+  <<: *base_image
+  stage: postcheck
+  variables:
+    GIT_STRATEGY: none
+  script:
+    - git clone https://gitlab.isc.org/isc-projects/bind9.git bind9-full-clone
+    - cd bind9-full-clone/
+    - git fsck
+  only:
+    - schedules
+  needs: []
+
 gcov:
   <<: *base_image
   <<: *default_triggering_rules