diff options
| author | Philip Kuryloski <kuryloskip@vmware.com> | 2021-11-12 09:37:30 +0100 |
|---|---|---|
| committer | Philip Kuryloski <kuryloskip@vmware.com> | 2021-11-12 09:37:30 +0100 |
| commit | f92e6b436cd8a510d5386009fb3a0db6ff9c578c (patch) | |
| tree | 5e023cd754cf197523f935c08117708845ea5154 /.bazelrc | |
| parent | 13e62b0939139293e35406c69376b6c883d1ca97 (diff) | |
| download | rabbitmq-server-git-f92e6b436cd8a510d5386009fb3a0db6ff9c578c.tar.gz | |
Add --remote_download_toplevel to the bazel config
Based on the testing and advice from BuildBuddy:
Network limitations/flakiness in GitHub actions can be mitigated by
reducing the number of artifacts that get downloaded. Since we only
use bazel for testing currently, we don't actually care about the
artifacts, so there is no downside to the flag.
If this isn't enough, we can try the --remote_download_minimal flag,
which limits the amount of downloads even further.
Diffstat (limited to '.bazelrc')
| -rw-r--r-- | .bazelrc | 1 |
1 files changed, 1 insertions, 0 deletions
@@ -7,6 +7,7 @@ build:buildbuddy --remote_cache=grpcs://remote.buildbuddy.io build:buildbuddy --remote_timeout=1200 build:buildbuddy --grpc_keepalive_time=360s build:buildbuddy --grpc_keepalive_timeout=360s +build:buildbuddy --remote_download_toplevel build:buildbuddy --build_metadata=REPO_URL=https://github.com/rabbitmq/rabbitmq-server.git build:rbe --config=buildbuddy |