Skip to content

[ci] May 2025 provisioned image refresh #22930

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

Closed
4 tasks done
tyler-yankee opened this issue Apr 25, 2025 · 4 comments
Closed
4 tasks done

[ci] May 2025 provisioned image refresh #22930

tyler-yankee opened this issue Apr 25, 2025 · 4 comments
Assignees
Labels
component: continuous integration Jenkins, CDash, mirroring of externals, website infrastructure

Comments

@tyler-yankee
Copy link
Contributor

tyler-yankee commented Apr 25, 2025

This is the first time we're doing this monthly per #22818.

  • Linux Jammy
  • Linux Noble
  • macOS Sonoma
  • macOS Sequoia

Also note the traffic from #22890, #22919, (edit) #22929, and (edit) #22937.

@jwnimmer-tri
Copy link
Collaborator

Since the bazel download from #22929 is also cached in the Provisioned images, landing that PR prior to the Linux snapshots would be a small benefit.

@jwnimmer-tri
Copy link
Collaborator

Also note that #22937 is about to change the Ubuntu packages list. It might be worth trying to coordinate that with the AMI refresh.

@tyler-yankee tyler-yankee changed the title [ci] Monthly provisioned image refresh [ci] May 2025 provisioned image refresh Apr 28, 2025
@tyler-yankee
Copy link
Contributor Author

tyler-yankee commented Apr 30, 2025

Linux Jammy and Noble are all set with the changes from #22937 and #22919 (and #22929 is done implicitly). They will need to be redone as part of the effort for #22890.

@tyler-yankee
Copy link
Contributor Author

Completed along with #22890.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
component: continuous integration Jenkins, CDash, mirroring of externals, website infrastructure
Development

No branches or pull requests

2 participants