ci: build warden-cpi noble image #2643
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
cf-foundation-community-automation
bot
moved this to Inbox
in Foundational Infrastructure Working Group
KauzClay
force-pushed
the
ck-bump-ci-image-noble
branch
2 times, most recently
from
bcc53db to
7edb1fb
Compare
Alphasite
previously approved these changes
Nov 20, 2025
github-project-automation
bot
moved this from Inbox
to Pending Merge | Prioritized
in Foundational Infrastructure Working Group
aramprice
force-pushed
the
ck-bump-ci-image-noble
branch
from
7edb1fb to
81a2f7b
Compare
ystros
previously approved these changes
Nov 20, 2025
aramprice
force-pushed
the
ck-bump-ci-image-noble
branch
from
81a2f7b to
b015647
Compare
aramprice
previously approved these changes
Nov 21, 2025
- noble is now the default for docker-cpi as well. - build `-jammy` for both CPI images as a stop-gap
* agent requires systemd to start when running on noble, which is the new default
Signed-off-by: Aram Price <aram.price@broadcom.com>
aramprice
force-pushed
the
ck-bump-ci-image-noble
branch
2 times, most recently
from
bd627d3 to
e696b50
Compare
* extract yaml anchors to make future updates easier Signed-off-by: Aram Price <aram.price@broadcom.com>
aramprice
force-pushed
the
ck-bump-ci-image-noble
branch
from
e696b50 to
a39366e
Compare
aramprice
approved these changes
Nov 21, 2025
github-project-automation
bot
moved this from Pending Merge | Prioritized
to Done
in Foundational Infrastructure Working Group
1 task
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What is this change about?
Following a pattern done for the docker-cpi image, add a new tag on the warden-cpi image for Noble. It will consume the integration-noble image.
Also includes various refactors and cleanup to force using images from the new ghcr.io/cloudfoundry/bosh repo
Please provide contextual information.
Related to cloudfoundry/community#892
In the past month, bosh-deployment has switched to using Noble as the default stemcell. As such, all the compiled releases are for Noble.
Various other parts of the ecosystem haven't caught up with this change, these cpi images being one of them. They result in a rather opaque errors, sometimes swallowed by other processes like BPM.
Example of a failed build using the Noble compiled releases on the Jammy based warden-cpi image: https://bosh.ci.cloudfoundry.org/teams/main/pipelines/golang-release/jobs/bump/builds/29
What tests have you run against this PR?
N/A
How should this change be described in bosh release notes?
N/A
Does this PR introduce a breaking change?
no, additive only
Tag your pair, your PM, and/or team!