ci: publish oci image outside of parallel block#603
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: ASSERTIVE Plan: Pro Run ID: 📒 Files selected for processing (1)
WalkthroughThe Suggested reviewers
🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ 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 |
There was a problem hiding this comment.
Pull request overview
This PR adjusts the Concourse publish-* job plan so that the OCI image build/push to GHCR is executed as a sequential set of steps instead of being run inside the final in_parallel publishing block.
Changes:
- Move
extract-warden-imageandbuild-stemcell-oci-imagetasks out of thein_parallelblock. - Move the
puttogithub-container-registry-<os>-stemcellout of thein_parallelblock so it runs before the parallel “published-*” puts.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
No description provided.