OCI DevOps Pro cheat sheet

OCI DevOps is a managed continuous delivery service composed of four resource types: projects, build pipelines, deploy pipelines, and connections; artifacts and environments are supporting resources.

A build pipeline runs stages in order: Managed Build (runs build specs), Deliver Artifact (copies an artifact version to a target artifact repository), Trigger (manual or external event), and Wait (approval gate).

Deploy pipeline stage types: Rolling deploy, Blue-green deploy (OKE), Canary deploy (OKE), Load balancer (blue-green via traffic shifting), Wait, and Approval; manual approval is required before a Wait/approval stage releases.

Build specs are YAML files; key fields include version, component, steps (type: Command or Shell), and each step's name and command. A build run executes all steps sequentially in a managed build runner.

Build runner shapes are selectable (e.g., small/medium/large) and billed per build-minute; the pipeline's build stage references a build spec file stored in a code repository.

Deployment environments reference a specific target: OKE cluster, Compute instance group, Functions application, or load balancer; a deploy pipeline selects the environment per stage.

Artifacts are stored in OCI Artifact Registry (generic repositories); the Deliver Artifact stage replaces a placeholder in the artifact version with the build output.

Triggers can be manual, or automatic via a DevOps trigger of type GitHub, GitLab, Bitbucket Cloud, or VBS; the trigger fires on push/PR events and passes the commit reference to the build.

Connections store credentials for external systems (GitHub, GitLab, Bitbucket, VBS, external artifact repositories); a connection is referenced by a pipeline, not embedded as plaintext.

Pipelines and their stages have states such as Active, Inactive, and Deleted; deleting a project requires deleting or deactivating dependent pipelines first.

Build pipeline run history retains logs per step; the run's status is one of Succeeded, Failed, Canceled, or In progress.

Blue-green on OKE: the stage deploys a new ReplicaSet, shifts traffic after the new version is healthy, and keeps the prior version available for rollback; canary uses a percentage of traffic before full promotion.

Rolling deploy on Compute uses an instance group and a deployment policy (batch size, wait time) to update instances in waves.

IAM policies grant manage/use/inspect on devops-projects, devops-pipelines, devops-build-runs, devops-deployments, and devops-connections; the deployment principal is the user who created the pipeline run.

DevOps integrates with OCI Logging for build and deploy logs and with OCI Notifications for pipeline event topics; configure a notification topic on the project.

A build run can use a private endpoint (build runner in a VCN) to reach private resources such as a private OKE API endpoint or internal artifact repository.

Artifact versions are immutable; re-delivering the same version name fails, so builds should tag with commit SHA or build number to avoid overwrite.

DevOps supports approval stages with approver lists; only users in the approver list can approve, and the pipeline pauses until approval or timeout.