googleapis
Version:
Google APIs Client Library for Node.js
717 lines • 142 kB
TypeScript
/// <reference types="node" />
import { OAuth2Client, JWT, Compute, UserRefreshClient, BaseExternalAccountClient, GaxiosPromise, GoogleConfigurable, MethodOptions, StreamMethodOptions, GlobalOptions, GoogleAuth, BodyResponseCallback, APIRequestContext } from 'googleapis-common';
import { Readable } from 'stream';
export declare namespace remotebuildexecution_v2 {
export interface Options extends GlobalOptions {
version: 'v2';
}
interface StandardParameters {
/**
* Auth client or API Key for the request
*/
auth?: string | OAuth2Client | JWT | Compute | UserRefreshClient | BaseExternalAccountClient | GoogleAuth;
/**
* V1 error format.
*/
'$.xgafv'?: string;
/**
* OAuth access token.
*/
access_token?: string;
/**
* Data format for response.
*/
alt?: string;
/**
* JSONP
*/
callback?: string;
/**
* Selector specifying which fields to include in a partial response.
*/
fields?: string;
/**
* API key. Your API key identifies your project and provides you with API access, quota, and reports. Required unless you provide an OAuth 2.0 token.
*/
key?: string;
/**
* OAuth 2.0 token for the current user.
*/
oauth_token?: string;
/**
* Returns response with indentations and line breaks.
*/
prettyPrint?: boolean;
/**
* Available to use for quota purposes for server-side applications. Can be any arbitrary string assigned to a user, but should not exceed 40 characters.
*/
quotaUser?: string;
/**
* Legacy upload protocol for media (e.g. "media", "multipart").
*/
uploadType?: string;
/**
* Upload protocol for media (e.g. "raw", "multipart").
*/
upload_protocol?: string;
}
/**
* Remote Build Execution API
*
* Supplies a Remote Execution API service for tools such as bazel.
*
* @example
* ```js
* const {google} = require('googleapis');
* const remotebuildexecution = google.remotebuildexecution('v2');
* ```
*/
export class Remotebuildexecution {
context: APIRequestContext;
actionResults: Resource$Actionresults;
actions: Resource$Actions;
blobs: Resource$Blobs;
operations: Resource$Operations;
v2: Resource$V2;
constructor(options: GlobalOptions, google?: GoogleConfigurable);
}
/**
* An `Action` captures all the information about an execution which is required to reproduce it. `Action`s are the core component of the [Execution] service. A single `Action` represents a repeatable action that can be performed by the execution service. `Action`s can be succinctly identified by the digest of their wire format encoding and, once an `Action` has been executed, will be cached in the action cache. Future requests can then use the cached result rather than needing to run afresh. When a server completes execution of an Action, it MAY choose to cache the result in the ActionCache unless `do_not_cache` is `true`. Clients SHOULD expect the server to do so. By default, future calls to Execute the same `Action` will also serve their results from the cache. Clients must take care to understand the caching behaviour. Ideally, all `Action`s will be reproducible so that serving a result from cache is always desirable and correct.
*/
export interface Schema$BuildBazelRemoteExecutionV2Action {
/**
* The digest of the Command to run, which MUST be present in the ContentAddressableStorage.
*/
commandDigest?: Schema$BuildBazelRemoteExecutionV2Digest;
/**
* If true, then the `Action`'s result cannot be cached, and in-flight requests for the same `Action` may not be merged.
*/
doNotCache?: boolean | null;
/**
* The digest of the root Directory for the input files. The files in the directory tree are available in the correct location on the build machine before the command is executed. The root directory, as well as every subdirectory and content blob referred to, MUST be in the ContentAddressableStorage.
*/
inputRootDigest?: Schema$BuildBazelRemoteExecutionV2Digest;
/**
* The optional platform requirements for the execution environment. The server MAY choose to execute the action on any worker satisfying the requirements, so the client SHOULD ensure that running the action on any such worker will have the same result. A detailed lexicon for this can be found in the accompanying platform.md. New in version 2.2: clients SHOULD set these platform properties as well as those in the Command. Servers SHOULD prefer those set here.
*/
platform?: Schema$BuildBazelRemoteExecutionV2Platform;
/**
* An optional additional salt value used to place this `Action` into a separate cache namespace from other instances having the same field contents. This salt typically comes from operational configuration specific to sources such as repo and service configuration, and allows disowning an entire set of ActionResults that might have been poisoned by buggy software or tool failures.
*/
salt?: string | null;
/**
* A timeout after which the execution should be killed. If the timeout is absent, then the client is specifying that the execution should continue as long as the server will let it. The server SHOULD impose a timeout if the client does not specify one, however, if the client does specify a timeout that is longer than the server's maximum timeout, the server MUST reject the request. The timeout is a part of the Action message, and therefore two `Actions` with different timeouts are different, even if they are otherwise identical. This is because, if they were not, running an `Action` with a lower timeout than is required might result in a cache hit from an execution run with a longer timeout, hiding the fact that the timeout is too short. By encoding it directly in the `Action`, a lower timeout will result in a cache miss and the execution timeout will fail immediately, rather than whenever the cache entry gets evicted.
*/
timeout?: string | null;
}
/**
* Describes the server/instance capabilities for updating the action cache.
*/
export interface Schema$BuildBazelRemoteExecutionV2ActionCacheUpdateCapabilities {
updateEnabled?: boolean | null;
}
/**
* An ActionResult represents the result of an Action being run. It is advised that at least one field (for example `ActionResult.execution_metadata.Worker`) have a non-default value, to ensure that the serialized value is non-empty, which can then be used as a basic data sanity check.
*/
export interface Schema$BuildBazelRemoteExecutionV2ActionResult {
/**
* The details of the execution that originally produced this result.
*/
executionMetadata?: Schema$BuildBazelRemoteExecutionV2ExecutedActionMetadata;
/**
* The exit code of the command.
*/
exitCode?: number | null;
/**
* The output directories of the action. For each output directory requested in the `output_directories` or `output_paths` field of the Action, if the corresponding directory existed after the action completed, a single entry will be present in the output list, which will contain the digest of a Tree message containing the directory tree, and the path equal exactly to the corresponding Action output_directories member. As an example, suppose the Action had an output directory `a/b/dir` and the execution produced the following contents in `a/b/dir`: a file named `bar` and a directory named `foo` with an executable file named `baz`. Then, output_directory will contain (hashes shortened for readability): ```json // OutputDirectory proto: { path: "a/b/dir" tree_digest: { hash: "4a73bc9d03...", size: 55 \} \} // Tree proto with hash "4a73bc9d03..." and size 55: { root: { files: [ { name: "bar", digest: { hash: "4a73bc9d03...", size: 65534 \} \} ], directories: [ { name: "foo", digest: { hash: "4cf2eda940...", size: 43 \} \} ] \} children : { // (Directory proto with hash "4cf2eda940..." and size 43) files: [ { name: "baz", digest: { hash: "b2c941073e...", size: 1294, \}, is_executable: true \} ] \} \} ``` If an output of the same name as listed in `output_files` of the Command was found in `output_directories`, but was not a directory, the server will return a FAILED_PRECONDITION.
*/
outputDirectories?: Schema$BuildBazelRemoteExecutionV2OutputDirectory[];
/**
* The output directories of the action that are symbolic links to other directories. Those may be links to other output directories, or input directories, or even absolute paths outside of the working directory, if the server supports SymlinkAbsolutePathStrategy.ALLOWED. For each output directory requested in the `output_directories` field of the Action, if the directory existed after the action completed, a single entry will be present either in this field, or in the `output_directories` field, if the directory was not a symbolic link. If an output of the same name was found, but was a symbolic link to a file instead of a directory, the server will return a FAILED_PRECONDITION. If the action does not produce the requested output, then that output will be omitted from the list. The server is free to arrange the output list as desired; clients MUST NOT assume that the output list is sorted. DEPRECATED as of v2.1. Servers that wish to be compatible with v2.0 API should still populate this field in addition to `output_symlinks`.
*/
outputDirectorySymlinks?: Schema$BuildBazelRemoteExecutionV2OutputSymlink[];
/**
* The output files of the action. For each output file requested in the `output_files` or `output_paths` field of the Action, if the corresponding file existed after the action completed, a single entry will be present either in this field, or the `output_file_symlinks` field if the file was a symbolic link to another file (`output_symlinks` field after v2.1). If an output listed in `output_files` was found, but was a directory rather than a regular file, the server will return a FAILED_PRECONDITION. If the action does not produce the requested output, then that output will be omitted from the list. The server is free to arrange the output list as desired; clients MUST NOT assume that the output list is sorted.
*/
outputFiles?: Schema$BuildBazelRemoteExecutionV2OutputFile[];
/**
* The output files of the action that are symbolic links to other files. Those may be links to other output files, or input files, or even absolute paths outside of the working directory, if the server supports SymlinkAbsolutePathStrategy.ALLOWED. For each output file requested in the `output_files` or `output_paths` field of the Action, if the corresponding file existed after the action completed, a single entry will be present either in this field, or in the `output_files` field, if the file was not a symbolic link. If an output symbolic link of the same name as listed in `output_files` of the Command was found, but its target type was not a regular file, the server will return a FAILED_PRECONDITION. If the action does not produce the requested output, then that output will be omitted from the list. The server is free to arrange the output list as desired; clients MUST NOT assume that the output list is sorted. DEPRECATED as of v2.1. Servers that wish to be compatible with v2.0 API should still populate this field in addition to `output_symlinks`.
*/
outputFileSymlinks?: Schema$BuildBazelRemoteExecutionV2OutputSymlink[];
/**
* New in v2.1: this field will only be populated if the command `output_paths` field was used, and not the pre v2.1 `output_files` or `output_directories` fields. The output paths of the action that are symbolic links to other paths. Those may be links to other outputs, or inputs, or even absolute paths outside of the working directory, if the server supports SymlinkAbsolutePathStrategy.ALLOWED. A single entry for each output requested in `output_paths` field of the Action, if the corresponding path existed after the action completed and was a symbolic link. If the action does not produce a requested output, then that output will be omitted from the list. The server is free to arrange the output list as desired; clients MUST NOT assume that the output list is sorted.
*/
outputSymlinks?: Schema$BuildBazelRemoteExecutionV2OutputSymlink[];
/**
* The digest for a blob containing the standard error of the action, which can be retrieved from the ContentAddressableStorage.
*/
stderrDigest?: Schema$BuildBazelRemoteExecutionV2Digest;
/**
* The standard error buffer of the action. The server SHOULD NOT inline stderr unless requested by the client in the GetActionResultRequest message. The server MAY omit inlining, even if requested, and MUST do so if inlining would cause the response to exceed message size limits.
*/
stderrRaw?: string | null;
/**
* The digest for a blob containing the standard output of the action, which can be retrieved from the ContentAddressableStorage.
*/
stdoutDigest?: Schema$BuildBazelRemoteExecutionV2Digest;
/**
* The standard output buffer of the action. The server SHOULD NOT inline stdout unless requested by the client in the GetActionResultRequest message. The server MAY omit inlining, even if requested, and MUST do so if inlining would cause the response to exceed message size limits.
*/
stdoutRaw?: string | null;
}
/**
* A request message for ContentAddressableStorage.BatchReadBlobs.
*/
export interface Schema$BuildBazelRemoteExecutionV2BatchReadBlobsRequest {
/**
* The individual blob digests.
*/
digests?: Schema$BuildBazelRemoteExecutionV2Digest[];
}
/**
* A response message for ContentAddressableStorage.BatchReadBlobs.
*/
export interface Schema$BuildBazelRemoteExecutionV2BatchReadBlobsResponse {
/**
* The responses to the requests.
*/
responses?: Schema$BuildBazelRemoteExecutionV2BatchReadBlobsResponseResponse[];
}
/**
* A response corresponding to a single blob that the client tried to download.
*/
export interface Schema$BuildBazelRemoteExecutionV2BatchReadBlobsResponseResponse {
/**
* The raw binary data.
*/
data?: string | null;
/**
* The digest to which this response corresponds.
*/
digest?: Schema$BuildBazelRemoteExecutionV2Digest;
/**
* The result of attempting to download that blob.
*/
status?: Schema$GoogleRpcStatus;
}
/**
* A request message for ContentAddressableStorage.BatchUpdateBlobs.
*/
export interface Schema$BuildBazelRemoteExecutionV2BatchUpdateBlobsRequest {
/**
* The individual upload requests.
*/
requests?: Schema$BuildBazelRemoteExecutionV2BatchUpdateBlobsRequestRequest[];
}
/**
* A request corresponding to a single blob that the client wants to upload.
*/
export interface Schema$BuildBazelRemoteExecutionV2BatchUpdateBlobsRequestRequest {
/**
* The raw binary data.
*/
data?: string | null;
/**
* The digest of the blob. This MUST be the digest of `data`.
*/
digest?: Schema$BuildBazelRemoteExecutionV2Digest;
}
/**
* A response message for ContentAddressableStorage.BatchUpdateBlobs.
*/
export interface Schema$BuildBazelRemoteExecutionV2BatchUpdateBlobsResponse {
/**
* The responses to the requests.
*/
responses?: Schema$BuildBazelRemoteExecutionV2BatchUpdateBlobsResponseResponse[];
}
/**
* A response corresponding to a single blob that the client tried to upload.
*/
export interface Schema$BuildBazelRemoteExecutionV2BatchUpdateBlobsResponseResponse {
/**
* The blob digest to which this response corresponds.
*/
digest?: Schema$BuildBazelRemoteExecutionV2Digest;
/**
* The result of attempting to upload that blob.
*/
status?: Schema$GoogleRpcStatus;
}
/**
* Capabilities of the remote cache system.
*/
export interface Schema$BuildBazelRemoteExecutionV2CacheCapabilities {
/**
* Capabilities for updating the action cache.
*/
actionCacheUpdateCapabilities?: Schema$BuildBazelRemoteExecutionV2ActionCacheUpdateCapabilities;
/**
* Supported cache priority range for both CAS and ActionCache.
*/
cachePriorityCapabilities?: Schema$BuildBazelRemoteExecutionV2PriorityCapabilities;
/**
* All the digest functions supported by the remote cache. Remote cache may support multiple digest functions simultaneously.
*/
digestFunction?: string[] | null;
/**
* Maximum total size of blobs to be uploaded/downloaded using batch methods. A value of 0 means no limit is set, although in practice there will always be a message size limitation of the protocol in use, e.g. GRPC.
*/
maxBatchTotalSizeBytes?: string | null;
/**
* Compressors supported by the "compressed-blobs" bytestream resources. Servers MUST support identity/no-compression, even if it is not listed here. Note that this does not imply which if any compressors are supported by the server at the gRPC level.
*/
supportedCompressor?: string[] | null;
/**
* Whether absolute symlink targets are supported.
*/
symlinkAbsolutePathStrategy?: string | null;
}
/**
* A `Command` is the actual command executed by a worker running an Action and specifications of its environment. Except as otherwise required, the environment (such as which system libraries or binaries are available, and what filesystems are mounted where) is defined by and specific to the implementation of the remote execution API.
*/
export interface Schema$BuildBazelRemoteExecutionV2Command {
/**
* The arguments to the command. The first argument must be the path to the executable, which must be either a relative path, in which case it is evaluated with respect to the input root, or an absolute path.
*/
arguments?: string[] | null;
/**
* The environment variables to set when running the program. The worker may provide its own default environment variables; these defaults can be overridden using this field. Additional variables can also be specified. In order to ensure that equivalent Commands always hash to the same value, the environment variables MUST be lexicographically sorted by name. Sorting of strings is done by code point, equivalently, by the UTF-8 bytes.
*/
environmentVariables?: Schema$BuildBazelRemoteExecutionV2CommandEnvironmentVariable[];
/**
* A list of the output directories that the client expects to retrieve from the action. Only the listed directories will be returned (an entire directory structure will be returned as a Tree message digest, see OutputDirectory), as well as files listed in `output_files`. Other files or directories that may be created during command execution are discarded. The paths are relative to the working directory of the action execution. The paths are specified using a single forward slash (`/`) as a path separator, even if the execution platform natively uses a different separator. The path MUST NOT include a trailing slash, nor a leading slash, being a relative path. The special value of empty string is allowed, although not recommended, and can be used to capture the entire working directory tree, including inputs. In order to ensure consistent hashing of the same Action, the output paths MUST be sorted lexicographically by code point (or, equivalently, by UTF-8 bytes). An output directory cannot be duplicated or have the same path as any of the listed output files. An output directory is allowed to be a parent of another output directory. Directories leading up to the output directories (but not the output directories themselves) are created by the worker prior to execution, even if they are not explicitly part of the input root. DEPRECATED since 2.1: Use `output_paths` instead.
*/
outputDirectories?: string[] | null;
/**
* A list of the output files that the client expects to retrieve from the action. Only the listed files, as well as directories listed in `output_directories`, will be returned to the client as output. Other files or directories that may be created during command execution are discarded. The paths are relative to the working directory of the action execution. The paths are specified using a single forward slash (`/`) as a path separator, even if the execution platform natively uses a different separator. The path MUST NOT include a trailing slash, nor a leading slash, being a relative path. In order to ensure consistent hashing of the same Action, the output paths MUST be sorted lexicographically by code point (or, equivalently, by UTF-8 bytes). An output file cannot be duplicated, be a parent of another output file, or have the same path as any of the listed output directories. Directories leading up to the output files are created by the worker prior to execution, even if they are not explicitly part of the input root. DEPRECATED since v2.1: Use `output_paths` instead.
*/
outputFiles?: string[] | null;
/**
* A list of keys for node properties the client expects to retrieve for output files and directories. Keys are either names of string-based NodeProperty or names of fields in NodeProperties. In order to ensure that equivalent `Action`s always hash to the same value, the node properties MUST be lexicographically sorted by name. Sorting of strings is done by code point, equivalently, by the UTF-8 bytes. The interpretation of string-based properties is server-dependent. If a property is not recognized by the server, the server will return an `INVALID_ARGUMENT`.
*/
outputNodeProperties?: string[] | null;
/**
* A list of the output paths that the client expects to retrieve from the action. Only the listed paths will be returned to the client as output. The type of the output (file or directory) is not specified, and will be determined by the server after action execution. If the resulting path is a file, it will be returned in an OutputFile) typed field. If the path is a directory, the entire directory structure will be returned as a Tree message digest, see OutputDirectory) Other files or directories that may be created during command execution are discarded. The paths are relative to the working directory of the action execution. The paths are specified using a single forward slash (`/`) as a path separator, even if the execution platform natively uses a different separator. The path MUST NOT include a trailing slash, nor a leading slash, being a relative path. In order to ensure consistent hashing of the same Action, the output paths MUST be deduplicated and sorted lexicographically by code point (or, equivalently, by UTF-8 bytes). Directories leading up to the output paths are created by the worker prior to execution, even if they are not explicitly part of the input root. New in v2.1: this field supersedes the DEPRECATED `output_files` and `output_directories` fields. If `output_paths` is used, `output_files` and `output_directories` will be ignored!
*/
outputPaths?: string[] | null;
/**
* The platform requirements for the execution environment. The server MAY choose to execute the action on any worker satisfying the requirements, so the client SHOULD ensure that running the action on any such worker will have the same result. A detailed lexicon for this can be found in the accompanying platform.md. DEPRECATED as of v2.2: platform properties are now specified directly in the action. See documentation note in the Action for migration.
*/
platform?: Schema$BuildBazelRemoteExecutionV2Platform;
/**
* The working directory, relative to the input root, for the command to run in. It must be a directory which exists in the input tree. If it is left empty, then the action is run in the input root.
*/
workingDirectory?: string | null;
}
/**
* An `EnvironmentVariable` is one variable to set in the running program's environment.
*/
export interface Schema$BuildBazelRemoteExecutionV2CommandEnvironmentVariable {
/**
* The variable name.
*/
name?: string | null;
/**
* The variable value.
*/
value?: string | null;
}
/**
* A content digest. A digest for a given blob consists of the size of the blob and its hash. The hash algorithm to use is defined by the server. The size is considered to be an integral part of the digest and cannot be separated. That is, even if the `hash` field is correctly specified but `size_bytes` is not, the server MUST reject the request. The reason for including the size in the digest is as follows: in a great many cases, the server needs to know the size of the blob it is about to work with prior to starting an operation with it, such as flattening Merkle tree structures or streaming it to a worker. Technically, the server could implement a separate metadata store, but this results in a significantly more complicated implementation as opposed to having the client specify the size up-front (or storing the size along with the digest in every message where digests are embedded). This does mean that the API leaks some implementation details of (what we consider to be) a reasonable server implementation, but we consider this to be a worthwhile tradeoff. When a `Digest` is used to refer to a proto message, it always refers to the message in binary encoded form. To ensure consistent hashing, clients and servers MUST ensure that they serialize messages according to the following rules, even if there are alternate valid encodings for the same message: * Fields are serialized in tag order. * There are no unknown fields. * There are no duplicate fields. * Fields are serialized according to the default semantics for their type. Most protocol buffer implementations will always follow these rules when serializing, but care should be taken to avoid shortcuts. For instance, concatenating two messages to merge them may produce duplicate fields.
*/
export interface Schema$BuildBazelRemoteExecutionV2Digest {
/**
* The hash. In the case of SHA-256, it will always be a lowercase hex string exactly 64 characters long.
*/
hash?: string | null;
/**
* The size of the blob, in bytes.
*/
sizeBytes?: string | null;
}
/**
* A `Directory` represents a directory node in a file tree, containing zero or more children FileNodes, DirectoryNodes and SymlinkNodes. Each `Node` contains its name in the directory, either the digest of its content (either a file blob or a `Directory` proto) or a symlink target, as well as possibly some metadata about the file or directory. In order to ensure that two equivalent directory trees hash to the same value, the following restrictions MUST be obeyed when constructing a a `Directory`: * Every child in the directory must have a path of exactly one segment. Multiple levels of directory hierarchy may not be collapsed. * Each child in the directory must have a unique path segment (file name). Note that while the API itself is case-sensitive, the environment where the Action is executed may or may not be case-sensitive. That is, it is legal to call the API with a Directory that has both "Foo" and "foo" as children, but the Action may be rejected by the remote system upon execution. * The files, directories and symlinks in the directory must each be sorted in lexicographical order by path. The path strings must be sorted by code point, equivalently, by UTF-8 bytes. * The NodeProperties of files, directories, and symlinks must be sorted in lexicographical order by property name. A `Directory` that obeys the restrictions is said to be in canonical form. As an example, the following could be used for a file named `bar` and a directory named `foo` with an executable file named `baz` (hashes shortened for readability): ```json // (Directory proto) { files: [ { name: "bar", digest: { hash: "4a73bc9d03...", size: 65534 \}, node_properties: [ { "name": "MTime", "value": "2017-01-15T01:30:15.01Z" \} ] \} ], directories: [ { name: "foo", digest: { hash: "4cf2eda940...", size: 43 \} \} ] \} // (Directory proto with hash "4cf2eda940..." and size 43) { files: [ { name: "baz", digest: { hash: "b2c941073e...", size: 1294, \}, is_executable: true \} ] \} ```
*/
export interface Schema$BuildBazelRemoteExecutionV2Directory {
/**
* The subdirectories in the directory.
*/
directories?: Schema$BuildBazelRemoteExecutionV2DirectoryNode[];
/**
* The files in the directory.
*/
files?: Schema$BuildBazelRemoteExecutionV2FileNode[];
nodeProperties?: Schema$BuildBazelRemoteExecutionV2NodeProperties;
/**
* The symlinks in the directory.
*/
symlinks?: Schema$BuildBazelRemoteExecutionV2SymlinkNode[];
}
/**
* A `DirectoryNode` represents a child of a Directory which is itself a `Directory` and its associated metadata.
*/
export interface Schema$BuildBazelRemoteExecutionV2DirectoryNode {
/**
* The digest of the Directory object represented. See Digest for information about how to take the digest of a proto message.
*/
digest?: Schema$BuildBazelRemoteExecutionV2Digest;
/**
* The name of the directory.
*/
name?: string | null;
}
/**
* ExecutedActionMetadata contains details about a completed execution.
*/
export interface Schema$BuildBazelRemoteExecutionV2ExecutedActionMetadata {
/**
* Details that are specific to the kind of worker used. For example, on POSIX-like systems this could contain a message with getrusage(2) statistics.
*/
auxiliaryMetadata?: Array<{
[key: string]: any;
}> | null;
/**
* When the worker completed executing the action command.
*/
executionCompletedTimestamp?: string | null;
/**
* When the worker started executing the action command.
*/
executionStartTimestamp?: string | null;
/**
* When the worker finished fetching action inputs.
*/
inputFetchCompletedTimestamp?: string | null;
/**
* When the worker started fetching action inputs.
*/
inputFetchStartTimestamp?: string | null;
/**
* When the worker finished uploading action outputs.
*/
outputUploadCompletedTimestamp?: string | null;
/**
* When the worker started uploading action outputs.
*/
outputUploadStartTimestamp?: string | null;
/**
* When was the action added to the queue.
*/
queuedTimestamp?: string | null;
/**
* The name of the worker which ran the execution.
*/
worker?: string | null;
/**
* When the worker completed the action, including all stages.
*/
workerCompletedTimestamp?: string | null;
/**
* When the worker received the action.
*/
workerStartTimestamp?: string | null;
}
/**
* Metadata about an ongoing execution, which will be contained in the metadata field of the Operation.
*/
export interface Schema$BuildBazelRemoteExecutionV2ExecuteOperationMetadata {
/**
* The digest of the Action being executed.
*/
actionDigest?: Schema$BuildBazelRemoteExecutionV2Digest;
/**
* The current stage of execution.
*/
stage?: string | null;
/**
* If set, the client can use this resource name with ByteStream.Read to stream the standard error from the endpoint hosting streamed responses.
*/
stderrStreamName?: string | null;
/**
* If set, the client can use this resource name with ByteStream.Read to stream the standard output from the endpoint hosting streamed responses.
*/
stdoutStreamName?: string | null;
}
/**
* A request message for Execution.Execute.
*/
export interface Schema$BuildBazelRemoteExecutionV2ExecuteRequest {
/**
* The digest of the Action to execute.
*/
actionDigest?: Schema$BuildBazelRemoteExecutionV2Digest;
/**
* An optional policy for execution of the action. The server will have a default policy if this is not provided.
*/
executionPolicy?: Schema$BuildBazelRemoteExecutionV2ExecutionPolicy;
/**
* An optional policy for the results of this execution in the remote cache. The server will have a default policy if this is not provided. This may be applied to both the ActionResult and the associated blobs.
*/
resultsCachePolicy?: Schema$BuildBazelRemoteExecutionV2ResultsCachePolicy;
/**
* If true, the action will be executed even if its result is already present in the ActionCache. The execution is still allowed to be merged with other in-flight executions of the same action, however - semantically, the service MUST only guarantee that the results of an execution with this field set were not visible before the corresponding execution request was sent. Note that actions from execution requests setting this field set are still eligible to be entered into the action cache upon completion, and services SHOULD overwrite any existing entries that may exist. This allows skip_cache_lookup requests to be used as a mechanism for replacing action cache entries that reference outputs no longer available or that are poisoned in any way. If false, the result may be served from the action cache.
*/
skipCacheLookup?: boolean | null;
}
/**
* The response message for Execution.Execute, which will be contained in the response field of the Operation.
*/
export interface Schema$BuildBazelRemoteExecutionV2ExecuteResponse {
/**
* True if the result was served from cache, false if it was executed.
*/
cachedResult?: boolean | null;
/**
* Freeform informational message with details on the execution of the action that may be displayed to the user upon failure or when requested explicitly.
*/
message?: string | null;
/**
* The result of the action.
*/
result?: Schema$BuildBazelRemoteExecutionV2ActionResult;
/**
* An optional list of additional log outputs the server wishes to provide. A server can use this to return execution-specific logs however it wishes. This is intended primarily to make it easier for users to debug issues that may be outside of the actual job execution, such as by identifying the worker executing the action or by providing logs from the worker's setup phase. The keys SHOULD be human readable so that a client can display them to a user.
*/
serverLogs?: {
[key: string]: Schema$BuildBazelRemoteExecutionV2LogFile;
} | null;
/**
* If the status has a code other than `OK`, it indicates that the action did not finish execution. For example, if the operation times out during execution, the status will have a `DEADLINE_EXCEEDED` code. Servers MUST use this field for errors in execution, rather than the error field on the `Operation` object. If the status code is other than `OK`, then the result MUST NOT be cached. For an error status, the `result` field is optional; the server may populate the output-, stdout-, and stderr-related fields if it has any information available, such as the stdout and stderr of a timed-out action.
*/
status?: Schema$GoogleRpcStatus;
}
/**
* Capabilities of the remote execution system.
*/
export interface Schema$BuildBazelRemoteExecutionV2ExecutionCapabilities {
/**
* Remote execution may only support a single digest function.
*/
digestFunction?: string | null;
/**
* Whether remote execution is enabled for the particular server/instance.
*/
execEnabled?: boolean | null;
/**
* Supported execution priority range.
*/
executionPriorityCapabilities?: Schema$BuildBazelRemoteExecutionV2PriorityCapabilities;
/**
* Supported node properties.
*/
supportedNodeProperties?: string[] | null;
}
/**
* An `ExecutionPolicy` can be used to control the scheduling of the action.
*/
export interface Schema$BuildBazelRemoteExecutionV2ExecutionPolicy {
/**
* The priority (relative importance) of this action. Generally, a lower value means that the action should be run sooner than actions having a greater priority value, but the interpretation of a given value is server- dependent. A priority of 0 means the *default* priority. Priorities may be positive or negative, and such actions should run later or sooner than actions having the default priority, respectively. The particular semantics of this field is up to the server. In particular, every server will have their own supported range of priorities, and will decide how these map into scheduling policy.
*/
priority?: number | null;
}
/**
* A `FileNode` represents a single file and associated metadata.
*/
export interface Schema$BuildBazelRemoteExecutionV2FileNode {
/**
* The digest of the file's content.
*/
digest?: Schema$BuildBazelRemoteExecutionV2Digest;
/**
* True if file is executable, false otherwise.
*/
isExecutable?: boolean | null;
/**
* The name of the file.
*/
name?: string | null;
nodeProperties?: Schema$BuildBazelRemoteExecutionV2NodeProperties;
}
/**
* A request message for ContentAddressableStorage.FindMissingBlobs.
*/
export interface Schema$BuildBazelRemoteExecutionV2FindMissingBlobsRequest {
/**
* A list of the blobs to check.
*/
blobDigests?: Schema$BuildBazelRemoteExecutionV2Digest[];
}
/**
* A response message for ContentAddressableStorage.FindMissingBlobs.
*/
export interface Schema$BuildBazelRemoteExecutionV2FindMissingBlobsResponse {
/**
* A list of the blobs requested *not* present in the storage.
*/
missingBlobDigests?: Schema$BuildBazelRemoteExecutionV2Digest[];
}
/**
* A response message for ContentAddressableStorage.GetTree.
*/
export interface Schema$BuildBazelRemoteExecutionV2GetTreeResponse {
/**
* The directories descended from the requested root.
*/
directories?: Schema$BuildBazelRemoteExecutionV2Directory[];
/**
* If present, signifies that there are more results which the client can retrieve by passing this as the page_token in a subsequent request. If empty, signifies that this is the last page of results.
*/
nextPageToken?: string | null;
}
/**
* A `LogFile` is a log stored in the CAS.
*/
export interface Schema$BuildBazelRemoteExecutionV2LogFile {
/**
* The digest of the log contents.
*/
digest?: Schema$BuildBazelRemoteExecutionV2Digest;
/**
* This is a hint as to the purpose of the log, and is set to true if the log is human-readable text that can be usefully displayed to a user, and false otherwise. For instance, if a command-line client wishes to print the server logs to the terminal for a failed action, this allows it to avoid displaying a binary file.
*/
humanReadable?: boolean | null;
}
/**
* Node properties for FileNodes, DirectoryNodes, and SymlinkNodes. The server is responsible for specifying the properties that it accepts.
*/
export interface Schema$BuildBazelRemoteExecutionV2NodeProperties {
/**
* The file's last modification timestamp.
*/
mtime?: string | null;
/**
* A list of string-based NodeProperties.
*/
properties?: Schema$BuildBazelRemoteExecutionV2NodeProperty[];
/**
* The UNIX file mode, e.g., 0755.
*/
unixMode?: number | null;
}
/**
* A single property for FileNodes, DirectoryNodes, and SymlinkNodes. The server is responsible for specifying the property `name`s that it accepts. If permitted by the server, the same `name` may occur multiple times.
*/
export interface Schema$BuildBazelRemoteExecutionV2NodeProperty {
/**
* The property name.
*/
name?: string | null;
/**
* The property value.
*/
value?: string | null;
}
/**
* An `OutputDirectory` is the output in an `ActionResult` corresponding to a directory's full contents rather than a single file.
*/
export interface Schema$BuildBazelRemoteExecutionV2OutputDirectory {
/**
* The full path of the directory relative to the working directory. The path separator is a forward slash `/`. Since this is a relative path, it MUST NOT begin with a leading forward slash. The empty string value is allowed, and it denotes the entire working directory.
*/
path?: string | null;
/**
* The digest of the encoded Tree proto containing the directory's contents.
*/
treeDigest?: Schema$BuildBazelRemoteExecutionV2Digest;
}
/**
* An `OutputFile` is similar to a FileNode, but it is used as an output in an `ActionResult`. It allows a full file path rather than only a name.
*/
export interface Schema$BuildBazelRemoteExecutionV2OutputFile {
/**
* The contents of the file if inlining was requested. The server SHOULD NOT inline file contents unless requested by the client in the GetActionResultRequest message. The server MAY omit inlining, even if requested, and MUST do so if inlining would cause the response to exceed message size limits.
*/
contents?: string | null;
/**
* The digest of the file's content.
*/
digest?: Schema$BuildBazelRemoteExecutionV2Digest;
/**
* True if file is executable, false otherwise.
*/
isExecutable?: boolean | null;
nodeProperties?: Schema$BuildBazelRemoteExecutionV2NodeProperties;
/**
* The full path of the file relative to the working directory, including the filename. The path separator is a forward slash `/`. Since this is a relative path, it MUST NOT begin with a leading forward slash.
*/
path?: string | null;
}
/**
* An `OutputSymlink` is similar to a Symlink, but it is used as an output in an `ActionResult`. `OutputSymlink` is binary-compatible with `SymlinkNode`.
*/
export interface Schema$BuildBazelRemoteExecutionV2OutputSymlink {
nodeProperties?: Schema$BuildBazelRemoteExecutionV2NodeProperties;
/**
* The full path of the symlink relative to the working directory, including the filename. The path separator is a forward slash `/`. Since this is a relative path, it MUST NOT begin with a leading forward slash.
*/
path?: string | null;
/**
* The target path of the symlink. The path separator is a forward slash `/`. The target path can be relative to the parent directory of the symlink or it can be an absolute path starting with `/`. Support for absolute paths can be checked using the Capabilities API. `..` components are allowed anywhere in the target path.
*/
target?: string | null;
}
/**
* A `Platform` is a set of requirements, such as hardware, operating system, or compiler toolchain, for an Action's execution environment. A `Platform` is represented as a series of key-value pairs representing the properties that are required of the platform.
*/
export interface Schema$BuildBazelRemoteExecutionV2Platform {
/**
* The properties that make up this platform. In order to ensure that equivalent `Platform`s always hash to the same value, the properties MUST be lexicographically sorted by name, and then by value. Sorting of strings is done by code point, equivalently, by the UTF-8 bytes.
*/
properties?: Schema$BuildBazelRemoteExecutionV2PlatformProperty[];
}
/**
* A single property for the environment. The server is responsible for specifying the property `name`s that it accepts. If an unknown `name` is provided in the requirements for an Action, the server SHOULD reject the execution request. If permitted by the server, the same `name` may occur multiple times. The server is also responsible for specifying the interpretation of property `value`s. For instance, a property describing how much RAM must be available may be interpreted as allowing a worker with 16GB to fulfill a request for 8GB, while a property describing the OS environment on which the action must be performed may require an exact match with the worker's OS. The server MAY use the `value` of one or more properties to determine how it sets up the execution environment, such as by making specific system files available to the worker. Both names and values are typically case-sensitive. Note that the platform is implicitly part of the action digest, so even tiny changes in the names or values (like changing case) may result in different action cache entries.
*/
export interface Schema$BuildBazelRemoteExecutionV2PlatformProperty {
/**
* The property name.
*/
name?: string | null;
/**
* The property value.
*/
value?: string | null;
}
/**
* Allowed values for priority in ResultsCachePolicy and ExecutionPolicy Used for querying both cache and execution valid priority ranges.
*/
export interface Schema$BuildBazelRemoteExecutionV2PriorityCapabilities {
priorities?: Schema$BuildBazelRemoteExecutionV2PriorityCapabilitiesPriorityRange[];
}
/**
* Supported range of priorities, including boundaries.
*/
export interface Schema$BuildBazelRemoteExecutionV2PriorityCapabilitiesPriorityRange {
/**
* The maximum numeric value for this priority range, which represents the least urgent task or shortest retained item.
*/
maxPriority?: number | null;
/**
* The minimum numeric value for this priority range, which represents the most urgent task or longest retained item.
*/
minPriority?: number | null;
}
/**
* An optional Metadata to attach to any RPC request to tell the server about an external context of the request. The server may use this for logging or other purposes. To use it, the client attaches the header to the call using the canonical proto serialization: * name: `build.bazel.remote.execution.v2.requestmetadata-bin` * contents: the base64 encoded binary `RequestMetadata` message. Note: the gRPC library serializes binary headers encoded in base 64 by default (https://github.com/grpc/grpc/blob/master/doc/PROTOCOL-HTTP2.md#requests). Therefore, if the gRPC library is used to pass/retrieve this metadata, the user may ignore the base64 encoding and assume it is simply serialized as a binary message.
*/
export interface Schema$BuildBazelRemoteExecutionV2RequestMetadata {
/**
* An identifier that ties multiple requests to the same action. For example, multiple requests to the CAS, Action Cache, and Execution API are used in order to compile foo.cc.
*/
actionId?: string | null;
/**
* A brief description of the kind of action, for example, CppCompile or GoLink. There is no standard agreed set of values for this, and they are expected to vary between different client tools.
*/
actionMnemonic?: string | null;
/**
* An identifier for the configuration in which the target was built, e.g. for differentiating building host tools or different target platforms. There is no expectation that this value will have any particular structure, or equality across invocations, though some client tools may offer these guarantees.
*/
configurationId?: string | null;
/**
* An identifier to tie multiple tool invocations together. For example, runs of foo_test, bar_test and baz_test on a post-submit of a given patch.
*/
correlatedInvocationsId?: string | null;
/**
* An identifier for the