-
Notifications
You must be signed in to change notification settings - Fork 99
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
Add bazel CI workflow #351
Conversation
Signed-off-by: Michael Carroll <mjcarroll@intrinsic.ai>
Signed-off-by: Michael Carroll <mjcarroll@intrinsic.ai>
This is still expected to fail until I add bazel-specific tests. |
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.
What's the purpose of the folder test/bazel
?
If that's just the build folder for bazel, I suggest to move it to .github/workflows/bazel
.
@@ -0,0 +1,18 @@ | |||
# This file contains Bazel settings to apply on CI only. | |||
# It is referenced with a --bazelrc option in the call to bazel in ci.yaml |
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 cannot find this reference. Can you please point me to the line in code?
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.
Well, it used to be used as part of the upstream CI workflow, but when trying to find the reference, I find that it has been removed in https://github.com/bazel-contrib/.github/pull/11/files#diff-fcdc74e04f54e030b7b5cfde9bbcd1cc443162841efd9375481872e030b43a2bL153, which was reported upstream here: bazel-contrib/.github#23)
Please integrate this PR into #350. They build upon each other anyway. |
It's where an integration test of the bazel rules will go, I haven't implemented it yet. I will move it into |
No description provided.