Skip to content

build: setup remote execution through dev-infra Orb #25694

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

Merged
merged 1 commit into from
Sep 24, 2022
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 3 additions & 4 deletions .circleci/config.yml
Original file line number Diff line number Diff line change
Expand Up @@ -100,9 +100,8 @@ var_15: &ignore_presubmit_branch_filter
# Runs a script that sets up the Bazel remote execution. This will be used by jobs that run
# Bazel primarily and should benefit from remote caching and execution.
var_16: &setup_bazel_remote_execution
run:
name: 'Setup bazel RBE remote execution'
command: ./scripts/bazel/setup-remote-execution.sh
devinfra/setup-bazel-remote-exec:
bazelrc: ./.bazelrc.user

# Sets up the bazel binary globally. We don't want to access bazel through Yarn and NodeJS
# because it could mean that the Bazel child process only has access to limited memory.
Expand Down Expand Up @@ -149,7 +148,7 @@ orbs:
# to make sure that snapshot builds are not deployed out of order, resulting in Git
# push conflicts.
queue: eddiewebb/queue@1.5.0
devinfra: angular/dev-infra@1.0.3
devinfra: angular/dev-infra@1.0.6

commands:
checkout_and_rebase:
Expand Down
Binary file removed scripts/bazel/gcp_token
Binary file not shown.
20 changes: 0 additions & 20 deletions scripts/bazel/setup-remote-execution.sh

This file was deleted.