DevOps Foundations (CI/CD, Docker)

Real portfolio pieces built during the course, not a certificate for its own sake. Each one is work you can show.

• Commented pipeline definitionA working CI/CD pipeline file for one service, with a commentary column that states what each stage actually guarantees and what it does not. The artifact is the reasoning as much as the YAML.
• Dockerfile and compose setupA multi stage Dockerfile that builds a small service, a .dockerignore that keeps environment files out of the build context, and a compose file that brings the service and its database up with one command. Includes the layer ordering rationale and the measured difference the signal handling makes to a stop.
• Deployment runbook with rollbackThe document someone else could follow at 2am, and the deploy script it calls: preconditions, the deploy command, how you verify it worked, the rollback path with its own verification, the point at which you stop and escalate, and a separate migration runbook for the releases where application rollback is not enough.
• Failed deploy incident timelineA timestamped timeline of a deploy that went wrong: what changed, when it was detected, what you did, what you told people, and the contributing factors written without blaming a person.
• Pipeline hardening checklistA reviewable checklist covering secret handling, credential scope, dependency and image provenance, branch protection and artifact integrity, with the current state of one real pipeline scored against it.
• Flaky test decision recordThe decision on a test that fails one run in four, written so somebody can disagree with it on the evidence: the failure rate measured from the run history, what the test actually asserts and whether anything else covers it, each option with what it costs and what it hides, the decision, and the condition, owner and date that reverse it.