Merge forward ubuntu-noble to ubuntu-resolute - #699
Merged
Conversation
Add europe-north2 region and europe-north2-a zone to the light-google-environment-oss terraform resource to fix the failing create-light-google-ubuntu-jammy-1 build. See: https://bosh.ci.cloudfoundry.org/teams/stemcell/pipelines/ubuntu-jammy/jobs/create-light-google-ubuntu-jammy-1/builds/16 ai-assisted=yes [TNZ-116382] Monthly Release - July patch
N1 machine types are not available in europe-north2. Switch to e2-standard-2 (2 vCPU, 8 GB) which is supported in all europe-north2 zones and is a direct equivalent to n1-standard-2. ai-assisted=yes [TNZ-116382] Monthly Release - July patch
…urope-north2 Fix GCE terraform region/zone for light stemcell CI pipeline
Bumps [actions/setup-go](https://github.com/actions/setup-go) from 6 to 7. - [Release notes](https://github.com/actions/setup-go/releases) - [Commits](actions/setup-go@v6...v7) --- updated-dependencies: - dependency-name: actions/setup-go dependency-version: '7' dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
This was used in a `cleanup-light-aws-builder-test-amis` job that has since been removed from the pipeline in c2e1e3c
This pipeline exists in the ubuntu-jammy, ubuntu-noble, and ubuntu-resolute pipelines. They all run at the same time. The cleanup of 3 year old images is looking at ALL distributions in each pipeline. This caused failures where one pipeline would delete an AMI and then the other 2 pipelines would try to delete that AMI again and fail. We cannot limit the cleanup to the current pipeline's OS, because we want to clean up old AMIs even after a stemcell line is EOL and its pipeline has been deleted. So this commit makes the cleanup script tolerant to the AMI having been deleted.
ci: Handle concurrent deletions in CI
Merge forward ubuntu-jammy to ubuntu-noble
Contributor
|
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 Plus Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
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 |
KauzClay
previously approved these changes
Jul 30, 2026
KauzClay
approved these changes
Jul 30, 2026
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
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-N>ubuntu-<short_name-N>intoubuntu-<short_name-N+1>AI Review Feedback
All AI review comments (CodeRabbit, and Copilot when assigned) must be resolved before human reviewers will look at the PR. For each comment, either: