Jenkins Review

Useful for us to collect and manage automatic processing pipelines

What is our primary use case?

Jenkins is part of our test infrastructure. We organize the test execution mainly of our performance tests, based on JMeter.

Second, the deployment of release candidates in our test infrastructure is managed using Jenkins.

In the future, we want to use Jenkins more in the field of continuous integration and continuous deployment.

How has it helped my organization?

For test automation, Jenkins seems to be our main and central solution at the moment. We want to extend this in the future towards Jenkins pipelines, which can be very useful for having a more dynamic test infrastructure.

What is most valuable?

Currently, using Jenkins for automatic testing is the most valuable feature for us.

It is very useful for us to be able to collect and manage automatic processing pipelines.

What needs improvement?

We have issues with the following points:

  • The usability and user interface could be improved.
  • Clearer feedback for problems and errors would be useful.
  • The learning curve is quite steep at the moment.
  • Our security policy does not allow normal users to introduce additional modules. A simpler way of extending the basic functionality would be nice.

For how long have I used the solution?

One year.

What do I think about the stability of the solution?

When there is enough disk space and RAM, the solution is stable.

What do I think about the scalability of the solution?

Scalability is not an issue for us.

How are customer service and technical support?

There is a large open source community where you can find a lot of workarounds and solutions when you have a problem.

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

We did not use another solution previously.

How was the initial setup?

The setup is straightforward.

What about the implementation team?

Our in-house SysOps team managed to install Jenkins.

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

Jenkins is open source and free.

Which other solutions did I evaluate?

We also evaluated Bamboo but decided to go with Jenkins because it is open source and free.

What other advice do I have?

We recommend having the proper infrastructure, and to ensure the maintenance of the server is performed.

**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: January 2021.
456,495 professionals have used our research since 2012.
Add a Comment