-
Notifications
You must be signed in to change notification settings - Fork 0
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
CUS-349: CI: enable remote execution in jobs that can use it #45
Changes from all commits
a5a3523
299c4fa
bd6aee4
5885096
63a1852
2d67ef4
ab93824
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -28,10 +28,8 @@ env: | |
# Recommended here: https://github.com/bazelbuild/bazelisk/issues/88#issuecomment-625178467 | ||
BAZELISK_GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }} | ||
CLUSTER_HOST: opal.cluster.engflow.com | ||
CLUSTER_CONFIG: opal | ||
CRED_HELPER_TOKEN: ${{ secrets.OPAL_CRED_HELPER_TOKEN }} | ||
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }} | ||
OPAL_RPC_CREDENTIALS: ${{ secrets.OPAL_RPC_CREDENTIALS }} | ||
|
||
jobs: | ||
# TODO(OND-616): use remote execution and caching for all CI Runner jobs. | ||
|
@@ -44,7 +42,7 @@ jobs: | |
- "engflow-pool=ci_sysbox_x64" | ||
- "engflow-runtime=sysbox-runc" | ||
- "engflow-runner-id=${{ github.repository_id }}_bazel-builder_${{ github.run_id }}_${{ github.run_number }}_${{ github.run_attempt }}" | ||
timeout-minutes: 10 | ||
timeout-minutes: 30 | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. How is this timeout sized, now that it's extended to 30m? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. 10m wasn't fast enough to reliably complete a clean build on Opal. It's usually enough, but not always. I hit a problem that was kind of a worst case: completely cold cache on a pool that had queueing but hadn't scaled up yet. The |
||
|
||
env: | ||
ARCH: "x64" | ||
|
@@ -59,8 +57,7 @@ jobs: | |
- name: Run all tests | ||
if: success() | ||
run: | | ||
# TODO(CUS-345): Enable remote execution | ||
bazel test --config=noninteractive --config="${CLUSTER_CONFIG}" //... | ||
bazel test --config=noninteractive --config=engflow --config=remote_linux_x64 //... | ||
|
||
- name: Log out | ||
run: infra/logout.sh | ||
|
@@ -106,8 +103,8 @@ jobs: | |
shell: bash | ||
run: | | ||
# TODO(CUS-345): Enable remote execution | ||
bazel run --config=noninteractive --config="${CLUSTER_CONFIG}" @rules_go//go -- test ./... | ||
bazel run --config=noninteractive --config="${CLUSTER_CONFIG}" @rules_go//go -- clean -cache -modcache | ||
bazel run --config=noninteractive --config=engflow_bes @rules_go//go -- test ./... | ||
bazel run --config=noninteractive --config=engflow_bes @rules_go//go -- clean -cache -modcache | ||
|
||
- name: Log out | ||
shell: bash | ||
|
@@ -138,8 +135,8 @@ jobs: | |
if: success() | ||
run: | | ||
# TODO(CUS-345): Enable remote execution | ||
bazel run --config=noninteractive @rules_go//go -- test ./... | ||
bazel run --config=noninteractive @rules_go//go -- clean -cache -modcache | ||
bazel run --config=noninteractive --config=engflow_bes @rules_go//go -- test ./... | ||
bazel run --config=noninteractive --config=engflow_bes @rules_go//go -- clean -cache -modcache | ||
|
||
- name: Log out | ||
run: infra/logout.sh | ||
|
@@ -168,7 +165,7 @@ jobs: | |
- name: Check copyright headers | ||
if: success() | ||
run: | | ||
bazel run --config=noninteractive --config="${CLUSTER_CONFIG}" //infra/internal/check_copyright_headers | ||
bazel run --config=noninteractive --config=engflow_bes //infra/internal/check_copyright_headers | ||
|
||
- name: Log out | ||
run: infra/logout.sh |
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.
Note: glass will be faster, because the CI runner is on glass, so it will be faster if the RE action is on the same cluster. Fine to switch in a followup (or create separate configs for glass and opal so that the switch for both CI Runners and RE can be done more easily).
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.
Can't use Glass yet, mainly because it's not authorized for open source, though I think we can change that. It also doesn't have a Mac RE pool, though we don't strictly need that.