execution-service: add new subcommand execute

This subcommand starts a single node remote execution service honoring
the just native remote protocol.

If the flag --compatible is provided, the execution service will honor
the original remote build execution protocol.

New command line args supported by this subcommand:

-p,--port INT: Execution service will listen to this port. If unset,
 the service will listen to the first available one.

--info-file TEXT: Write the used port, interface, and pid to this file
  in JSON format. If the file exists, it will be overwritten.

-i,--interface TEXT: Interface to use. If unset, the loopback device
 is used.

--pid-file TEXT Write pid to this file in plain txt. If the file
  exists, it will be overwritten.

--tls-server-cert TEXT: Path to the TLS server certificate.

--tls-server-key TEXT: Path to the TLS server key.

Co-authored by: Klaus Aehlig <klaus.aehlig@huawei.com>

1 files changed, 57 insertions, 0 deletions

diff --git a/src/buildtool/execution_api/execution_service/capabilities_server.cpp b/src/buildtool/execution_api/execution_service/capabilities_server.cpp
new file mode 100644
index 00000000..198d1fb6
--- /dev/null
+++ b/src/buildtool/execution_api/execution_service/capabilities_server.cpp
@@ -0,0 +1,57 @@
+// Copyright 2023 Huawei Cloud Computing Technology Co., Ltd.
+//
+// Licensed under the Apache License, Version 2.0 (the "License");
+// you may not use this file except in compliance with the License.
+// You may obtain a copy of the License at
+//
+//     http://www.apache.org/licenses/LICENSE-2.0
+//
+// Unless required by applicable law or agreed to in writing, software
+// distributed under the License is distributed on an "AS IS" BASIS,
+// WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+// See the License for the specific language governing permissions and
+// limitations under the License.
+
+#include "src/buildtool/execution_api/execution_service/capabilities_server.hpp"
+
+#include "src/buildtool/compatibility/compatibility.hpp"
+#include "src/buildtool/logging/logger.hpp"
+
+auto CapabilitiesServiceImpl::GetCapabilities(
+    ::grpc::ServerContext* /*context*/,
+    const ::build::bazel::remote::execution::v2::GetCapabilitiesRequest*
+    /*request*/,
+    ::build::bazel::remote::execution::v2::ServerCapabilities* response)
+    -> ::grpc::Status {
+    if (!Compatibility::IsCompatible()) {
+        auto const* str = "GetCapabilities not implemented";
+        Logger::Log(LogLevel::Error, str);
+        return ::grpc::Status{grpc::StatusCode::UNIMPLEMENTED, str};
+    }
+    ::build::bazel::remote::execution::v2::CacheCapabilities cache;
+    ::build::bazel::remote::execution::v2::ExecutionCapabilities exec;
+
+    cache.add_digest_function(
+        ::build::bazel::remote::execution::v2::DigestFunction_Value::
+            DigestFunction_Value_SHA256);
+    cache.mutable_action_cache_update_capabilities()->set_update_enabled(false);
+    static constexpr std::size_t kMaxBatchTransferSize = 1024 * 1024;
+    cache.set_max_batch_total_size_bytes(kMaxBatchTransferSize);
+    static_assert(kMaxBatchTransferSize < GRPC_DEFAULT_MAX_RECV_MESSAGE_LENGTH,
+                  "Max batch transfer size too large.");
+    *(response->mutable_cache_capabilities()) = cache;
+
+    exec.set_digest_function(
+        ::build::bazel::remote::execution::v2::DigestFunction_Value::
+            DigestFunction_Value_SHA256);
+    exec.set_exec_enabled(true);
+
+    *(response->mutable_execution_capabilities()) = exec;
+    ::build::bazel::semver::SemVer v{};
+    v.set_major(2);
+    v.set_minor(0);
+
+    *(response->mutable_low_api_version()) = v;
+    *(response->mutable_high_api_version()) = v;
+    return ::grpc::Status::OK;
+}