Use the gerritcodereview-ci instance for RBE builds
Use the dedicated project on GCloud for spawning the RBE
executors, isolating the access from the main Gerrit Code Review
GCloud project.
Change-Id: I6777f71f13ce4d327134689de2658c177f0d7e03
diff --git a/jenkins/gerrit-bazel-build.sh b/jenkins/gerrit-bazel-build.sh
index 6fb040f..9365f29 100644
--- a/jenkins/gerrit-bazel-build.sh
+++ b/jenkins/gerrit-bazel-build.sh
@@ -26,7 +26,7 @@
then
# TODO(davido): Figure out why javadoc part of api-rule doesn't work on RBE.
# See: https://github.com/bazelbuild/bazel/issues/12765 for more background.
- bazelisk build --config=remote --remote_instance_name=projects/api-project-164060093628/instances/default_instance plugins:core release api-skip-javadoc
+ bazelisk build --config=remote --remote_instance_name=projects/gerritcodereview-ci/instances/default_instance plugins:core release api-skip-javadoc
elif [[ "$MODE" == *"polygerrit"* ]]
then
echo "Skipping building eclipse and maven"
diff --git a/jenkins/gerrit-bazel-verifier-test.sh b/jenkins/gerrit-bazel-verifier-test.sh
index 47fe4da..0ba3142 100755
--- a/jenkins/gerrit-bazel-verifier-test.sh
+++ b/jenkins/gerrit-bazel-verifier-test.sh
@@ -17,7 +17,7 @@
case $TARGET_BRANCH$MODE in
masterrbe|stable-3.4rbe|stable-3.5rbe|stable-3.6rbe)
TEST_TAG_FILTER="-flaky,-elastic,-no_rbe"
- BAZEL_OPTS="--config=remote --remote_instance_name=projects/api-project-164060093628/instances/default_instance"
+ BAZEL_OPTS="--config=remote --remote_instance_name=projects/gerritcodereview-ci/instances/default_instance"
;;
masternotedb|stable-3.4notedb|stable-3.5notedb|stable-3.6notedb)
TEST_TAG_FILTER="-flaky,elastic,no_rbe"
