-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Upgrade to Bazel 5.0 in Provisioned #16447
Comments
I have been running 5.0 locally since it was released, and I haven't seen any problems. Our macOS unprovisioned is also running it without any problems. FYI see #16405 for a fix (that's already landed) that is required for 5.0. Users of older Drake releases that still want to use Bazel 5.0 should set |
@BetsyMcPhail could you take this on (or delegate it), as part of this week's "monthly dependency upgrades" work? (For myself, I will check that Anzu is also happy with Bazel 5.) |
Sounds good |
@jwnimmer-tri, to make sure we're on the same page, this issue is similar to #15711? Upgrade the requirement within drake and then, eventually if all looks good, the provisioned images? |
Yes, perfect! To be clear -- in this case, though, I think we will not need to update the minimum required version. We have no evidence that bazel 4.0 is incompatible with current Drake. If you'd like to locally install 4.0 and try a Release build to confirm or refute, that's fine too, but is not especially important. |
Linux images have been updated. |
Mac images are also updated |
And PR for unprovisioned images is merged. All set to close. |
https://github.com/bazelbuild/bazel/releases/tag/5.0.0
The text was updated successfully, but these errors were encountered: