Get desktop application:
View/edit binary Protocol Buffers messages
Cancel a currently running Bazel command. May return before the run command actually terminates.
Passed to CommandServer.cancel to initiate graceful cancellation of an in-flight command.
The client request cookie (see RunRequest.cookie).
The id of the command to cancel.
The server response cookie (see RunResponse.cookie).
Does not do anything. Used for liveness check.
Passed to CommandServer.ping to initiate a ping request.
The client request cookie (see RunRequest.cookie).
The server response cookie (see RunResponse.cookie).
Run a Bazel command. See documentation of argument/return messages for details.
Passed to CommandServer.run to initiate execution of a Bazel command.
Request cookie from the output base of the server. This serves as a rudimentary form of mutual authentication.
Command and command arguments. Does not include startup arguments.
Tells the server whether or not the client is willing to wait for any concurrent in-flight request to complete (there are many commands which may not run concurrently). If false and there are in-flight requests then the server will return an error immediately.
Whether the server should restrict itself to emitting only errors on the console.
A simple description of the client for reporting purposes. This value is required.
Invocation policy affects how command arguments are interpreted and should be passed separately. This is a proto message, either a human readable String or base64-encoded binary-serialized version of the message. It is not typed directly as an InvocationPolicy message due to distinctions between batch and server mode, so the parsing logic is only in the Java code.
Startup arguments, in the order they were applied, tagged with where they came from. These options have already been parsed and already have had their effect. This information should only be used for logging.
Whether the resulting command can be preempted if additional commands are received.
Additional per-command information passed to the server in the form of arbitrary messages which the server may be programmed to recognize and consume. Unrecognized message types are ignored.
Contains metadata and result data for a command execution.
Request cookie from the output base of the server. This serves as a rudimentary form of mutual authentication. Set on every response.
Standard out of the command, chunked. May be empty.
Standard error of the command, chunked. May be empty.
Whether this is the last message of the stream, signals that exit_code is valid.
The exit code of the command, only valid when finished is set.
Randomly generated command identifier, this may be used to cancel execution of the command by issuing a cancel call. This should be sent to the client as soon as possible. This is not required to be set (non-empty) on every response.
Whether the command has shut down the server; if set, the client should wait until the server process dies before finishing.
A command to exec() after the command invocation finishes. Should only be present if finished is set.
Fine-grained failure details. Should only be present if finished is set. WARNING: This functionality is experimental and should not be relied on at this time. TODO(mschaller): remove experimental warning
Additional per-command information passed by the server in the form of arbitrary messages.
Description of an environment variable
Used in:
Description of a request by the server to the client to execute a binary after the command invocation finishes.
Used in:
Represents paths to replace to allow localization of an ExecRequest when the build takes place on a different filesystem from where executing the ExecRequest would occur. In addition, the PathToReplace#Type enumeration is also reused to specify the possible base directory for a redirect output. The redirect output will be downloaded under one of the specified base directory in the downstream filesystem. TODO: b/331203854 - Rename this message to reflect both redirect output and ExecRequest use cases.
Used in:
Used in:
Represents the --script_path value and the run script contents for relevant run builds.
Used in:
Describes metadata necessary for connecting to and managing the server.
The server process's pid.
Address the CommandServer is listening on. Can be passed directly to grpc to create a connection.
Client request cookie.
Server response cookie.
Contains the a startup option with its source file. Uses bytes to preserve the way the user inputted the arguments, like the args in RunRequest.
Used in:
Startup option in --nullaryflag or --unaryflag=value form.
Where the option came from, such as an rc file or an empty string for the command line.