#jenkins

Create a Jenkins declarative pipeline for Java application. Stages: 1. Checkout code from Git. 2. Build with Maven. 3. Run unit tests and code coverage (JaCoCo). 4. Static code analysis (SonarQube). 5. Build Docker image. 6. Push to container registry. 7. Deploy to Kubernetes. 8. Run smoke tests. Use parallel stages for efficiency. Implement pipeline as code (Jenkinsfile). Include credential management, artifact archiving, and email notifications on failure.

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.