Change cron schedule for container builds
Build Containers / build-and-push (musa) (push) Failing after 56s
Build Containers / build-and-push (vulkan) (push) Failing after 45s
Build Containers / build-and-push (rocm) (push) Failing after 11m36s
Build Containers / build-and-push (intel) (push) Failing after 13m16s
Build Containers / build-and-push (cuda13) (push) Failing after 13m18s
Build Containers / build-and-push (cuda) (push) Failing after 14m56s
Build Containers / build-and-push (cpu) (push) Failing after 14m58s
Build Containers / delete-untagged-containers (push) Failing after 14m58s

Shift the non-unified container builds about 8 hours after the llama.cpp's projects container publishing window. The llama.cpp containers take a few hours to build and publish and 8 hours is expected to be enough time to remain fresh. 

Additionally, add an extra build at 18:00 in case the 12:00 one does not pick things up. The container builds on the llama-swap side are cheap (just injecting llama-swap binary) so it is fine to run them a bit more frequently.
This commit is contained in:
Benson Wong
2026-06-04 11:00:43 -07:00
committed by GitHub
parent 29d3d9ba20
commit ddfae90b19
+2 -2
View File
@@ -2,10 +2,10 @@ name: Build Containers
on:
# time has no specific meaning, trying to time it after
# the llama.cpp daily packages are published
# the llama.cpp daily packages have time to build and publish (~8hr after llama.cpp project's cron)
# https://github.com/ggml-org/llama.cpp/blob/master/.github/workflows/docker.yml
schedule:
- cron: "37 5 * * *"
- cron: "00 12,18 * * *"
# Allows manual triggering of the workflow
workflow_dispatch: