Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

release(executors): update ami naming #62579

Merged
merged 2 commits into from May 14, 2024
Merged

Conversation

BolajiOlajide
Copy link
Contributor

@BolajiOlajide BolajiOlajide commented May 9, 2024

Context

Test plan

We found out during the 5.4.0 release that the amis weren't named properly. Thus PR fixes that.
Below is the matrix for naming AMIs.

Matrix

Internal Release Public Release
{IMAGE_FAMILY}-{BUILDKITE_BUILD_NUMBER} {IMAGE_FAMILY}

@BolajiOlajide BolajiOlajide requested a review from a team May 9, 2024 16:14
@BolajiOlajide BolajiOlajide self-assigned this May 9, 2024
@cla-bot cla-bot bot added the cla-signed label May 9, 2024
@BolajiOlajide BolajiOlajide changed the title release: update ami naming release(executors): update ami naming May 9, 2024
@@ -25,7 +25,7 @@ export AWS_SECRET_ACCESS_KEY="${AWS_EXECUTOR_AMI_SECRET_KEY}"

# Point to GCP boot disk image/AMI built by //cmd/executor/vm-image:ami.build
NAME="${IMAGE_FAMILY}"
if [ "${RELEASE_INTERNAL:-}" != "true" ]; then
if [ "${RELEASE_INTERNAL:-}" == "true" ]; then
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Need a similar one for docker mirror?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hmmm does ami.push only get triggered during releases?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I was going to ask that, I assumed it is but not 100% certain.
We can revisit this PR next week when everyone is back btw.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@BolajiOlajide BolajiOlajide added the backport 5.4.0 label used to backport PRs to the 5.4.0 release branch label May 14, 2024
@BolajiOlajide BolajiOlajide removed the backport 5.4.0 label used to backport PRs to the 5.4.0 release branch label May 14, 2024
@BolajiOlajide BolajiOlajide merged commit 894a951 into main May 14, 2024
14 of 15 checks passed
@BolajiOlajide BolajiOlajide deleted the bo/update-ami-naming branch May 14, 2024 08:56
@BolajiOlajide BolajiOlajide added the backport 5.4.0 label used to backport PRs to the 5.4.0 release branch label May 14, 2024
sourcegraph-release-guild-bot pushed a commit that referenced this pull request May 14, 2024
* update naming

* update docker mirror image family name

(cherry picked from commit 894a951)
BolajiOlajide added a commit that referenced this pull request May 18, 2024
release(executors): update ami naming (#62579)

* update naming

* update docker mirror image family name

(cherry picked from commit 894a951)

Co-authored-by: Bolaji Olajide <25608335+BolajiOlajide@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport 5.4.0 label used to backport PRs to the 5.4.0 release branch cla-signed
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants