ci: add scheduled cache-warm workflow for BST remote cache - #787
Conversation
Runs Mon/Thu at 06:00 UTC to keep the BuildStream remote cache hot and prevent cold-start timeouts (ND1 from automation audit). BST builds have a 420-min timeout; full GNOME stack rebuild from scratch can exceed 6h on cache miss after junction ref bumps. Build is non-fatal (|| true) — warming is best-effort. Assisted-by: Claude Sonnet 4.5 via pi
|
Warning Review limit reached
More reviews will be available in 6 minutes and 58 seconds. Learn how PR review limits work. Your organization has run out of usage credits. Purchase more in the billing tab. ⌛ How to resolve this issue?After more reviews become available, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans include higher PR review limits than trial, open-source, and free plans. In all cases, reviews become available again over time. During sustained high-volume PR review activity, CodeRabbit may temporarily slow when the next review becomes available. Please see our Fair Usage Limits Policy for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
Thanks for the PR! A maintainer will review it. While you wait, make sure these pass locally: just validate # element graph check
just build default # build the image
just boot-test # confirm the desktop boots (exits 0 = pass)
just lint # bootc container lintIf this PR fixes a bug, add verify steps to the linked issue so users can confirm the fix on their hardware after the next nightly ships: ```verify
ujust <something> # what users should run to confirm the fix
``` |
Summary
Automation audit Phase 7 / ND1: scheduled workflow to keep the BST remote cache hot.
Problem: Dakota BST builds have a 420-min timeout. Full GNOME stack rebuild from scratch after junction ref bumps can exceed 6h.
Solution: Schedule Mon/Thu 06:00 UTC cache-warm build to keep artifacts fresh before typical work-hour PR windows.
Key choices:
cancel-in-progress: false— let cache warm complete even if newer run starts|| trueon build — warming is best-effort, failure doesn't block anythingtestingbranch — builds live content, not stale mainoci/bluefin.bst— correct top-level build target per JustfileSupersedes #785 (clean branch from main, no conflicts).
Assisted-by: Claude Sonnet 4.5 via pi