Improved production Docker image loading in CI#28105
Conversation
The full production image is already pushed to GHCR on trusted CI runs, so loading it back into the local Docker daemon only adds export/import time for optional image reporting. Keep local loading for artifact-based fork runs where downstream jobs need it.
WalkthroughThis PR updates the CI workflow in Possibly related PRs
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches📝 Generate docstrings
🧪 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 |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #28105 +/- ##
==========================================
- Coverage 73.82% 73.81% -0.01%
==========================================
Files 1528 1528
Lines 129417 129417
Branches 15509 15506 -3
==========================================
- Hits 95537 95527 -10
- Misses 32924 32934 +10
Partials 956 956
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
Summary
Why
The full image is already pushed to GHCR on trusted runs. Loading it locally is only needed for artifact transfer/reporting and was adding roughly 45-60s of export/import overhead after BuildKit cache hits.
The skipped reporting is informational only: it runs
docker inspectanddocker historyto write image size and layer details to the GitHub Step Summary. It does not enforce thresholds, alert, or gate CI.Testing