commit | 48504d85ac67fb0be01bfacaa95965b0b6892679 | [log] [tgz] |
---|---|---|
author | Commit Bot <commit-bot@chromium.org> | Tue Apr 27 07:01:14 2021 |
committer | Gerrit Code Review <noreply-gerritcodereview@google.com> | Tue Apr 27 07:01:14 2021 |
tree | 5c5ded1218dca10abf4e22e9b0e83718d35c7a43 | |
parent | a389dfd0d297d8c7f3577c20ac42c20f02b0ba48 [diff] | |
parent | 7f1668a89914b84b1ba219299f2f25642137e118 [diff] |
Merge "Import changes for goma server" into main
Goma is a distributed compiler service for open-source project such as Chromium and Android. It's some kind of replacement of distcc+ccache.
This is reference implementation of server code to be used with Goma client.
The Goma server uses a backend service that implements the Remote Execution API to distribute compile requests across a collection of worker machines and to cache the results of compilations. The Remote Execution API is an open-source standard, with multiple service implementations. The Goma server has been tested with Google's internal Remote Build Execution service, but could use other service implementations with some minor tweaks to the service code.
Goma server can be built on Linux.
$ GO111MODULE=on go get go.chromium.org/goma/server/cmd/remoteexec_proxy
You will get the binary in $(go env GOPATH)/bin
.
remoteexec_proxy
is a single server that acts as proxy server between Goma client and Remote Execution API.
$ remoteexec_proxy --port $PORT \ --platform-container-image "docker://...@sha256:..." \ --remoteexec-addr $REMOTEEXEC_ADDR \ --remote-instance-name $REMOTE_INSTANCE_NAME
for chromium, platform container image would be something like
FROM marketing.gcr.io/google/ubuntu1804:latest ENV DEBIAN_FRONTEND noninteractive RUN apt-get -y update \ && \ apt-get install -f -y build-essential lsb-release python \ && \ rm -rf /var/lib/apt/lists/*
If Remote Execution API requires service account, specify service account JSON file for Remote Execution API by --service-account-json
.
Running user is granted by default. If you need to allow other users, you need to specify them by --allowed-users
.
Log messages will be output to stderr.
Install goma client. We provide prebuilt binary with cipd
, which is available in depot_tools
.
$ cipd install infra/goma/client/linux-amd64 -root ${HOME}/goma
or follow the build instructions to build your own local version of Goma client before running the server code, and install it in $HOME/goma
.
Need to authenticate Goma client before use.
$ $HOME/goma/goma_auth.py login
Specify hostname in $GOMA_SERVER_HOST
and port in $GOMA_SERVER_PORT
, along with a few other environment flags.
$ export GOMA_SERVER_HOST='host-of-remoteexec_proxy-running' $ export GOMA_SERVER_PORT='port-of-remoteexec_proxy-running' $ export GOMA_USE_SSL=false $ export GOMA_ARBITRARY_TOOLCHAIN_SUPPORT=true
For example, if you are running remoteexec_proxy locally with --port 5050
, use:
$ export GOMA_SERVER_HOST=localhost $ export GOMA_SERVER_PORT=5050
Finally, start Goma client:
$ $HOME/goma/goma_ctl.py ensure_start
and in chromium tree.
$ rm -f out/Release/obj/base/base/base64.o $ GOMA_USE_LOCAL=false autoninja -C out/Release obj/base/base/base64.o