Jenkins

What is Jenkins?

  1. Building projects
  2. Running tests to detect bugs
  3. Static code analysis
  4. Deployment

Jenkins Features:

  1. Adoption: Jenkins is widespread, with more than 147,000 active installations and over 1 million users around the world.
  2. Plugins: Jenkins is interconnected with well over 1,000 plugins that allow it to integrate with most of the development, testing, and deployment tools.

What is Continuous Integration?

Continuous Integration Example: Nokia

Continuous Integration With Jenkins

  1. Developers have to wait until the complete software is developed for the test results.
  2. There is a high possibility that the test results might show multiple bugs. It was tough for developers to locate those bugs because they have to check the entire source code of the application.
  3. It slows the software delivery process.
  4. Continuous feedback pertaining to things like coding or architectural issues, build failures, test status and file release uploads were missing due to which the quality of software can go down.
  5. The whole process was manual which increases the risk of frequent failure.
  • First, a developer commits the code to the source code repository. Meanwhile, the Jenkins server checks the repository at regular intervals for changes.
  • Soon after a commit occurs, the Jenkins server detects the changes that have occurred in the source code repository. Jenkins will pull those changes and will start preparing a new build.
  • If the build fails, then the concerned team will be notified.
  • If the build is successful, then Jenkins deploys the built-in test server.
  • After testing, Jenkins generates feedback and then notifies the developers about the build and test results.
  • It will continue to check the source code repository for changes made in the source code and the whole process keeps on repeating.

HP Case Study:

Problem

  1. Gary’s team consisted of around 400+ developers distributed across countries like the USA, Brazil, and India but only made two software releases per year! This is because LaserJet models had separate code bases which developed enumerable inefficiencies.
  2. Software bugs were detected via manual testing after 6 weeks of writing code. Fixing a bug that incurred within a code weeks ago, was labor-intensive and tiresome for the developers.
  3. This is where the team needed a new approach to remove the bottleneck

Solution

ETSY Case Study:

Problem

  1. Initially, Etsy struggled with the development of its organization because it adopted the monolithic architecture.
  2. Their deployment rate was about two times a week resulting in the isolation of departments. Etsy had to find a way out of this traditional system.

Solution

The Wrap-Up

--

--

--

I am tech enthusiast fascinated towards technology and its various disciplines including Big Data, Hadoop, Web Development, Competative Programming,ML,etc.

Love podcasts or audiobooks? Learn on the go with our new app.

Recommended from Medium

How To Build A Web App, part 7 of ?: connecting our Rails app to our database

The Spreadsheets of the Future

Git Commands i learnt this week

Hack The Box Cap Walkthrough

What is a delta migration?

What is DevOps and Why Should I Care?

PostgreSQL: Most useful commands for Full Stack developers (6–6)

Go Worker Pool for a layman

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store
Abhayagarwal

Abhayagarwal

I am tech enthusiast fascinated towards technology and its various disciplines including Big Data, Hadoop, Web Development, Competative Programming,ML,etc.

More from Medium

Jenkins:- Jenkins is an open-source automation tool written in Java with plugins built for…

Installing Jenkins on CentOS

Upgrade Jenkins Server