Jenkins Review

It's simple and intuitive but the plugins need to be streamlined

What is most valuable?

  • Extensibility
  • Usability

How has it helped my organization?

We've achieved continuous integration and delivery on all our commits, securing the quality of all of our products on their main branches. The features used come almost out of the box.

What needs improvement?

Many of the plugins needs to be streamlined, their terminology needs to be the same and some plugins should be split into multiple smaller plugins.

For how long have I used the solution?

Since 2010, so almost five years.

What was my experience with deployment of the solution?

No issues encountered.

What do I think about the stability of the solution?

Minor, but those issues typically gets fixed after reporting them. Some issues can be addressed as pull requests, fixing them myself.

What do I think about the scalability of the solution?

No, not after the lazy-load of items were introduced.

How are customer service and technical support?

Customer Service:


Technical Support:


Which solution did I use previously and why did I switch?

I used Hudson before, so the switch was quite natural.

What about the implementation team?

In-house implementation.

What's my experience with pricing, setup cost, and licensing?

My colleagues and I did the setup, so only the hours we spent doing it.

Which other solutions did I evaluate?

We also looked at Buildbot.

What other advice do I have?

Just go for it. It's simple and intuitive.

**Disclosure: I am a real user, and this review is based on my own experience and opinions.
More Jenkins reviews from users
...who work at a Computer Software Company
...who compared it with Bamboo
Find out what your peers are saying about Jenkins, Atlassian, JetBrains and others in Build Automation. Updated: December 2020.
454,950 professionals have used our research since 2012.
Add a Comment