The OCID of the build pipeline.
The path to the build specification file for this environment. The default location of the file if not specified is build_spec.yaml.
The OCID of the compartment where the pipeline is created.
Defined tags for this resource. Each key is predefined and scoped to a namespace. See Resource Tags. Example: {@code {"foo-namespace": {"bar-key": "value"}}}
Optional description about the build stage.
Stage 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.
Image name for the build environment.
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 stage.
Name of the build source where the build_spec.yml file is located. If not specified, then the first entry in the build source collection is chosen as primary build source.
The OCID of the DevOps project.
Timeout for the build stage execution. Specify value in seconds. Note: Numbers greater than Number.MAX_SAFE_INTEGER will result in rounding issues.
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 stage was created. Format defined by RFC3339.
The time the stage was updated. Format defined by RFC3339.
Specifies the build stage.