Jenkins Review

​Potential deployment problems pop up almost instantly during the development process.

What is most valuable?

  • Scalability
  • Controllability
  • Organization of jobs

How has it helped my organization?

Potential deployment problems pop up almost instantly during the development process. The developers are more confident about their committed code.

What needs improvement?

They need more useful tutorials about how to write database related plugins. It also needs a "run only" option without option for changing job configuration.

For how long have I used the solution?

I've used it for six months.

What was my experience with deployment of the solution?

There were some issues with deployment.

What do I think about the stability of the solution?

There were some issues with stability.

What do I think about the scalability of the solution?

There were some issues with scalability.

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

No other solution was used previously.

How was the initial setup?

It wasn't complex.

What about the implementation team?

We did it in-house.

What was our ROI?

It's infinity as the developer's happiness are endless.

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

It's free.

Which other solutions did I evaluate?

We did not do a deep evaluation but we did look at Bamboo.

What other advice do I have?

Stay calm and mind the gap between your QA automation team and developers.

**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 CircleCI
Find out what your peers are saying about Jenkins, Atlassian, JetBrains and others in Build Automation. Updated: June 2021.
511,521 professionals have used our research since 2012.
Add a Comment
ITCS user