The OCID of the compartment where you want to create the pipeline run.
The OCID of the user who created the pipeline run.
Defined tags for this resource. Each key is predefined and scoped to a namespace. See Resource Tags. Example: {@code {"Operations": {"CostCenter": "42"}}}
A user-friendly display name for the resource.
Free-form tags for this resource. Each tag is a simple key-value pair with no predefined name, type, or namespace. See Resource Tags. Example: {@code {"Department": "Finance"}}
The OCID of the pipeline run.
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 state of the pipeline run.
The OCID of the pipeline for which pipeline run is created.
The OCID of the project to associate the pipeline run with.
Usage of system tag keys. These predefined keys are scoped to namespaces. Example: {@code {"orcl-cloud": {"free-tier-retained": "true"}}}
The date and time the pipeline run was accepted in the timestamp format defined by RFC3339.
The date and time the pipeline run request was finished in the timestamp format defined by RFC3339.
The date and time the pipeline run request was started in the timestamp format defined by RFC3339.
The date and time the pipeline run was updated in the timestamp format defined by RFC3339.
Summary of the PipelineRun.