cicd-pipeline-setup — an agent skill by aj-geddes

Design and implement CI/CD pipelines with GitHub Actions, GitLab CI, Jenkins, or CircleCI. Use for automated testing, building, and deployment workflows.

CI/CD Pipeline Setup Table of Contents [Overview]( overview) [When to Use]( when to use) [Quick Start]( quick start) [Reference Guides]( reference guides) [Best Practices]( best practices) Overview Build automated continuous integration and deployment pipelines that test code, build artifacts, run security checks, and deploy to multiple environments with minimal manual intervention. When to Use Automated code testing and quality checks Containerized application builds Multi environment deployments Release management and versioning Automated security scanning Performance testing integration Artifact management and registry Quick Start Minimal working example: Reference Guides Detailed implementations in the references/ directory: Guide Contents [GitHub Actions Workflow](references/github actions workflow.md) GitHub Actions Workflow [GitLab CI Pipeline](references/gitlab ci pipeline.md) GitLab CI Pipeline [Jenkins Pipeline](references/jenkins pipeline.md) Jenkins Pipeline [CI/CD Script](references/cicd script.md) CI/CD Script Best Practices ✅ DO Fail fast with early validation Run tests in parallel when possible Use caching for dependencies Implement proper secret management Gate production deployments with approval Monitor and alert on pipeline failures Use consistent environment configuration Implement infrastructure as code ❌ DON'T Store credentials in pipeline configuration Deploy without automated tests Skip security scanning Allow long running pipelines Mix staging and production pipelines Ignore test failures Deploy directly to main branch Skip health checks after deployment