Fix Buildkite (#40)

Author: Jamie Brynes

.buildkite/hooks/post-checkout

@@ -2,4 +2,11 @@
 set -euo pipefail
 [[ -n "${DEBUG:-}" ]] && set -x
 
-ci/bootstrap.sh
+if [[ -z "${BUILDKITE-}" ]]; then
+  # Local workstations
+  ci/bootstrap.sh
+  exit 0
+fi
+if [[ "${BUILDKITE_AGENT_META_DATA_QUEUE}" != "trigger-pipelines" ]]; then
+  ci/bootstrap.sh
+fi

.buildkite/premerge.steps.yaml

@@ -13,14 +13,20 @@ common: &common
     - "environment=production"
     - "permission_set=builder"
     - "platform=windows"
-    - "queue=v2-1555079572-898096a2a0311231-------z"
+    - "queue=v2-1556548819-32d66bca3227c14a-------z"
   timeout_in_minutes: 60 # TODO(ENG-548): reduce timeout once agent-cold-start is optimised.
   retry:
     automatic:
         # This is designed to trap and retry failures because agent lost connection. Agent exits with -1 in this case.
       - exit_status: -1
         limit: 3
-
+        # This is designed to trap and retry failures because of a buildkite bug.
+      - exit_status: 255
+        limit: 3
+        # Workaround for flaky Git clones, likely due to - https://github.com/PowerShell/Win32-OpenSSH/issues/1322
+      - exit_status: 128
+        limit: 3
+        
 # NOTE: step labels turn into commit-status names like {org}/{repo}/{pipeline}/{step-label}, lower-case and hyphenated.
 # These are then relied on to have stable names by other things, so once named, please beware renaming has consequences.
 

.buildkite/release-qa.steps.yaml

@@ -13,13 +13,19 @@ common: &common
     - "environment=production"
     - "permission_set=builder"
     - "platform=windows"
-    - "queue=v2-1555079572-898096a2a0311231-------z"
+    - "queue=v2-1556548819-32d66bca3227c14a-------z"
   timeout_in_minutes: 60 # TODO(ENG-548): reduce timeout once agent-cold-start is optimised.
   retry:
     automatic:
         # This is designed to trap and retry failures because agent lost connection. Agent exits with -1 in this case.
       - exit_status: -1
         limit: 3
+        # This is designed to trap and retry failures because of a buildkite bug.
+      - exit_status: 255
+        limit: 3
+        # Workaround for flaky Git clones, likely due to - https://github.com/PowerShell/Win32-OpenSSH/issues/1322
+      - exit_status: 128
+        limit: 3
 
 # NOTE: step labels turn into commit-status names like {org}/{repo}/{pipeline}/{step-label}, lower-case and hyphenated.
 # These are then relied on to have stable names by other things, so once named, please beware renaming has consequences.

ci/bootstrap.sh

@@ -12,7 +12,7 @@ if [ -d "${SHARED_CI_DIR}" ]; then
     rm -rf "${SHARED_CI_DIR}"
 fi
 
-git clone "${CLONE_URL}" "${SHARED_CI_DIR}"
+git clone --depth 1 --verbose "${CLONE_URL}" "${SHARED_CI_DIR}"
 
 
 # Clone the GDK for Unity repository
@@ -23,7 +23,12 @@ PINNED_VERSION=$(cat ./gdk.pinned)
 
 rm -rf "${TARGET_DIRECTORY}"
 
-git clone ${CLONE_URI} "${TARGET_DIRECTORY}"
+mkdir "${TARGET_DIRECTORY}"
+
+# Workaround for being unable to clone a specific commit with depth of 1.
 pushd "${TARGET_DIRECTORY}"
+    git init
+    git remote add origin "${CLONE_URI}"
+    git fetch --depth 20 origin develop
     git checkout "${PINNED_VERSION}"
 popd