Skip to content

armgit / floci

Public Imported from GitHub
0

Light, fluffy, and always free - The AWS Local Emulator alternative

ci: align the nightly schedule on 23:00 America/Chicago (#2862)

Hector Ventura2b4f39e4e631
diff --git a/.github/workflows/nightly.yml b/.github/workflows/nightly.yml
index 8029b40033..f0bcb68eb1 100644
--- a/.github/workflows/nightly.yml
+++ b/.github/workflows/nightly.yml
@@ -1,7 +1,9 @@
name: Nightly
# Builds and publishes native images from the tip of main as nightly Docker tags.
-# Runs every night at 22:00 CT (03:00 UTC, approximate — shifts 1 h in CST winter).
+# Runs every night at 23:00 America/Chicago (04:00 UTC in CDT, 05:00 UTC in CST).
+# GitHub may delay scheduled runs on low-activity repositories; observed delays on this
+# org have reached several hours. The schedule is a target, not a guarantee.
# Can also be triggered manually.
#
# Published tags:
@@ -38,7 +40,7 @@ jobs:
id: date
run: echo "version=$(TZ='America/Chicago' date +'%m%d%Y')" >> "$GITHUB_OUTPUT"
- # ── Build native artifact — amd64 ────────────────────────────────────────
+ # ── Build native artifact: amd64 ─────────────────────────────────────────
build-native-amd64:
name: Build native artifact (amd64)
needs: prepare
@@ -54,7 +56,7 @@ jobs:
with:
java-version: '25'
distribution: 'mandrel'
- # no `cache: maven` — it could never hit here. Its restore hashes the
+ # no `cache: maven`, since it could never hit here. Its restore hashes the
# pristine pom.xml, but its post-job save runs *after* `versions:set`
# below has rewritten that pom, so the two keys never match. Worse, the
# nightly version embeds the date, so the save key changed every night:
@@ -64,7 +66,7 @@ jobs:
# Restore-only, keyed identically to ci.yml so this reads the ~/.m2 that
# ci.yml's shard 1 saves on every push to main. This job checks out `ref:
- # main`, so the pristine pom hashed here matches the one ci.yml hashed —
+ # main`, so the pristine pom hashed here matches the one ci.yml hashed,
# and restoring before `versions:set` keeps it that way. Nothing is saved:
# ci.yml is the single writer, and a save here would recreate the mutated-
# key garbage described above.
@@ -90,7 +92,7 @@ jobs:
if-no-files-found: warn
retention-days: 1
- # ── Build native artifact — arm64 ────────────────────────────────────────
+ # ── Build native artifact: arm64 ─────────────────────────────────────────
build-native-arm64:
name: Build native artifact (arm64)
needs: prepare
@@ -106,7 +108,7 @@ jobs:
with:
java-version: '25'
distribution: 'mandrel'
- # no `cache: maven` — it could never hit here. Its restore hashes the
+ # no `cache: maven`, since it could never hit here. Its restore hashes the
# pristine pom.xml, but its post-job save runs *after* `versions:set`
# below has rewritten that pom, so the two keys never match. Worse, the
# nightly version embeds the date, so the save key changed every night:
@@ -116,7 +118,7 @@ jobs:
# Restore-only, keyed identically to ci.yml so this reads the ~/.m2 that
# ci.yml's shard 1 saves on every push to main. This job checks out `ref:
- # main`, so the pristine pom hashed here matches the one ci.yml hashed —
+ # main`, so the pristine pom hashed here matches the one ci.yml hashed,
# and restoring before `versions:set` keeps it that way. Nothing is saved:
# ci.yml is the single writer, and a save here would recreate the mutated-
# key garbage described above.