Here’re the 10 frequently asked Jenkin’s interview questions and answers.
- What is continuous delivery?
Continuous Delivery (CD) is the practice of delivering quality software more frequently. CD practices can include more or less the following entities:
- A good branching strategy.
- A working Continuous Integration (CI) process.
- Distributed builds.
- Automated testing.
- Distributed or parallel testing.
- Automated and quick environment provisioning.
- Automated code promotion.
2. What’s the branching strategy?
All the development steps one can do in a branch. However multiple-branchning simplifies delivery. This is how jenkins works.
3. What is high-availability set-up?
It means availability of Hardware, Server and services without service interruption. It can be achieved by setting up Active and Passive nodes. When one node (active) fails, the passive node takes responsibility.
4. What is the purpose of Pacemaker?
The Pacemaker/Corosync should detect the node (Primary node) failure and automatically start the Jenkins Server along with the Floating IP on the secondary node.
5. What is Floating IP?
Floating IP is a public, static IP address for instances created only in a private subnet (that is, without a public network interface). Using floating IP, such an instance will be able to accept incoming connections from the Internet. Here’s more on Floating IP.
6. What is Continuous Integration?
Continuous Integration requires developers to publish each and every change (commit) to the Integration/ Master branch. All these changes (on the Integration/Master branch) are built, tested, and analyzed for quality, and only after this we know if a change is good or bad
7. What is pre-tested commits?
Pre-tested commits (Gated Check-in), on the other hand, ensures that not all, but only those changes that are good, should be allowed on the Integration/ Master branch. Pre-tested commits (Gated check-in) ensure that only good changes are published to the Integration/Master branch by performing a check (build, test, analyze) on them.
8. What are the top Tools for continuous delivery?
|ools Used||Purpose||Alternative Tools|
|Jenkins||Main orchestrator for the Continuous Delivery||Teamcity, Atlassian Bamboo, ThoughtWorks Go…(may or may not have the option of pipeline as a code)|
|Artifactory||The binary repository to store build artifacts||Sonatype Nexus…|
|SonarQube||To perform Static Code Analysis||Squale, Kalistick, MetrixWare, Cast…|
|Apache Jmeter||To perform performance testing||LoadRunner, Testing Anywhere…|
|Junit||To perform unit testing and Integration testing||The list is huge depending on the project code…|
|Maven||To build Java project||Ant, MSBuild (.net, c#, c++)…|
|GitHub||Version Control repository||Git, Bitbucket, SVN, Mercurial…|
|Docker||To provision on-demand Jenkins Slaves||Kubernetes, Amazon EC2…|
9. What is Pipeline as a code?
Tired of creating and configuring Pipelines for your continuous integration (CI) and continuous delivery (CD) solution? Pipeline as a Code is the answer. The concept of Pipeline as a Code using Jenkinsfile or pipeline script is one of the newly introduced features in Jenkins (2.0)
10. What is continupus integration?
One of the fundamental components of continuous delivery is continuous integration. And it’s important that you have a robust, working continuous integration model in place. Following are some of the parameters that define a robust CI.
- Codable CI pipelines.
- Reproducible build environments.
- A highly available CI master.