Oracle Cloud Infrastructure DevOps Professional: Hands-On Workshop — Lesson 1: OCI DevOps Projects, Code Repositories, Build Pipelines, and Artifacts

Learning Objectives

• Explain the purpose and operating context of DevOps projects, notifications, repositories, branches, commits, and reviews.
• Apply build runners, build specifications, stages, environment variables, and caching and Artifact Registry repositories, versions, immutability, and provenance in a controlled environment.
• Validate outcomes and troubleshoot risks involving trigger rules, build evidence, failure analysis, and pipeline ownership.

Detailed Topics

• DevOps projects, notifications, repositories, branches, commits, and reviews
• build runners, build specifications, stages, environment variables, and caching
• Artifact Registry repositories, versions, immutability, and provenance
• trigger rules, build evidence, failure analysis, and pipeline ownership

Instructor Demonstration

Demonstrate DevOps projects, notifications, repositories, branches, commits, and reviews for a regulated application delivered from commit to production with auditable OCI DevOps controls; capture the exact configuration, code, command, transaction, query, dashboard, model, schedule, or report evidence that proves the expected result.

Hands-On Exercise

Complete a controlled Oracle Cloud Infrastructure DevOps Professional: Hands-On Workshop exercise covering build runners, build specifications, stages, environment variables, and caching and Artifact Registry repositories, versions, immutability, and provenance; introduce an exception involving trigger rules, build evidence, failure analysis, and pipeline ownership, diagnose it from evidence, apply the smallest reversible correction, and rerun acceptance checks.

1. Confirm scope, prerequisites, identities, dependencies, data, risks, and expected outcome.
2. Perform the course-specific configuration, development, administration, analysis, or business-process workflow.
3. Capture commands, settings, records, logs, screenshots, reports, metrics, or test results.
4. Compare the observed result with acceptance criteria and document corrective or preventive action.

Scenario Analysis

• Identify the technical or business decision and the stakeholders affected by it.
• Compare security, performance, reliability, compliance, cost, usability, and support trade-offs.
• Define rollback, recovery, communication, evidence, ownership, and escalation requirements.

Troubleshooting Guidance

Diagnose issues involving DevOps projects, notifications, repositories, branches, commits, and reviews, build runners, build specifications, stages, environment variables, and caching, Artifact Registry repositories, versions, immutability, and provenance, trigger rules, build evidence, failure analysis, and pipeline ownership without making an unverified production change. Separate symptoms from causes, gather time-correlated evidence, test a reversible hypothesis, validate the correction, and record recurrence controls.

Validation Checklist

• The requirement, environment, inputs, dependencies, and expected result are documented.
• The result is reproducible and supported by product-specific evidence.
• Normal, boundary, failure, security, performance, and operational conditions are reviewed.
• Exceptions, rollback, ownership, support actions, and the next improvement priority are recorded.

Lesson Outcome

Learners can apply OCI DevOps Projects, Code Repositories, Build Pipelines, and Artifacts in a realistic Oracle Cloud Infrastructure DevOps Professional: Hands-On Workshop scenario and defend the result with documented evidence.