Merge jammy forward#594
Conversation
These are not stable enough for testing purposes.
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Organization UI Review profile: ASSERTIVE Plan: Pro Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ 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
Updates the Ubuntu Jammy OS-image metalink and aligns the Concourse builder pipeline’s GCP preemptible settings as part of the repo’s merge-forward workflow.
Changes:
- Bump
ubuntu-jammyOS-image metalink to version1048.0.0(new hashes/sizes + published timestamp). - Disable GCP preemptible instances for the director deploy steps and BATS vars in
ci/pipelines/builder.yml.
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
| image-metalinks/ubuntu-jammy/ubuntu-jammy.meta4 | Updates Jammy OS-image + USN log hashes/sizes and bumps metalink version/published timestamp. |
| ci/pipelines/builder.yml | Sets GCP_PREEMPTIBLE / VARS_PREEMPTIBLE to false for relevant GCP integration steps. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
|
/easycla |
NOTE: this repository uses a "Merge Forward" strategy
Changes should be made in the earliest applicable branch, and
merged forward through subsequent branches.
ubuntu-<short_name>)merge-to-<next_short_name>branchubuntu-<short_name>intomerge-to-<next_short_name>merge-to-<next_short_name>intoubuntu-<next_short_name>