Get desktop application:
View/edit binary Protocol Buffers messages
Creates and manages builds on Google Cloud Platform. The main concept used by this API is a `Build`, which describes the location of the source to build, how to build the source, and where to store the built artifacts, if any. A user can list previously-requested builds or get builds by their ID to determine the status of the build.
Starts a build with the specified configuration. This method returns a long-running `Operation`, which includes the build ID. Pass the build ID to `GetBuild` to determine the build status (such as `SUCCESS` or `FAILURE`).
Request to create a new build.
Required. ID of the project.
Required. Build resource to create.
Returns information about a previously requested build. The `Build` that is returned includes its status (such as `SUCCESS`, `FAILURE`, or `WORKING`), and timing information.
Request to get a build.
Required. ID of the project.
Required. ID of the build.
Lists previously requested builds. Previously requested builds may still be in-progress, or may have finished successfully or unsuccessfully.
Request to list builds.
Required. ID of the project.
Number of results to return in the list.
Token to provide to skip to a particular spot in the list.
The raw filter text to constrain the results.
Response including listed builds.
Builds will be sorted by `create_time`, descending.
Token to receive the next page of results.
Cancels a build in progress.
Request to cancel an ongoing build.
Required. ID of the project.
Required. ID of the build.
Creates a new build based on the specified build. This method creates a new build using the original build request, which may or may not result in an identical build. For triggered builds: * Triggered builds resolve to a precise revision; therefore a retry of a triggered build will result in a build that uses the same revision. For non-triggered builds that specify `RepoSource`: * If the original build built from the tip of a branch, the retried build will build from the tip of that branch, which may not be the same revision as the original build. * If the original build specified a commit sha or revision ID, the retried build will use the identical source. For builds that specify `StorageSource`: * If the original build pulled source from Google Cloud Storage without specifying the generation of the object, the new build will use the current object, which may be different from the original build source. * If the original build pulled source from Cloud Storage and specified the generation of the object, the new build will attempt to use the same object, which may or may not be available depending on the bucket's lifecycle management settings.
Specifies a build to retry.
Required. ID of the project.
Required. Build ID of the original build.
Creates a new `BuildTrigger`. This API is experimental.
Request to create a new `BuildTrigger`.
Required. ID of the project for which to configure automatic builds.
Required. `BuildTrigger` to create.
Returns information about a `BuildTrigger`. This API is experimental.
Returns the `BuildTrigger` with the specified ID.
Required. ID of the project that owns the trigger.
Required. ID of the `BuildTrigger` to get.
Lists existing `BuildTrigger`s. This API is experimental.
Request to list existing `BuildTriggers`.
Required. ID of the project for which to list BuildTriggers.
Number of results to return in the list.
Token to provide to skip to a particular spot in the list.
Response containing existing `BuildTriggers`.
`BuildTriggers` for the project, sorted by `create_time` descending.
Token to receive the next page of results.
Deletes a `BuildTrigger` by its project ID and trigger ID. This API is experimental.
Request to delete a `BuildTrigger`.
Required. ID of the project that owns the trigger.
Required. ID of the `BuildTrigger` to delete.
Updates a `BuildTrigger` by its project ID and trigger ID. This API is experimental.
Request to update an existing `BuildTrigger`.
Required. ID of the project that owns the trigger.
Required. ID of the `BuildTrigger` to update.
Required. `BuildTrigger` to update.
Runs a `BuildTrigger` at a particular source revision.
Specifies a build trigger to run and the source to use.
Required. ID of the project.
Required. ID of the trigger.
Required. Source to build against this trigger.
Creates a `WorkerPool` to run the builds, and returns the new worker pool. This API is experimental.
Request to create a new `WorkerPool`.
ID of the parent project.
`WorkerPool` resource to create.
Returns information about a `WorkerPool`. This API is experimental.
Request to get a `WorkerPool` with the specified name.
The field will contain name of the resource requested, for example: "projects/project-1/workerPools/workerpool-name"
Deletes a `WorkerPool` by its project ID and WorkerPool name. This API is experimental.
Request to delete a `WorkerPool`.
The field will contain name of the resource requested, for example: "projects/project-1/workerPools/workerpool-name"
Update a `WorkerPool`. This API is experimental.
Request to update a `WorkerPool`.
The field will contain name of the resource requested, for example: "projects/project-1/workerPools/workerpool-name"
`WorkerPool` resource to update.
List project's `WorkerPool`s. This API is experimental.
Request to list `WorkerPool`s.
ID of the parent project.
Response containing existing `WorkerPools`.
`WorkerPools` for the project.
An artifact that was uploaded during a build. This is a single record in the artifact manifest JSON file.
The path of an artifact in a Google Cloud Storage bucket, with the generation number. For example, `gs://mybucket/path/to/output.jar#generation`.
The file hash of the artifact.
Artifacts produced by a build that should be uploaded upon successful completion of all build steps.
Used in:
A list of images to be pushed upon the successful completion of all build steps. The images will be pushed using the builder service account's credentials. The digests of the pushed images will be stored in the Build resource's results field. If any of the images fail to be pushed, the build is marked FAILURE.
A list of objects to be uploaded to Cloud Storage upon successful completion of all build steps. Files in the workspace matching specified paths globs will be uploaded to the specified Cloud Storage location using the builder service account's credentials. The location and generation of the uploaded objects will be stored in the Build resource's results field. If any objects fail to be pushed, the build is marked FAILURE.
Files in the workspace to upload to Cloud Storage upon successful completion of all build steps.
Used in:
Cloud Storage bucket and optional object path, in the form "gs://bucket/path/to/somewhere/". (see [Bucket Name Requirements](https://cloud.google.com/storage/docs/bucket-naming#requirements)). Files in the workspace matching any path pattern will be uploaded to Cloud Storage with this location as a prefix.
Path globs used to match files in the build's workspace.
Output only. Stores timing information for pushing all artifact objects.
A build resource in the Cloud Build API. At a high level, a `Build` describes where to find source code, how to build it (for example, the builder image to run on the source), and where to store the built artifacts. Fields can include the following variables, which will be expanded when the build is created: - $PROJECT_ID: the project ID of the build. - $BUILD_ID: the autogenerated ID of the build. - $REPO_NAME: the source repository name specified by RepoSource. - $BRANCH_NAME: the branch name specified by RepoSource. - $TAG_NAME: the tag name specified by RepoSource. - $REVISION_ID or $COMMIT_SHA: the commit SHA specified by RepoSource or resolved from the specified branch or tag. - $SHORT_SHA: first 7 characters of $REVISION_ID or $COMMIT_SHA.
Used as response type in: CloudBuild.CancelBuild, CloudBuild.GetBuild
Used as field type in:
, , ,Output only. Unique identifier of the build.
Output only. ID of the project.
Output only. Status of the build.
Output only. Customer-readable message about the current status.
The location of the source files to build.
Required. The operations to be performed on the workspace.
Output only. Results of the build.
Output only. Time at which the request to create the build was received.
Output only. Time at which execution of the build was started.
Output only. Time at which execution of the build was finished. The difference between finish_time and start_time is the duration of the build's execution.
Amount of time that this build should be allowed to run, to second granularity. If this amount of time elapses, work on the build will cease and the build status will be `TIMEOUT`. Default time is ten minutes.
A list of images to be pushed upon the successful completion of all build steps. The images are pushed using the builder service account's credentials. The digests of the pushed images will be stored in the `Build` resource's results field. If any of the images fail to be pushed, the build status is marked `FAILURE`.
Artifacts produced by the build that should be uploaded upon successful completion of all build steps.
Google Cloud Storage bucket where logs should be written (see [Bucket Name Requirements](https://cloud.google.com/storage/docs/bucket-naming#requirements)). Logs file names will be of the format `${logs_bucket}/log-${build_id}.txt`.
Output only. A permanent fixed identifier for source.
Output only. The ID of the `BuildTrigger` that triggered this build, if it was triggered automatically.
Special options for this build.
Output only. URL to logs for this build in Google Cloud Console.
Substitutions data for `Build` resource.
Tags for annotation of a `Build`. These are not docker tags.
Secrets to decrypt using Cloud Key Management Service.
Output only. Stores timing information for phases of the build. Valid keys are: * BUILD: time to execute all build steps * PUSH: time to push all specified images. * FETCHSOURCE: time to fetch source. If the build does not specify source or images, these keys will not be included.
Possible status of a build or build step.
Used in:
,Status of the build is unknown.
Build or step is queued; work has not yet begun.
Build or step is being executed.
Build or step finished successfully.
Build or step failed to complete successfully.
Build or step failed due to an internal cause.
Build or step took longer than was allowed.
Build or step was canceled by a user.
Metadata for build operations.
The build that the operation is tracking.
Optional arguments to enable specific features of builds.
Used in:
Requested hash for SourceProvenance.
Requested verifiability options.
Compute Engine machine type on which to run the build.
Requested disk size for the VM that runs the build. Note that this is *NOT* "disk free"; some of the space will be used by the operating system and build utilities. Also note that this is the minimum disk size that will be allocated for the build -- the build may run with a larger disk than requested. At present, the maximum disk size is 1000GB; builds that request more than the maximum are rejected with an error.
Option to specify behavior when there is an error in the substitution checks.
Option to define build log streaming behavior to Google Cloud Storage.
Option to specify a `WorkerPool` for the build. User specifies the pool with the format "[WORKERPOOL_PROJECT_ID]/[WORKERPOOL_NAME]". This is an experimental field.
Option to specify the logging mode, which determines where the logs are stored.
A list of global environment variable definitions that will exist for all build steps in this build. If a variable is defined in both globally and in a build step, the variable will use the build step value. The elements are of the form "KEY=VALUE" for the environment variable "KEY" being given the value "VALUE".
A list of global environment variables, which are encrypted using a Cloud Key Management Service crypto key. These values must be specified in the build's `Secret`. These variables will be available to all build steps in this build.
Global list of volumes to mount for ALL build steps Each volume is created as an empty volume prior to starting the build process. Upon completion of the build, volumes and their contents are discarded. Global volume names and paths cannot conflict with the volumes defined a build step. Using a global volume in a build with only one step is not valid as it is indicative of a build request with an incorrect configuration.
Specifies the behavior when writing build logs to Google Cloud Storage.
Used in:
Service may automatically determine build log streaming behavior.
Build logs should be streamed to Google Cloud Storage.
Build logs should not be streamed to Google Cloud Storage; they will be written when the build is completed.
Specifies the logging mode.
Used in:
The service determines the logging mode. The default is `LEGACY`. Do not rely on the default logging behavior as it may change in the future.
Stackdriver logging and Cloud Storage logging are enabled.
Only Cloud Storage logging is enabled.
Supported VM sizes.
Used in:
Standard machine type.
Highcpu machine with 8 CPUs.
Highcpu machine with 32 CPUs.
Specifies the behavior when there is an error in the substitution checks.
Used in:
Fails the build if error in substitutions checks, like missing a substitution in the template or in the map.
Do not fail the build if error in substitutions checks.
Specifies the manner in which the build should be verified, if at all.
Used in:
Not a verifiable build. (default)
Verified build.
A step in the build pipeline.
Used in:
Required. The name of the container image that will run this particular build step. If the image is available in the host's Docker daemon's cache, it will be run directly. If not, the host will attempt to pull the image first, using the builder service account's credentials if necessary. The Docker daemon's cache will already have the latest versions of all of the officially supported build steps ([https://github.com/GoogleCloudPlatform/cloud-builders](https://github.com/GoogleCloudPlatform/cloud-builders)). The Docker daemon will also have cached many of the layers for some popular images, like "ubuntu", "debian", but they will be refreshed at the time you attempt to use them. If you built an image in a previous build step, it will be stored in the host's Docker daemon's cache and is available to use as the name for a later build step.
A list of environment variable definitions to be used when running a step. The elements are of the form "KEY=VALUE" for the environment variable "KEY" being given the value "VALUE".
A list of arguments that will be presented to the step when it is started. If the image used to run the step's container has an entrypoint, the `args` are used as arguments to that entrypoint. If the image does not define an entrypoint, the first element in args is used as the entrypoint, and the remainder will be used as arguments.
Working directory to use when running this step's container. If this value is a relative path, it is relative to the build's working directory. If this value is absolute, it may be outside the build's working directory, in which case the contents of the path may not be persisted across build step executions, unless a `volume` for that path is specified. If the build specifies a `RepoSource` with `dir` and a step with a `dir`, which specifies an absolute path, the `RepoSource` `dir` is ignored for the step's execution.
Unique identifier for this build step, used in `wait_for` to reference this build step as a dependency.
The ID(s) of the step(s) that this build step depends on. This build step will not start until all the build steps in `wait_for` have completed successfully. If `wait_for` is empty, this build step will start when all previous build steps in the `Build.Steps` list have completed successfully.
Entrypoint to be used instead of the build step image's default entrypoint. If unset, the image's default entrypoint is used.
A list of environment variables which are encrypted using a Cloud Key Management Service crypto key. These values must be specified in the build's `Secret`.
List of volumes to mount into the build step. Each volume is created as an empty volume prior to execution of the build step. Upon completion of the build, volumes and their contents are discarded. Using a named volume in only one step is not valid as it is indicative of a build request with an incorrect configuration.
Output only. Stores timing information for executing this build step.
Output only. Stores timing information for pulling this build step's builder image only.
Time limit for executing this build step. If not defined, the step has no time limit and will be allowed to continue to run until either it completes or the build itself times out.
Output only. Status of the build step. At this time, build step status is only updated on build completion; step status is not updated in real-time as the build progresses.
Configuration for an automated build in response to source repository changes.
Used as response type in: CloudBuild.CreateBuildTrigger, CloudBuild.GetBuildTrigger, CloudBuild.UpdateBuildTrigger
Used as field type in:
, ,Output only. Unique identifier of the trigger.
Human-readable description of this trigger.
User assigned name of the trigger. Must be unique within the project.
Tags for annotation of a `BuildTrigger`
Template describing the types of source changes to trigger a build. Branch and tag names in trigger templates are interpreted as regular expressions. Any branch or tag change that matches that regular expression will trigger a build. Mutually exclusive with `github`.
GitHubEventsConfig describes the configuration of a trigger that creates a build whenever a GitHub event is received. Mutually exclusive with `trigger_template`.
Template describing the Build request to make when the trigger is matched.
Contents of the build template.
Path, from the source root, to a file whose contents is used for the template.
Output only. Time when the trigger was created.
If true, the trigger will never result in a build.
Substitutions data for Build resource.
ignored_files and included_files are file glob matches using http://godoc/pkg/path/filepath#Match extended with support for "**". If ignored_files and changed files are both empty, then they are not used to determine whether or not to trigger a build. If ignored_files is not empty, then we ignore any files that match any of the ignored_file globs. If the change has no files that are outside of the ignored_files globs, then we do not trigger a build.
If any of the files altered in the commit pass the ignored_files filter and included_files is empty, then as far as this filter is concerned, we should trigger the build. If any of the files altered in the commit pass the ignored_files filter and included_files is not empty, then we make sure that at least one of those files matches a included_files glob. If not, then we do not trigger a build.
An image built by the pipeline.
Used in:
Name used to push the container image to Google Container Registry, as presented to `docker push`.
Docker Registry 2.0 digest.
Output only. Stores timing information for pushing the specified image.
Container message for hashes of byte content of files, used in SourceProvenance messages to verify integrity of source input to the build.
Used in:
,Collection of file hashes.
GitHubEventsConfig describes the configuration of a trigger that creates a build whenever a GitHub event is received. This message is experimental.
Used in:
The installationID that emits the GitHub event.
Owner of the repository. For example: The owner for https://github.com/googlecloudplatform/cloud-builders is "googlecloudplatform".
Name of the repository. For example: The name for https://github.com/googlecloudplatform/cloud-builders is "cloud-builders".
Filter describing the types of events to trigger a build. Currently supported event types: push, pull_request.
filter to match changes in pull requests.
filter to match changes in refs like branches, tags.
Container message for hash values.
Used in:
The type of hash that was performed.
The hash value.
Specifies the hash algorithm, if any.
Used in:
,No hash requested.
Use a sha256 hash.
Use a md5 hash.
Network describes the GCP network used to create workers in.
Used in:
Project id containing the defined network and subnetwork. For a peered VPC, this will be the same as the project_id in which the workers are created. For a shared VPC, this will be the project sharing the network with the project_id project in which workers will be created. For custom workers with no VPC, this will be the same as project_id.
Network on which the workers are created. "default" network is used if empty.
Subnetwork on which the workers are created. "default" subnetwork is used if empty.
PullRequestFilter contains filter properties for matching GitHub Pull Requests.
Used in:
Target refs to match. A target ref is the git reference where the pull request will be applied.
Regex of branches to match. The syntax of the regular expressions accepted is the syntax accepted by RE2 and described at https://github.com/google/re2/wiki/Syntax
Whether to block builds on a "/gcbrun" comment from a repository owner or collaborator.
Controls behavior of Pull Request comments.
Used in:
Do not require comments on Pull Requests before builds are triggered.
Enforce that repository owners or collaborators must comment on Pull Requests before builds are triggered.
Push contains filter properties for matching GitHub git pushes.
Used in:
Modified refs to match. A modified refs are the refs modified by a git push operation.
Regexes matching branches to build. The syntax of the regular expressions accepted is the syntax accepted by RE2 and described at https://github.com/google/re2/wiki/Syntax
Regexes matching tags to build. The syntax of the regular expressions accepted is the syntax accepted by RE2 and described at https://github.com/google/re2/wiki/Syntax
Location of the source in a Google Cloud Source Repository.
Used in:
, , ,ID of the project that owns the Cloud Source Repository. If omitted, the project ID requesting the build is assumed.
Name of the Cloud Source Repository. If omitted, the name "default" is assumed.
A revision within the Cloud Source Repository must be specified in one of these ways.
Regex matching branches to build. The syntax of the regular expressions accepted is the syntax accepted by RE2 and described at https://github.com/google/re2/wiki/Syntax
Regex matching tags to build. The syntax of the regular expressions accepted is the syntax accepted by RE2 and described at https://github.com/google/re2/wiki/Syntax
Explicit commit SHA to build.
Directory, relative to the source root, in which to run the build. This must be a relative path. If a step's `dir` is specified and is an absolute path, this value is ignored for that step's execution.
Artifacts created by the build pipeline.
Used in:
Container images that were built as a part of the build.
List of build step digests, in the order corresponding to build step indices.
Path to the artifact manifest. Only populated when artifacts are uploaded.
Number of artifacts uploaded. Only populated when artifacts are uploaded.
List of build step outputs, produced by builder images, in the order corresponding to build step indices. [Cloud Builders](https://cloud.google.com/cloud-build/docs/cloud-builders) can produce this output by writing to `$BUILDER_OUTPUT/output`. Only the first 4KB of data is stored.
Time to push all non-container artifacts.
Pairs a set of secret environment variables containing encrypted values with the Cloud KMS key to use to decrypt the value.
Used in:
Cloud KMS key name to use to decrypt these envs.
Map of environment variable name to its encrypted value. Secret environment variables must be unique across all of a build's secrets, and must be used by at least one build step. Values can be at most 64 KB in size. There can be at most 100 secret values across all of a build's secrets.
Location of the source in a supported storage service.
Used in:
Location of source.
If provided, get the source from this location in Google Cloud Storage.
If provided, get the source from this location in a Cloud Source Repository.
Provenance of the source. Ways to find the original source, or verify that some source was used for this build.
Used in:
A copy of the build's `source.storage_source`, if exists, with any generations resolved.
A copy of the build's `source.repo_source`, if exists, with any revisions resolved.
Output only. Hash(es) of the build source, which can be used to verify that the original source integrity was maintained in the build. Note that `FileHashes` will only be populated if `BuildOptions` has requested a `SourceProvenanceHash`. The keys to this map are file paths used as build source and the values contain the hash values for those files. If the build source came in a single package such as a gzipped tarfile (`.tar.gz`), the `FileHash` will be for the single path to that file.
Location of the source in an archive file in Google Cloud Storage.
Used in:
,Google Cloud Storage bucket containing the source (see [Bucket Name Requirements](https://cloud.google.com/storage/docs/bucket-naming#requirements)).
Google Cloud Storage object containing the source. This object must be a gzipped archive file (`.tar.gz`) containing source to build.
Google Cloud Storage generation for the object. If the generation is omitted, the latest generation will be used.
Start and end times for a build execution phase.
Used in:
, , , ,Start of time span.
End of time span.
Volume describes a Docker container volume which is mounted into build steps in order to persist files across build step execution.
Used in:
,Name of the volume to mount. Volume names must be unique per build step and must be valid names for Docker volumes. Each named volume must be used by at least two build steps.
Path at which to mount the volume. Paths must be absolute and cannot conflict with other volume paths on the same build step or with certain reserved volume paths.
WorkerConfig defines the configuration to be used for a creating workers in the pool.
Used in:
Machine Type of the worker, such as n1-standard-1. See https://cloud.google.com/compute/docs/machine-types. If left blank, Cloud Build will use a standard unspecified machine to create the worker pool. `machine_type` is overridden if you specify a different machine type in `build_options`. In this case, the VM specified in the `build_options` will be created on demand at build time. For more information see https://cloud.google.com/cloud-build/docs/speeding-up-builds#using_custom_virtual_machine_sizes
Size of the disk attached to the worker, in GB. See https://cloud.google.com/compute/docs/disks/ If `0` is specified, Cloud Build will use a standard disk size. `disk_size` is overridden if you specify a different disk size in `build_options`. In this case, a VM with a disk size specified in the `build_options` will be created on demand at build time. For more information see https://cloud.google.com/cloud-build/docs/api/reference/rest/v1/projects.builds#buildoptions
The network definition used to create the worker. If this section is left empty, the workers will be created in WorkerPool.project_id on the default network.
The tag applied to the worker, and the same tag used by the firewall rule. It is used to identify the Cloud Build workers among other VMs. The default value for tag is `worker`.
Configuration for a WorkerPool to run the builds. Workers are machines that Cloud Build uses to run your builds. By default, all workers run in a project owned by Cloud Build. To have full control over the workers that execute your builds -- such as enabling them to access private resources on your private network -- you can request Cloud Build to run the workers in your own project by creating a custom workers pool.
Used as response type in: CloudBuild.CreateWorkerPool, CloudBuild.GetWorkerPool, CloudBuild.UpdateWorkerPool
Used as field type in:
, ,User-defined name of the `WorkerPool`.
The project ID of the GCP project for which the `WorkerPool` is created.
Output only. The service account used to manage the `WorkerPool`. The service account must have the Compute Instance Admin (Beta) permission at the project level.
Total number of workers to be created across all requested regions.
Configuration to be used for a creating workers in the `WorkerPool`.
List of regions to create the `WorkerPool`. Regions can't be empty. If Cloud Build adds a new GCP region in the future, the existing `WorkerPool` will not be enabled in the new region automatically; you must add the new region to the `regions` field to enable the `WorkerPool` in that region.
Output only. Time at which the request to create the `WorkerPool` was received.
Output only. Time at which the request to update the `WorkerPool` was received.
Output only. Time at which the request to delete the `WorkerPool` was received.
Output only. WorkerPool Status.
Supported GCP regions to create the `WorkerPool`.
Used in:
no region
us-central1 region
us-west1 region
us-east1 region
us-east4 region
`WorkerPool` status
Used in:
Status of the `WorkerPool` is unknown.
`WorkerPool` is being created.
`WorkerPool` is running.
`WorkerPool` is being deleting: cancelling builds and draining workers.
`WorkerPool` is deleted.