Skip to content

Add script for programatically updating images - #2835

Open
ted-xie wants to merge 2 commits into
masterfrom
hash-update-script
Open

Add script for programatically updating images#2835
ted-xie wants to merge 2 commits into
masterfrom
hash-update-script

Conversation

@ted-xie

@ted-xie ted-xie commented Sep 1, 2026

Copy link
Copy Markdown
Contributor
  • Adds sentinel values in bazelci.py around the images dict for simplicity
  • To run: python3 update_image_hashes.py

* Adds sentinel values in bazelci.py around the images dict for
  simplicity
* To run: `python3 update_image_hashes.py`
Comment thread buildkite/update_image_hashes.py
prefix = "bazel-public/testing" if branch == "testing" else "bazel-public"

print(f"Detected branch: {branch}")
print(f"Default Docker registry prefix: gcr.io/{prefix}")

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

I wonder do we still need gcr.io/bazel-public/testing? We can just always build from the master branch, then run this script to update bazelci.py, then the ci smoke test will test the new images?

Previously, we had to build on the testing branch and push new images to gcr.io/bazel-public/testing and make sure we use those in bazel-testing org, then rebuild those images after the Dockerfile changes are merged into master. Probably this process is no longer needed?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

I think we should still keep the testing org around for a while. The smoke test (AFAIK) doesn't cover terraform changes, while the testing org does.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants