pipelines/tools/bazel_builder
Ajay Gopinathan a882999c42 Use Remote Build Execution for Bazel builds. (#1031)
* [WIP] Use Remote Build Execution for Bazel builds.

* Add build_api_server.sh build script for API server.

* update build_image.yaml

* update build_image.yaml

* update build_image.yaml

* update build_image.yaml

* update build_image.yaml

* update build_image.yaml

* escape newlines

* Try using bazelbuilder's service account credentials.

* Clean up

* Add README

* Update backend README

* Update OWNERS
2019-09-30 10:41:38 -07:00
..
BUILD Use Remote Build Execution for Bazel builds. (#1031) 2019-09-30 10:41:38 -07:00
Dockerfile Use Remote Build Execution for Bazel builds. (#1031) 2019-09-30 10:41:38 -07:00
OWNERS Use Remote Build Execution for Bazel builds. (#1031) 2019-09-30 10:41:38 -07:00
README.md Use Remote Build Execution for Bazel builds. (#1031) 2019-09-30 10:41:38 -07:00
bazelrc Use Remote Build Execution for Bazel builds. (#1031) 2019-09-30 10:41:38 -07:00

README.md

This directory contains Dockerfile and Bazel configuration to be used by the Remote Build Execution service for running Bazel workloads in GCP.

The build is run using a custom image that contains both Bazel as well as cmake (which is required by the ML Metadata dependency used in API Server).

The custom image is pushed to gcr.io/ml-pipeline-test/bazel-builder@sha256:<IMAGE_SHA>"

To build a new image, use the Dockerfile in this folder: docker build -f Dockerfile .

Take note of the SHA id of the image, and update the value of CONTAINER_VERSION in the BUILD file in this directory.

For more information about RBE, see their documentation.