Jenkins Tutorial for Beginners

In DevOps process, we had earlier certain challenges in the way developer code were integrated and tested.

Before Continuous Integration:

  • Complete source code build and testing was done
  • Developer had to wait a lot thru SDLC cycle for final test result
  • No feedback given after commit and after code is pulled to integration server

After continuous Integration

  • Every commit made in the source code is built and tested in the integration server
  • Developers is notified the test results of every commit made in the source code on the run
  • In case of any integration build failure due to bug in code, it is easy for developer to fix only that portion of code which was recently committed

In CI, developer has to make frequent commit and the code gets pulled by Continuous integration server and feedback given to developer

Jenkins is a continuous integration tool earlier known as Hudson. It is open source automation tool written in JAVA. It uses various plugins to integrate with various devops stages.

Jenkins can integrate with various other Devops tools such as:

  • Puppet [Configuration Management]
  • Maven, Ant, Teamcity, Bamboo [Build]
  • Nagios [Continuous Monitoring]
  • GIT, SVN [Version Control System]
  • Selenium [Continuous Automation Testing]
  • Ansible [Continuous Deployment]

Jenkins dashboard shows the status of all build jobs.

Various types of Jenkins Plugins are:

  • Test Analysis
  • Compile
  • Deployment
  • Notification
  • Monitoring
  • Reports and Performance Publishers
  • Dashboard View plugins
  • Global Build Status
  • Job Generator
  • Source Control Management