CI uses noble now, we can use the compiled bpm release#2724
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)
💤 Files with no reviewable changes (1)
WalkthroughThe CI pipeline 🚥 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. Review rate limit: 7/8 reviews remaining, refill in 7 minutes and 30 seconds.Comment |
There was a problem hiding this comment.
Pull request overview
Updates the Concourse pipeline to stop forcing BPM to be used as a source release now that the main CI path targets Ubuntu Noble, allowing use of a compiled BPM release during director deployment.
Changes:
- Removed
-o bosh-deployment/misc/source-releases/bpm.ymlfrom thebatsdeploy args. - Removed
-o bosh-deployment/misc/source-releases/bpm.ymlfrom thebats-fipsdeploy args.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
b648677 to
cab66cb
Compare
This was originally put in place because the CI pipelines ran on ubuntu-jammy after the releases started being compiled for ubuntu-noble