lets try CI

AztecProtocol · Sep 25, 2024 · 09d85a7 · 09d85a7
1 parent fa75d27
commit 09d85a7
Show file tree

Hide file tree

Showing 2 changed files with 8 additions and 2 deletions.
diff --git a/.github/workflows/ci.yml b/.github/workflows/ci.yml
@@ -170,7 +170,10 @@ jobs:
       - uses: ./.github/ci-setup-action
         with:
           concurrency_key: build-cache-tool-tests
-      - name: "Build Cache Tool Tests"
+      - name: "Build Cache Tool Correctness Tests"
+        timeout-minutes: 5
+        run: earthly-ci --no-output ./build-system/cache-tool/+test
+      - name: "Build Cache Tool Connectivity Tests"
         timeout-minutes: 5
         run: earthly-ci --no-output ./build-system/cache-tool/+test
 

diff --git a/scripts/earthly-ci b/scripts/earthly-ci
@@ -33,7 +33,10 @@ function wipe_non_cache_docker_state {
 }
 
 EARTHLY_RUN_STATS_JSON="earthly-run-stats.json"
-EARTHLY_ARGS="--logstream-debug-manifest-file $EARTHLY_RUN_STATS_JSON --secret AWS_ACCESS_KEY_ID=${AWS_ACCESS_KEY_ID:-} --secret AWS_SECRET_ACCESS_KEY=${AWS_SECRET_ACCESS_KEY:-} --secret AZTEC_BOT_COMMENTER_GITHUB_TOKEN=${AZTEC_BOT_GITHUB_TOKEN:-}"
+# Run earthly with our necesary secrets initialized
+# AWS credentials can be blank, only the odd test like build-system/cache-tool/+test need them
+# everything else relies on AZTEC_CACHE_TOOL_IP being set.
+EARTHLY_ARGS="--logstream-debug-manifest-file $EARTHLY_RUN_STATS_JSON --secret AWS_ACCESS_KEY_ID=${AWS_ACCESS_KEY_ID:-} --secret AZTEC_CACHE_TOOL_IP=$(hostname -I | awk '{print $1}') --secret AWS_SECRET_ACCESS_KEY=${AWS_SECRET_ACCESS_KEY:-} --secret AZTEC_BOT_COMMENTER_GITHUB_TOKEN=${AZTEC_BOT_GITHUB_TOKEN:-}"
 
 function print_earthly_command_timings() {
   jq --version >/dev/null || return