Gitlab hero border pattern left svg Gitlab hero border pattern right svg

Jenkins Gaps

On this page

Not a Single DevOps Application


High Maintenance

Developer Experience

Jenkins quickly established itself as a leading build orchestration tool after its inception in 2005 and continued gaining steam before the term "DevOps" and "CI/CD" was all the craze like we hear about today. As the saying goes, "time stops for no one," and we're seeing more rapid advancements in technology and software development than ever before. Standards from 20 years ago seem foreign and what worked even 5 years ago is unlikely to still be considered best practice. We're all having to adapt quickly to stay relevant and compete in the current technological climate. Unfortunately for Jenkins, what worked so well 15 years ago hasn't stood the test of time and the lack of innovation to remain current and improve the project has taken a toll on its seemingly dwindling community of users and open source contributors, at least compared to how thriving the community once was. The two main Jenkins differentiators:

The above has turned into a double edged sword scenario where the plugin ecosystem has grown to a scale that's difficult to maintain and secure but still critical to making up for what Jenkins lacks in native capabilities. Jenkins itself is a java application with a severely outdated UI/UX, so problems of this nature are compounded for developers trying to use it efficiently and effectively – a constant uphill battle. Additionally, the once thriving community has seen a consistently significant decrease in activity and adoption.

While Jenkins is great for automating some things it is very brittle and is taking away from the developer experience. Specifically:

Increased Risk

Enterprise Readiness

Jenkins X

Kubernetes Support

Git is a trademark of Software Freedom Conservancy and our use of 'GitLab' is under license