#github-actions

Build robust CI/CD automation pipeline. Workflow: 1. Set up multi-stage builds (test, build, deploy). 2. Implement automated testing (unit, integration, e2e). 3. Add code quality checks (linting, security scanning). 4. Configure Docker image building and optimization. 5. Set up environment-specific deployments (dev, staging, prod). 6. Implement blue-green deployment strategy. 7. Add automated rollback on failure. 8. Configure Slack/email notifications. Include secrets management and deployment approval gates.

Build a production-grade CI/CD pipeline using GitHub Actions. Workflow: 1. Trigger on push to main and pull requests. 2. Run linting and unit tests in parallel. 3. Build Docker image with caching. 4. Run integration tests against test environment. 5. Deploy to staging on main branch merge. 6. Manual approval gate for production deployment. 7. Rollback mechanism on failure. Use secrets management, matrix builds for multiple Node versions, and status badges. Include deployment notifications to Slack.

Design a basic CI/CD pipeline using GitHub Actions for a Python web application. The pipeline should be triggered on a push to the main branch. It should include steps for installing dependencies, running linters, executing unit tests, and deploying the application to a staging environment.

Design robust CI/CD pipelines that automate software delivery with quality gates and rollback mechanisms. Pipeline stages: 1. Source control integration: GitHub/GitLab webhooks trigger builds on commits. 2. Build automation: compile code, dependency resolution, artifact generation. 3. Testing suite: unit tests (>80% coverage), integration tests, security scans. 4. Quality gates: SonarQube analysis, vulnerability scanning, performance benchmarks. 5. Deployment stages: dev → staging → production with approval workflows. Jenkins pipeline configuration: declarative Jenkinsfile with parallel stages, environment-specific variables, credential management. GitLab CI/CD: .gitlab-ci.yml with stages, artifacts, deployment environments, manual approvals. GitHub Actions: workflow triggers, matrix builds, environment secrets, deployment strategies. Quality metrics: build success rate (>95%), deployment frequency (daily for mature teams), lead time (<1 hour for hotfixes), mean time to recovery (<30 minutes). Rollback strategies: blue-green deployments, database migration rollbacks, feature flags for instant disabling. Security integration: SAST/DAST scanning, dependency vulnerability checks, secret detection, compliance verification.