ci: add scheduled cache-warm workflow for BST remote cache - #785
ci: add scheduled cache-warm workflow for BST remote cache#785castrojo wants to merge 7 commits into
Conversation
* docs(skills): add ci.md lessons from PR 751 testing fast-forward and next stream (#752) - Document GitHub API 422 idempotent fast-forward pattern - Document merge-queue head_branch never equals 'main' - Document :next/:btw as fully automated rolling stream (no human gate) Assisted-by: Claude Sonnet 4.6 via GitHub Copilot * chore(deps): update common: v2026.06-169 -> v2026.06-186 * ci: trigger Build Bluefin dakota on testing branch [skip build] PR base changed to testing — re-trigger CI so renovate-automerge fires. Assisted-by: Claude Sonnet 4.6 via pi * ci: re-trigger CI (build.yml now includes testing branch) Assisted-by: Claude Sonnet 4.6 via pi --------- Co-authored-by: Jorge O. Castro <jorge.castro@gmail.com> Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Match bluefin-lts behavior — every Renovate/track-bst merge to testing fires a build so testing images stay current. Assisted-by: Claude Sonnet 4.6 via pi
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
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 360-min timeout; full GNOME stack rebuild from scratch can exceed 6h on cache miss after junction ref bumps. Closes automation-audit ND1 (cold-start timeout non-determinism). Assisted-by: Claude Sonnet 4.5 via pi
|
Warning Review limit reached
More reviews will be available in 12 minutes and 15 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 (5)
✨ 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 |
|
This PR targets |
…ments/layers/top.bst The initial version referenced a non-existent path. Correct target per build.yml and Justfile is `oci/bluefin.bst`. Also bump timeout from 360 to 420 min to match the build job timeout. Assisted-by: Claude Sonnet 4.5 via pi
|
Superseded by clean branch from main. |
castrojo
added
4-review
1 participant
Summary
Automation audit Phase 7: scheduled workflow to keep the BuildStream remote cache hot.
Addresses ND1 (cold-start timeout non-determinism) from the automation audit.
Problem: Dakota BST builds have a 360-min timeout. When cache misses after junction ref bumps or gbm upstream rebuilds, the full GNOME stack must rebuild from scratch — which can exceed 6h.
Solution: Schedule a cache-warm build Mon/Thu at 06:00 UTC to keep artifacts fresh before typical work-hour PR merge windows.
Behavior:
workflow_dispatchfor manual warmcancel-in-progress: false— cache warm should complete even if a newer one starts|| true) — this is warming, not gatingAssisted-by: Claude Sonnet 4.5 via pi