-
Notifications
You must be signed in to change notification settings - Fork 6.7k
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
build: update to bazel 3.6 #20855
build: update to bazel 3.6 #20855
Conversation
9bf13f2
to
f2e255f
Compare
Bumps the version of Bazel to 3.6 like in angular/angular in an attempt to resolve some of the recent CI flakes.
f2e255f
to
390f530
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
@@ -81,7 +81,6 @@ build:remote --host_cpu=k8 | |||
# Setup the remote build execution servers. | |||
build:remote --remote_cache=remotebuildexecution.googleapis.com | |||
build:remote --remote_executor=remotebuildexecution.googleapis.com | |||
build:remote --tls_enabled=true |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I removed this one since Bazel was logging that it's not supported.
Bumps the version of Bazel to 3.6 like in angular/angular in an attempt to resolve some of the recent CI flakes. (cherry picked from commit 594b4ef)
Bumps the version of Bazel to 3.6 like in angular/angular in an attempt to resolve some of the recent CI flakes. (cherry picked from commit 594b4ef)
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
Bumps the version of Bazel to 3.6 like in angular/angular in an attempt to resolve some of the recent CI flakes.