diff options
| author | Klaus Aehlig <klaus.aehlig@huawei.com> | 2022-06-20 14:57:08 +0200 |
|---|---|---|
| committer | Klaus Aehlig <klaus.aehlig@huawei.com> | 2022-06-20 17:51:44 +0200 |
| commit | 7e37836d99fb6567460738943e3d86e6ed30c5bd (patch) | |
| tree | d5eec62ddb89e5ffee6ff1c4d49af994f7cd6617 | |
| parent | 8a9664f9e63bf0528ee70ce40904314dd9deee64 (diff) | |
| download | justbuild-7e37836d99fb6567460738943e3d86e6ed30c5bd.tar.gz | |
Export remote-execution API
In this way, we follow our own standard practices of exporting
targets to be used by other repositories. While for a couple of
proto files, there shouldn't be a difference in performance, it is
still good to have the interfaces cleaned up and documented.
| -rw-r--r-- | etc/import/TARGETS.bazel_remote_apis | 12 |
1 files changed, 11 insertions, 1 deletions
diff --git a/etc/import/TARGETS.bazel_remote_apis b/etc/import/TARGETS.bazel_remote_apis index 3a51bd53..8f846701 100644 --- a/etc/import/TARGETS.bazel_remote_apis +++ b/etc/import/TARGETS.bazel_remote_apis @@ -3,7 +3,7 @@ , "name": ["semver_proto"] , "srcs": ["build/bazel/semver/semver.proto"] } -, "remote_execution_proto": +, "remote_execution_proto impl": { "type": ["@", "rules", "proto", "library"] , "name": ["remote_execution_proto"] , "service": ["yes"] @@ -16,4 +16,14 @@ , ["@", "google_apis", "", "google_rpc_status_proto"] ] } +, "remote_execution_proto": + { "type": "export" + , "target": "remote_execution_proto impl" + , "doc": + [ "Remote Execution API" + , "" + , "The Remote Execution API is an API that, at its most general, allows clients" + , "to request execution of binaries on a remote system." + ] + } } |