Chiebot-Mirror
/
grpc
mirror of https://github.com/grpc/grpc.git
8
0
Fork 0
Code Issues Projects Releases Wiki Activity
The C based gRPC (C++, Python, Ruby, Objective-C, PHP, C#) https://grpc.io/
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
43470 Commits
274 Branches
377 Tags
1.2 GiB
 
 
 
 
 
 
Tag: Branch: Tree: c3ac15b480
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from 'c3ac15b480'
${ noResults }
grpc/tools/remote_build
Vijay Pai 0c0f3f0556
Declare microbenchmarks as tests rather than binaries, fix issues 		5 years ago
..
README.md introduce mac.bazelrc 5 years ago
kokoro.bazelrc
…
mac.bazelrc Adding GRPC_PORT_ISOLATED_RUNTIME=1 to mac.bazelrc. 5 years ago
manual.bazelrc avoid occasional timeout uploading RBE results 5 years ago
rbe_common.bazelrc Declare microbenchmarks as tests rather than binaries, fix issues 5 years ago
windows.bazelrc avoid occasional timeout uploading RBE results 5 years ago
workspace_status_kokoro.bat
…
workspace_status_kokoro.sh
…

README.md

Running Remote Builds with bazel

This allows you to spawn gRPC C/C++ remote build and tests from your workstation with configuration that's very similar to what's used by our CI Kokoro.

Note that this will only work for gRPC team members (it requires access to the remote build and execution cluster), others will need to rely on local test runs and tests run by Kokoro CI.

Prerequisites

  • See Installing Bazel for instructions how to install bazel on your system.

  • Setup application default credentials for running remote builds by following the "Set credentials" section. (Note: for the ResultStore UI upload to work, you'll need a special kind of application default credentials, so if the build event upload doesn't work, doublecheck the instructions)

Running remote build manually from dev workstation

Run from repository root (opt, dbg):

# manual run of bazel tests remotely on Foundry
bazel --bazelrc=tools/remote_build/manual.bazelrc test --config=opt //test/...

Sanitizer runs (asan, msan, tsan, ubsan):

# manual run of bazel tests remotely on Foundry with given sanitizer
bazel --bazelrc=tools/remote_build/manual.bazelrc test --config=asan //test/...

Run on Windows MSVC:

# manual run of bazel tests remotely on RBE Windows (must be run from Windows machine)
bazel --bazelrc=tools/remote_build/windows.bazelrc test --config=windows_opt //test/...

Run on MacOS (experimental for now):

# manual run of bazel tests on Mac (must be run from Mac machine)
# NOTE: it's not really a "remote execution", but uploads results to ResultStore
bazel --bazelrc=tools/remote_build/mac.bazelrc test --config=opt //test/...

Available command line options can be found in Bazel command line reference