In this post, I am going showcase my love for Jenkins.

I am aware a lot of developers/engineers out there are not a huge fan of this tool because of many known reasons and I can’t blame them at all. Jenkins sometimes can be a bit of a pain to get used to and takes time to get it right. If you get it wrong, it can cause a lot of havoc & stress in your development workflow.

However, I can’t express how much i adore Jenkins. My love for this tool is second to none and here’s why:

Jenkins is not just a CI server.

Jenkins (<2.0) used to be just merely a CI server at one point. It was basically a fork of the Hudson project. It was aimed to be much better than Hudson. But Jenkins 1 just caused problems after problems. As a CI server, I felt that it did its job. But what actually caused pain for most people was the vast library of plugins in their ecosystem. Some plugins were better than others while others were really poor & didn’t really integrate well within the Jenkins ecosystem which this caused a lot of problems for people. Stuff just weren’t mature back then for whatever reasons. Maybe open source was still in its infantry stage compared to what it is like today. Also, to correctly administer a Jenkins server or a cluster of Jenkins servers were a pain too. It was just too hard to get it right. Maintenance was tedious and wasn’t error free most of the times. In my opinion, the usage of Jenkins far outweigh the cons of Jenkins management and maintenance.

#jenkins #ci-cd-pipeline