The OCID of the build pipeline.
The OCID of the compartment where the build is running.
Defined tags for this resource. Each key is predefined and scoped to a namespace. See Resource Tags. Example: {@code {"foo-namespace": {"bar-key": "value"}}}
Build run display name, which can be renamed and is not necessarily unique. Avoid entering confidential information.
Simple key-value pair that is applied without any predefined name, type or scope. Exists for cross-compatibility only. See Resource Tags. Example: {@code {"bar-key": "value"}}
Unique identifier that is immutable on creation.
A message describing the current state in more detail. For example, can be used to provide actionable information for a resource in Failed state.
The current state of the build run.
The OCID of the DevOps project.
Usage of system tag keys. These predefined keys are scoped to namespaces. See Resource Tags. Example: {@code {"orcl-cloud": {"free-tier-retained": "true"}}}
The time the build run was created. Format defined by RFC3339.
The time the build run was updated. Format defined by RFC3339.
Each time you attempt to run a build pipeline you create one build run. A build can be running currently, or it can be a record of the run that happened in the past. The set of build runs constitutes a build pipeline's history.