CI/CD and Release Engineering
The question for this group
How does a reviewed commit become a release I can verify and reverse?
Use GitHub Actions with AWS as the primary practice path.
Topics to explore
- Git collaboration: pull requests, branch protection, reviews, release tags, and traceability.
- Continuous integration: install, lint, tests, build, dependency scanning, artifacts, and cache correctness.
- Deployment identity: GitHub Actions OIDC, AWS roles, trust conditions, and environment permissions.
- Delivery pipelines: build once, artifact promotion, staging, production approvals, and concurrent deployments.
- Release strategies: rolling updates, blue-green, canary, feature flags, and database compatibility.
- Release verification: smoke tests, health checks, rollback triggers, previous artifacts, and pipeline diagnosis.
Practice target
Deploy the frontend from a reviewed commit using temporary AWS credentials. Promote a known artifact and rehearse rollback after a failed smoke test.