Skip to content

ci: add scheduled cache-warm workflow for BST remote cache - #787

Merged
castrojo merged 1 commit into
mainfrom
ci/phase7-cache-warm-v2
Jun 10, 2026
Merged

ci: add scheduled cache-warm workflow for BST remote cache#787
castrojo merged 1 commit into
mainfrom
ci/phase7-cache-warm-v2

Conversation

@castrojo

Copy link
Copy Markdown
Contributor

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
  • || true on build — warming is best-effort, failure doesn't block anything
  • Checks out testing branch — builds live content, not stale main
  • oci/bluefin.bst — correct top-level build target per Justfile
  • Includes Restore + Save cache steps for GitHub Actions cache layer

Supersedes #785 (clean branch from main, no conflicts).

Assisted-by: Claude Sonnet 4.5 via pi

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
@castrojo
castrojo requested review from p5 and tulilirockz as code owners June 10, 2026 23:45
@coderabbitai

coderabbitai Bot commented Jun 10, 2026

Copy link
Copy Markdown

Warning

Review limit reached

@castrojo, we couldn't start this review because you've reached your PR review rate limit.

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 @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

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 configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: b7a8d866-7c79-4656-8afe-43cb314d5d0e

📥 Commits

Reviewing files that changed from the base of the PR and between 5377a93 and a9afaad.

📒 Files selected for processing (1)
  • .github/workflows/cache-warm.yml
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch ci/phase7-cache-warm-v2

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.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@github-actions

Copy link
Copy Markdown
Contributor

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 lint

If 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
```

@castrojo
castrojo merged commit eda419a into main Jun 10, 2026
22 checks passed
@castrojo
castrojo deleted the ci/phase7-cache-warm-v2 branch June 10, 2026 23:47
@castrojo castrojo added 4-review A pull request is awaiting review. and removed pr/needs-review labels Jul 29, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

4-review A pull request is awaiting review.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant