-
Notifications
You must be signed in to change notification settings - Fork 484
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
Implemented GitHub Actions Workflow for bazel build #51
base: master
Are you sure you want to change the base?
Conversation
uses: actions/checkout@v2 | ||
|
||
- name: Setup bazel | ||
uses: jwlawson/actions-setup-bazel@v1 |
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.
Is this step necessary?
It looks like some of the virtual environments for Github Actions already install bazel (or have a helper ready to go): https://github.com/actions/virtual-environments/blob/main/images/linux/scripts/installers/bazel.sh
I'm also looking at https://github.com/googleapis/google-cloud-cpp/pull/4333/files for reference.
Thanks for mentioning :) Using Bazel CI would be straight-forward here, too, basically a matter of checking in this file as ---
tasks:
ubuntu1804:
build_targets:
- "//..."
test_targets:
- "//..." and pinging us here https://github.com/bazelbuild/continuous-integration/issues/new/choose so that we can create the pipeline on Bazel's CI. Some docs about Bazel's CI: https://github.com/bazelbuild/continuous-integration/blob/master/buildkite/README.md |
GitHub Actions
Implemented a CI to build bazil that runs on every push or pull request and a badge on README.md.
An example of it successfully running here.