Repository navigation
chunk workflows: export the runner's oci_cache as OCI_PROXY - #83
Conversation
Same as armbian/actions runner-clean: the build framework reads a pull-through OCI cache from OCI_PROXY (armbian/build#10860); GHCR_MIRROR_ADDRESS alone did nothing. Signed-off-by: Igor Pecovnik <igor@armbian.com>
|
Navigate logical layers of code changes, visualize relationships, and explore their blast radius. No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Advanced Run ID: 📒 Files selected for processing (2)
Included review availability: This review used your included allowance. Your plan provides up to 1 included review per hour; 0 remain after this review. WalkthroughBoth chunk workflows now map the Priority: ⬇️ Low Estimated code review effort: 2 (Simple) | ~5 minutes Change: Bug fix Merge Risk: ⚪ Minimal · up to The workflow mapping is correctly handed to the build step; compatibility with the selected external build revision should be covered by normal integration validation. Architecture SummaryArchitecture risk: 🔵 Low · up to The changed surface does not map to a changed system, dependency edge, entrypoint, or external dependency. Changed systems: None identified. Architecture concerns Review detailsBefore / after behavior
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ 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 |
Goal: CI builds use the runner's OCI cache.
Export the runner's
oci_cacheasOCI_PROXYinstead ofGHCR_MIRROR_ADDRESS. The build ignoredGHCR_MIRROR_ADDRESSwithoutGHCR_MIRROR=dockerproxy.oci_cacheset.