pipelines/tools/bazel_builder
Humair Khan 24782d178d
chore: update all owners files (#11886)
Various owners' files reviewers/approvers are no longer involved with
the community. Additionaly, we have various other folks that are
involved and have shown an active interest in reviewing various portions
of the code base. This change updates all owners files to reflect this
current state of the community.

Signed-off-by: Humair Khan <HumairAK@users.noreply.github.com>
2025-05-02 14:47:04 +00: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
README.md Use Remote Build Execution for Bazel builds. (#1031) 2019-09-30 10:41:38 -07:00
bazelrc Assigned copyright to the project authors (#5587) 2021-05-05 13:53:22 +08: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.