What CICD tools are you using in your project for continuous building and continuous deployment?

Question

Accepted Answer

A typical Java CI/CD toolchain combines a build automation tool, a CI/CD orchestrator, and a containerization platform to automatically build, test, and deploy code whenever changes are pushed.

Key Points:
• Jenkins (or a similar orchestrator like GitLab CI or GitHub Actions) triggers a pipeline on every push or pull request via a webhook from Git.
• Maven or Gradle compiles the code, runs unit tests, and packages the application into a JAR or WAR artifact.
• Docker builds a container image from that artifact so the exact same image runs in every environment.
• The pipeline pushes the image to a registry and then deploys it, often to Kubernetes, staging, or production depending on the branch.
• Fast feedback from automated tests early in the pipeline catches issues before they reach later, more expensive stages.

Example:
A push to main triggers Jenkins, which runs mvn clean verify, builds a Docker image tagged with the commit SHA, pushes it to a private registry, and then updates the Kubernetes deployment to roll out the new image.

Code Example:
```
pipeline {
    agent any
    stages {
        stage('Build') { steps { sh 'mvn clean verify' } }
        stage('Docker') { steps { sh 'docker build -t myapp:${GIT_COMMIT} .' } }
        stage('Deploy') { steps { sh 'kubectl set image deployment/myapp myapp=myapp:${GIT_COMMIT}' } }
    }
}
```

Interview Tip:
A concise interview answer is:

"We use Jenkins as the orchestrator, triggered by Git pushes, with Maven or Gradle handling the build and tests. Jenkins then builds a Docker image and deploys it, giving us a fully automated pipeline from commit to production."