Jenkins Overview
In this article, I will give an overview of Jenkins, the Workflow flow of Jenkins, and the advantages of using Jenkins. In the future, I will come up with a CI/CD project using Jenkins. First of let’s start with the definition of Jenkins.
→ Jenkins is an Open-Source project written in Java that runs on Windows, macOS, and other Unix Operating systems. It is free Community supported and might be your first-choice tool for CI.
→ Jenkins automates the entire software deployment life cycle.
→ Jenkins was originally developed by Sun Microsystem in 2004 under the name Hudson.
→ The project was later named Jenkins when oracle bought micro-system
→ IT can run on any major platform without any compatibility issues.
→ When developers write code, we integrate all that code of all developers at that point in time and we build test, and deliver/deploy to the client. This process is called CI/CD.
→ Jenkins helps us to achieve this
→ Because of CI, now bugs will be reported fast and get rectified foot. So, the entire software development happens fast.
Workflow of Jenkins
→ We can attach git, maven, selenium, and artifactory plugins to Jenkins.
→ Once developers put code in GitHub, Jenkins pulls that code and sends to maven for build.
→ Once the build is done, Jenkins pulls that code and sends it to selenium for testing.
→ Once testing is done, then Jenkins will pull that code and send it to artifactory (Archiving purposes) as per requirement and so on.
→ We can also deploy with Jenkins.
Advantage of Jenkins
→ It has lots of plugins available.
→ You can write your own plugin.
→ You can use a community plug-in.
→ Jenkins isn’t just a tool. It is a framework. i.e., You can do whatever you want. All you need is plug-ins.
→ We can attach slaves (nodes) to Jenkins master. It instructs others (slaves) to do jobs. If slaves are not available, Jenkins itself does the job.
→ Jenkins also behaves as a crone server replacement. i.e., can do scheduled tasks.
· It can create labels.
