This repository has been archived by the owner on Sep 26, 2023. It is now read-only.
ci: not using container for bazel build #1566
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
google-cla
bot
added
the
cla: yes
meltsufin
approved these changes
Nov 19, 2021
chanseokoh
reviewed
Nov 19, 2021
Comment on lines
+25
to
+26
| # Not using container. The ubuntu-latest has bazel installed | ||
| # container: gcr.io/cloud-devrel-public-resources/java8 |
There was a problem hiding this comment.
No need to add a comment. Just remove the line.
|
All checks passed. @chanseokoh This is also an experiment. I think it's better to not rely on GitHub's default Bazel version. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Does main branch build even if we don't use a container?