-
Notifications
You must be signed in to change notification settings - Fork 0
/
pants.remote.ini
49 lines (45 loc) · 2.76 KB
/
pants.remote.ini
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
# For goals that you'd like to remote, first install the Google cloud CLI and then log in to an
# an account authorized to run the Pants project (you may need to ask a Pants committer for
# to authorize your account). Then, point to this config file and provide the oauth token like this:
#
# $ ./pants --pants-config-files=pants.remote.ini
# --remote-oauth-bearer-token-path=<(gcloud auth application-default print-access-token | perl -p -e 'chomp if eof')
# --no-v1 --v2 test tests/python/pants_test/util:strutil
#
# Remoting does not work for every goal, so you should not permanently point to this ini file, e.g.
# via an env var; only point to it when you want to remote a specific invocation.
[DEFAULT]
remote_execution: True
remote_execution_server: remotebuildexecution.googleapis.com
remote_store_server: remotebuildexecution.googleapis.com
# This file might not exist on your machine. If this default fails, run `find /usr -name '*.pem'`
# and override this value via the env var PANTS_REMOTE_CA_CERTS_PATH.
remote_ca_certs_path: /usr/local/etc/openssl/cert.pem
remote_instance_name: projects/pants-remoting-beta/instances/default_instance
remote_execution_extra_platform_properties: [
# This allows network requests, e.g. to resolve dependencies with Pex.
"dockerNetwork=standard",
"container-image=docker://gcr.io/pants-remoting-beta/rbe-remote-execution@sha256:5d818cd71c9180d977e16ca7a20e90ced14211621b69fe1d6c3fc4c42c537a14",
]
# This should correspond to the number of workers running in Google RBE. See
# https://console.cloud.google.com/apis/api/remotebuildexecution.googleapis.com/quotas?project=pants-remoting-beta&folder&organizationId&duration=PT6H.
process_execution_remote_parallelism: 32
# TODO: Temporarily disabling speculation until we're able to confirm that it never causes a
# negative performance impact.
process_execution_speculation_strategy: none
# p95 of RBE appears to be ~ 2 seconds, but we need to factor in local queue time which can be much longer, but no metrics yet.
process_execution_speculation_delay: 15
[python-setup]
# TODO(#7735): This config is not ideal, that we must specify the PATH for both local and remote
# platforms. This should be replaced by a proper mechanism to differentiate between the two.
interpreter_search_paths: [
# We include the host PATH and PEXRC values so that speculation still works.
'<PATH>',
'<PEXRC>',
# This is the $PATH of the docker container, obtained by locally running `$ docker run --tag
# rbe-remote-execution sh -c 'echo $PATH'`.
"/pyenv-docker-build/versions/3.7.3/bin:/pyenv-docker-build/versions/3.6.8/bin:/pyenv-docker-build/versions/2.7.15/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/local/go/bin",
]
[python-native-code]
ld_flags: []
cpp_flags: []