<img alt="" src="https://secure.leadforensics.com/150446.png " style="display:none;">

Jenkins: DevOps perspective

Vishal Dorage Nov 29, 2016

Software Development Open Source Jenkins


Jenkins is an open source cross-platform framework that allow to continuous integration and continues delivery of project. And integrating with a large number of testing and deployment technologies and it can handle any kind of build or continuous integration. Jenkins was originally developed as Hudson project.

Different plugins are available for Jenkins that can help to Jenkins to integrate with
Most of version control systems and big databases. Plugins can change the Jenkins
Looks and new functionality.

The reason you would want to do this is:

  • Decreases development cost and increase productivity
Because of using automation process so that time isn’t west for doing any task manually. And hence automatically Decreases development cost and increase productivity.

  • Developer time is focused on work
Much of work handled by automated build and testing system.so that developer time isn’t west for finding errors and doing any integration manually.

  • Quality of software is improved
Any error or issue are detected that are resolve immediately and keeping software in up to date stage whenever it can be released safely at any time.

  • Fast development process

Because of using continuous integration serious issue isn’t occur. And hence the process of developing application is fast.

How Jenkins works in software development phase

How Jenkins works in software development phase.png

Now with the help of above picture we get clear picture about how Jenkins works in software development phase.

Developer develops a program or a piece code on his local machine. He then stages his code and then push it to the centralized GIT/SVN repository.

As the GIT repository receives the commit from the developer, its post commit hook event is triggered. This is linked with the Jenkins build process which starts a new build using the latest code available in the code repository.Based on the output from the build of Jenkins, the notifications are sent out to the concerned audience. I.e. if the build fails, the responsible developer is notified via email or if the build succeeds, the build is forwarded ahead for its testing.

Different plugins are used by jenkins for continuous integration process:

Category of Jenkins plugins

  • Plugins for source code management
  • Plugins for build triggers
  • Build tools
  • Build notifiers
  • UI plugins

And much more plugins are available for Jenkins as per need.

Plugins for source code management:

With the help of source code management plugins, Jenkins get the source code for
Build triggering. Git are one of the most used plugin for source code management
With Jenkins.

Plugins for build triggers:

With the help of build trigger plugins Jenkins can trigger a build. Post commit hook available in Git is a one of the build trigger plugin.

Build tools:

With the help of build tools Jenkins can make a build. By pulling code from source
Code management system. Apache maven and apache ant are mostly used build
Tools with Jenkins.

Build notifiers:

With the help of build notifies we get notification about build via email or sms.

UI plugins:

With the help of UI plugins user get custom options to interact with Jenkins and
Jenkins build. Blue Ocean plugin one of the Jenkins UI plugin that gives user to
New experience for Jenkins.

e-Zest is a leading digital innovation partner for enterprises and technology companies that utilizes emerging technologies for creating engaging customers experiences. Being a customer-focused and technology-driven company, it always helps clients in crafting holistic business value for their software development efforts. It offers software development and consulting services for cloud computing, enterprise mobility, big data and analytics, user experience and digital commerce.