DO400 – Red Hat DevOps Pipelines and Processes: CI/CD with Jenkins, Git, and Test Driven Development — Lesson 1: DevOps Foundations, Git Collaboration, Branching, Reviews, and Change Control

Learning Objectives

• Explain the architecture, purpose, dependencies, and expected behavior of DevOps principles, Git repositories, and branching strategies.
• Apply code reviews and change control while preserving reviewable technical evidence.
• Recognize and correct the condition where an unstated prerequisite or ownership gap causes the initial design to be incomplete.

Detailed Topics

• DevOps principles: apply the concept to the course scenario, identify dependencies and controls, and record objective evidence of the result.
• Git repositories: apply the concept to the course scenario, identify dependencies and controls, and record objective evidence of the result.
• branching strategies: apply the concept to the course scenario, identify dependencies and controls, and record objective evidence of the result.
• code reviews: apply the concept to the course scenario, identify dependencies and controls, and record objective evidence of the result.
• change control: apply the concept to the course scenario, identify dependencies and controls, and record objective evidence of the result.

Instructor Demonstration

The instructor demonstrates devops foundations, git collaboration, branching, reviews, and change control by tracing architecture, commands, configuration, system messages, and evidence. The walkthrough tests how an unstated prerequisite or ownership gap causes the initial design to be incomplete and explains how to isolate the cause without masking related issues.

Hands-On Exercise

Establish a controlled baseline for DevOps Foundations, Git Collaboration, Branching, Reviews, and Change Control and add the verified result to the Git-based application repository, automated test suite, Jenkins pipeline, deployment evidence, and support guide.

1. Confirm scope, versions, access, dependencies, assumptions, and acceptance criteria.
2. Perform the workflow while recording commands, configuration, output, events, and decisions.
3. Test the normal path and one course-specific exception or boundary condition.
4. Retest the correction and document rollback, ownership, and follow-up actions.

Scenario Analysis

• Identify which dependency most strongly influences DevOps principles in the stated scenario.
• Compare two approaches for code reviews and explain the security, reliability, performance, and support trade-offs.
• Decide what evidence must be retained in the Git-based application repository, automated test suite, Jenkins pipeline, deployment evidence, and support guide before operational acceptance.

Troubleshooting Guidance

Begin with the first observable difference from the expected result. Check architecture, scope, identities, prerequisites, and starting conditions separately, then correlate logs, events, commands, metrics, and configuration history. Treat the assumption that an unstated prerequisite or ownership gap causes the initial design to be incomplete as a hypothesis until a reproducible retest confirms the cause.

Validation Checklist

• The required architecture, scope, identities, prerequisites, and starting conditions were checked and recorded.
• The normal path and a course-specific exception were tested.
• The Git-based application repository, automated test suite, Jenkins pipeline, deployment evidence, and support guide links conclusions to commands, configuration, logs, metrics, or other objective evidence.
• Corrective actions, rollback, ownership, and handover notes are complete.

Lesson Outcome

Learners can apply DevOps Foundations, Git Collaboration, Branching, Reviews, and Change Control, explain the observed platform behavior, and support the result with a reviewable Git-based application repository, automated test suite, Jenkins pipeline, deployment evidence, and support guide.