@@ -67,7 +67,6 @@ build --define=angular_ivy_enabled=True
67
67
68
68
# Use the Angular team internal GCP instance for remote execution.
69
69
build:remote --remote_instance_name=projects/internal-200822/instances/primary_instance
70
- build:remote --project_id=internal-200822
71
70
72
71
# Needed due to: https://github.com/bazelbuild/bazel/issues/7254
73
72
build:remote --define=EXECUTOR=remote
@@ -80,7 +79,7 @@ build:remote --host_cpu=k8
80
79
# Setup the remote build execution servers.
81
80
build:remote --remote_cache=remotebuildexecution.googleapis.com
82
81
build:remote --remote_executor=remotebuildexecution.googleapis.com
83
- build:remote --auth_enabled =true
82
+ build:remote --google_default_credentials =true
84
83
85
84
# Setup the toolchain and platform for the remote build execution. The platform
86
85
# is provided by the shared dev-infra package and targets k8 remote containers.
@@ -108,6 +107,7 @@ test --sandbox_default_allow_network=false
108
107
# that could cause builds to fail unnecessarily. If desired, build result uploading
109
108
# can be manually uploaded, but given that the build event service server has been
110
109
# less stable than the remote executors, we do not want to degrade CI stability.
110
+ build:build-results --bes_instance_name=internal-200822
111
111
build:build-results --bes_backend=buildeventservice.googleapis.com
112
112
build:build-results --bes_timeout=60s
113
113
build:build-results --bes_results_url="https://source.cloud.google.com/results/invocations/"
0 commit comments