JENKINS Interview Questions
JENKINS Interview Questions
Q. Mention what is Jenkins?
Jenkins is an open source tool with plugin built for continuous integration purpose. The principle functionality of Jenkins is to keep a track of version control system and to initiate and monitor a build system if changes occur. It monitors the whole process and provides reports and notifications to alert.
Q. Explain what is continuous integration?
In software development, when multiple developers or teams are working on different segments of same web application, we need to perform integration test by integrating all modules. In order to do that an automated process for each piece of code is performed on daily bases so that all your code get tested.
Q. What is the requirement for using Jenkins?
To use Jenkins you require
A source code repository which is accessible, for instance, a Git repository
A working build script, e.g., a Maven script, checked into the repository
Q. Mention what are the advantages of Jenkins?
Advantage of Jenkins include
At integration stage, build failures are cached
For each code commit changes an automatic build report notification generates
To notify developers about build report success or failure, it is integrated with LDAP mail server
Achieves continuous integration agile development and test driven development
With simple steps, maven release project is automated
Easy tracking of bugs at early stage in development environment than production
Q. Explain how you can move or copy Jenkins from one server to another?
Slide a job from one installation of Jenkins to another by copying the related job directory
Make a copy of an already existing job by making clone of a job directory by a different name
Renaming an existing job by renaming a directory.
Q. Mention what are the commands you can use to start Jenkins manually?
To start Jenkins manually, you can use either of the following
(Jenkins_url)/restart: Forces a restart without waiting for builds to complete
(Jenkin_url)/safeRestart: Allows all running builds to complete
Q. Mention some of the useful plugins in Jenkin?
Some of the important plugins in Jenkin includes
Maven 2 project
Q. Explain how you can deploy a custom build of a core plugin?
To deploy a custom field of a core plugin, you have to do following things
Copy the custom HPI to $Jenkins_Home/plugins
Delete the previously expanded plugin directory
Make an empty file called <plugin>.hpi.pinned
Q. Explain how can create a backup and copy files in Jenkins?
Jenkins saves all the setting, build artifacts and logs in its home directory, to create a back-up of your Jenkins setup, just copy this directory. You can also copy a job directory to clone or replicate a job or rename the directory.
Q. Explain how you can clone a Git repository via Jenkins?
To clone a Git repository via Jenkins, you have to enter the e-mail and user name for your Jenkins system. For that, you have to switch into your job directory and execute the “git config” command.
Q. Explain how you can set up Jenkins job?
To create a project that is handled via jobs in Jenkins. Select New item from the menu, once this done enter a name for the job and select free-style job. Then click OK to create new job in Jenkins. The next page enables you to configure your job.
Q. Mention what are the two components Jenkins is mainly integrated with?
Jenkin is mainly integrated with two components
Version Control system like GIT, SVN
And build tools like Apache Maven.
Q. What is Jenkins ?
It is a continuous integration tool written in Java.
Q. What is the difference between Maven, Ant and Jenkins ?
Maven and Ant are Build Technologies whereas Jenkins is a continuous integration tool.
Q. Which SCM tools Jenkins supports ?
AccuRev, CVS, Subversion, Git, Mercurial, Perforce, Clearcase and RTC
Q. What are the various ways in which build can be scheduled in Jenkins ?
Builds can be triggered by source code management commits.
Can be triggered after completion of other builds.
Can be scheduled to run at specified time ( crons )
Manual Build Requests
Q. What is the relation between hudson and Jenkins ?
Hudson was the earlier name and version of current Jenkins. After some issue , the project name was changed from Hudson to Jenkins.
Q. What you do to make sure that your project build doesn’t break in Jenkins ?
I make sure that I perform successful clean install on my local machine with all unit tests.
Then I make sure that I check in all code changes.
Then I do a Synchronize with repository to make sure that all required config and POM changes and any difference is checked into the repository.
Q. What you do when you see a broken build for your project in Jenkins ?
I will open the console output for the build and will try to see if any file changes were missed.
If not able to find the issue that way, Will clean and update my local workspace to replicate the problem on my local and will try to solve it.
Q. Tell us a bit about what your service and plugin do. Who is it for? What are the highlights of your plugin?
Loader.io is a simple-to-use cloud-based load testing service. The service is designed for developers and people who need to ensure applications are performing as they should. It allows developers to perform large-scale load tests on demand, which lets them understand the scalability and performance of their applications. We realize Jenkins is the preferred build service for a lot of our users, and we know providing a way for them to implement, measure and improve application performance during the continuous build cycle is important. So we wrote a Jenkins plugin that allows load testing to be brought into the continuous build and deployment process with ease.