• Moves Linux Bazel cache writes from RBE to the dedicated cache workflow.
• Uses analysis-only population to reduce cache size and preserve Windows cache retention.

graph TD
  T["Trunk or schedule"] --> G["GitHub Cache"] --> M["OS matrix"] --> L[("Linux cache")]
  M --> A[("macOS cache")]
  M --> W[("Windows cache")]
  R["RBE tests"] -. "restore only" .-> L

Loading

The following are alternative approaches to this PR:

1. Prune the RBE cache before saving

• ➕ Retains browser artifacts during the RBE run
• ➕ Keeps cache production attached to the primary Linux test job
• ➖ Requires selective cleanup of Bazel repository cache contents
• ➖ Adds fragile coupling to Bazel repository layout
• ➖ Still incurs archive and upload overhead in the RBE job

2. Use separate browser and dependency caches

• ➕ Allows independent retention policies for large browser artifacts
• ➕ Could preserve resilience when pinned browser packages disappear upstream
• ➖ Consumes additional GitHub cache quota and keys
• ➖ Requires custom cache partitioning beyond the existing setup-bazel workflow
• ➖ Increases invalidation and maintenance complexity

Recommendation: Use the PR's analysis-only Linux population in the dedicated cache workflow. It aligns cache ownership across operating systems, reduces quota pressure without measurable RBE slowdown, and avoids custom cache-pruning logic.

Other (2) +1 / -2

ci-rbe.ymlStop saving the Linux repository cache from RBE +0/-1

Stop saving the Linux repository cache from RBE

• Removes trunk-only cache saving from the full RBE test job. This prevents pinned browser repositories from producing an oversized Linux cache entry.

.github/workflows/ci-rbe.yml

gh-cache.ymlAdd Ubuntu to repository cache population +1/-1

Add Ubuntu to repository cache population

• Extends the cache-population matrix to Ubuntu alongside macOS and Windows. Linux cache content is now generated by the smaller analysis-only build with browser pinning disabled.

.github/workflows/gh-cache.yml

💡 Did you know, you can tweak Display preferences with a live preview to see your comment before it ships

More tips ↗ | Customize Qodo ↗ | Qodo docs ↗