How did you design and implement deployment pipelines using Jenkins at Infosys?

The question aims to understand your experience and expertise with Jenkins, a popular Continuous Integration / Continuous Deployment (CI/CD) tool. Specifically, the interviewer wants to know how you've used Jenkins to design and implement deployment pipelines in your previous role at Infosys. When answering this question, it's important to:

1. Demonstrate your understanding of Jenkins and its role in CI/CD processes.
2. Detail your responsibilities and achievements when designing and implementing a deployment pipeline.
3. Mention any specific Jenkins functionalities you used and explain why they were chosen.
4. Explain the process and troubleshooting techniques used during the implementation phase.
5. If possible, discuss the results or improvements that occurred as a result of your work.

At Infosys, our project required frequent and reliable deployments to multiple environments, so a robust CI/CD pipeline was crucial. I designed the deployment pipelines using Jenkins as it offers great flexibility and compatibility.

Firstly, I divided the complete process into multiple stages - code fetch, build, testing, and deployment. I configured Jenkins to automatically fetch the latest code from our Git repository. The build process was scripted with Maven, and I set up Jenkins to build and compile the code. Post the build, I used the JUnit plugin to automate our unit tests.

For deployment, I used the Jenkins Pipeline plugin. It was chosen due to its support for complex pipelines and its compatibility with our tech stack. During the implementation, I faced issues like failing unit tests and slow pipeline execution. I frequently analyzed logs to understand and fix these issues.

As a result of the implementation, the coding-deployment cycle was significantly reduced, enhancing our productivity.

In my role at Infosys, I was responsible for automating our deployment process with Jenkins. Here's how I accomplished this:

The first step was to design the pipeline. I broke down the process into stages: code pull, build, test, and deployment. For each stage, I set up distinct Jenkins Jobs. Jenkins would automatically fetch changes from our GitHub repository on code commit. For building the application, I used the Gradle build tool and automated this in Jenkins.

Testing was another crucial stage. I leveraged the JUnit plugin in Jenkins to conduct unit tests and the SonarQube plugin for static code analysis. For deploying the built code, I incorporated Docker and Kubernetes into Jenkins to ensure our application ran in the same environment during all stages.

I routinely checked the job console for any errors and debugged them. This implementation resulted in higher deployment frequency and less time wasted on troubleshooting manual errors.