CI/CD Automation Skill
Overview
Master CI/CD pipelines for automated software delivery.
Parameters
| Name | Type | Required | Default | Description |
|---|---|---|---|---|
| platform | string | No | github-actions | CI/CD platform |
| operation | string | Yes | - | Pipeline operation |
Core Topics
MANDATORY
- Git workflows (trunk-based, GitFlow)
- Pull request best practices
- GitHub Actions workflows
- GitLab CI pipelines
- Deployment strategies
OPTIONAL
- Jenkins pipelines
- ArgoCD GitOps
- Artifact management
- Security scanning
ADVANCED
- Multi-environment promotion
- Feature flags
- Chaos engineering integration
- Custom actions/runners
Quick Reference
# Git
git checkout -b feature/name
git add -p
git commit -m "type: description"
git rebase -i HEAD~3
git push -u origin feature/name
# GitHub CLI
gh pr create --title "feat: add X"
gh pr checkout 123
gh pr merge --squash
gh run list
gh run view 12345 --log
# Rollback
kubectl rollout undo deployment/app
kubectl rollout history deployment/appDeployment Strategies
| Strategy | Rollback | Use Case |
|---|---|---|
| Rolling | Slow | Low-risk |
| Blue-Green | Instant | Zero-downtime |
| Canary | Fast | High-risk |
Troubleshooting
Common Failures
| Symptom | Root Cause | Solution |
|---|---|---|
| Timeout | Slow build | Add caching |
| Test flaky | Unreliable test | Fix isolation |
| Secret missing | Not configured | Add in settings |
| Deploy failed | Auth issue | Check credentials |
Debug Checklist
- Check workflow syntax
- Review full logs
- Verify secrets set
- Test locally if possible
Recovery Procedures
Failed Deployment
- Rollback:
kubectl rollout undo - Identify issue in logs
- Fix and redeploy