All Downloads are FREE. Search and download functionalities are using the official Maven repository.

build.bazel.remote.execution.v2.ExecuteResponseOrBuilder Maven / Gradle / Ivy

// Generated by the protocol buffer compiler.  DO NOT EDIT!
// source: build/bazel/remote/execution/v2/remote_execution.proto

// Protobuf Java Version: 3.25.3
package build.bazel.remote.execution.v2;

public interface ExecuteResponseOrBuilder extends
    // @@protoc_insertion_point(interface_extends:build.bazel.remote.execution.v2.ExecuteResponse)
    com.google.protobuf.MessageOrBuilder {

  /**
   * 
   * The result of the action.
   * 
* * .build.bazel.remote.execution.v2.ActionResult result = 1; * @return Whether the result field is set. */ boolean hasResult(); /** *
   * The result of the action.
   * 
* * .build.bazel.remote.execution.v2.ActionResult result = 1; * @return The result. */ build.bazel.remote.execution.v2.ActionResult getResult(); /** *
   * The result of the action.
   * 
* * .build.bazel.remote.execution.v2.ActionResult result = 1; */ build.bazel.remote.execution.v2.ActionResultOrBuilder getResultOrBuilder(); /** *
   * True if the result was served from cache, false if it was executed.
   * 
* * bool cached_result = 2; * @return The cachedResult. */ boolean getCachedResult(); /** *
   * 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.
   * 
* * .google.rpc.Status status = 3; * @return Whether the status field is set. */ boolean hasStatus(); /** *
   * 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.
   * 
* * .google.rpc.Status status = 3; * @return The status. */ com.google.rpc.Status getStatus(); /** *
   * 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.
   * 
* * .google.rpc.Status status = 3; */ com.google.rpc.StatusOrBuilder getStatusOrBuilder(); /** *
   * 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.
   * 
* * map<string, .build.bazel.remote.execution.v2.LogFile> server_logs = 4; */ int getServerLogsCount(); /** *
   * 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.
   * 
* * map<string, .build.bazel.remote.execution.v2.LogFile> server_logs = 4; */ boolean containsServerLogs( java.lang.String key); /** * Use {@link #getServerLogsMap()} instead. */ @java.lang.Deprecated java.util.Map getServerLogs(); /** *
   * 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.
   * 
* * map<string, .build.bazel.remote.execution.v2.LogFile> server_logs = 4; */ java.util.Map getServerLogsMap(); /** *
   * 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.
   * 
* * map<string, .build.bazel.remote.execution.v2.LogFile> server_logs = 4; */ /* nullable */ build.bazel.remote.execution.v2.LogFile getServerLogsOrDefault( java.lang.String key, /* nullable */ build.bazel.remote.execution.v2.LogFile defaultValue); /** *
   * 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.
   * 
* * map<string, .build.bazel.remote.execution.v2.LogFile> server_logs = 4; */ build.bazel.remote.execution.v2.LogFile getServerLogsOrThrow( java.lang.String key); /** *
   * Freeform informational message with details on the execution of the action
   * that may be displayed to the user upon failure or when requested explicitly.
   * 
* * string message = 5; * @return The message. */ java.lang.String getMessage(); /** *
   * Freeform informational message with details on the execution of the action
   * that may be displayed to the user upon failure or when requested explicitly.
   * 
* * string message = 5; * @return The bytes for message. */ com.google.protobuf.ByteString getMessageBytes(); }




© 2015 - 2024 Weber Informatics LLC | Privacy Policy