Name: Jenkins
Brand: Jenkins
Rating: 4.0 (92 reviews)

it_user188790

QA Automation Lead at a tech company with 51-200 employees

Feb 2, 2015

Download

Provisioning VMs was an issue during deployment but automation in general has been improved.

What is most valuable?

I can build slaves and extensions through plugins.

How has it helped my organization?

Automation in general has been improved.

What needs improvement?

Provisioning of VMs during deployment.

For how long have I used the solution?

Five years.

Buyer's Guide

Jenkins

December 2025

Free Report: Jenkins Reviews and More

Learn what your peers think about Jenkins. Get advice and tips from experienced pros sharing their opinions. Updated: December 2025.

DOWNLOAD NOW

879,889 professionals have used our research since 2012.

What was my experience with deployment of the solution?

Provisioning VMs during deployment was an issue.

What do I think about the stability of the solution?

No issues encountered.

What do I think about the scalability of the solution?

No issues encountered.

How are customer service and support?

Customer Service:

Not needed.

Technical Support:

Not needed.

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

We previously used Hudson, and CruiseControl.

How was the initial setup?

Initial set-up was straightforward.

What about the implementation team?

We implemented in-house.

Which other solutions did I evaluate?

We compared Jenkins to CruiseControl.

What other advice do I have?

It works.

Disclosure: My company does not have a business relationship with this vendor other than being a customer.

it_user181050

Senior Software Automation Engineer with 501-1,000 employees

Jan 13, 2015

Download

Open source community with many plugins although stability for all but the most popular plugins needs to be improved.

What is most valuable?

Open source community with many plugins & flexibility as an automation platform.

How has it helped my organization?

Rather than send emails and tickets around we can hand out "buttons" to teams so they can do self-service for actions that used to involve manual effort from the Operations group.

What needs improvement?

Polish for the user interface, stability of plugins beyond the very most commonly used ones.

For how long have I used the solution?

Over seven years.

What was my experience with deployment of the solution?

No issues encountered.

What do I think about the stability of the solution?

No, although in some scenarios memory use can bloat over time.

What do I think about the scalability of the solution?

Not directly, but because of our overcomplicated networking setup we had to spread over multiple Jenkins masters each with a set of nodes.

How are customer service and technical support?

Customer Service:

Open source version, but have occasionally asked a quick question in the IRC channel and sometimes get a clue or two.

Technical Support:

Open source version, but have occasionally asked a quick question in the IRC channel and sometimes get a clue or two.

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

We started with Bamboo, but it wasn't flexible enough (at the time) to also be used for general automation (code deployments, application restarts, etc). Really we might have just expected too much of it.

How was the initial setup?

Easy. Drop in .war file, and restart the Tomcat server.

What about the implementation team?

In-house.

What was our ROI?

Hard to say. Although it was free, so infinite.

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

Free. Takes some work hours of course, but those come back many fold in improved productivity through automation.

Which other solutions did I evaluate?

No, we picked a long time ago before there were a lot of alternative options on the market. The few others available were expensive. Jenkins (well, Hudson at the time) was free!

What other advice do I have?

Do it! There's really no way you can lose. Even if you decide Jenkins isn't for you then you only spent work hours that helped train your staff and create reusable scripts that can be applied in other tools just as well.

Disclosure: My company does not have a business relationship with this vendor other than being a customer.

Buyer's Guide

Jenkins

December 2025

Free Report: Jenkins Reviews and More

Learn what your peers think about Jenkins. Get advice and tips from experienced pros sharing their opinions. Updated: December 2025.

DOWNLOAD NOW

879,889 professionals have used our research since 2012.

it_user7542

Director of Operations at a tech vendor with 51-200 employees

Jul 9, 2013

Strong community of developers and contributors

Jenkins is also open source, in very active development, and has a strong community of developers and contributors. Because Jenkins is a fork of Hudson, the interface is similar, and much of the core code remains the same (although Hudson 3.0 has some significant changes). Without going too far into the debate (you can read more about it from the Jenkins team and the Hudson team), it comes down to what your dev environment looks like. If you’re in an Oracle-heavy company, Hudson may work best for you. If you’re not, consider Jenkins. Jenkins seems to have more active dev going on right now. Both solutions are integrated with Eclipse and are heavily Java oriented (although not to the exclusion of other technologies).

Disclosure: My company does not have a business relationship with this vendor other than being a customer.

Don IngersonSr. QA Automation Engineer at a manufacturing company with 11-50 employees

Report as inappropriate

Jan 9, 2017

Alex,
I have heard good things about Jenkins. Can you please list a couple of sites that would help someone learn more about Jenkins from the ground level?

See all 2 comments

reviewer1864587

Java Developer at a financial services firm with 10,001+ employees

Jun 2, 2022

Download

Helps with continuous integration but onboarding could be smoother

Pros and Cons

"Jenkins is stable, user-friendly, and helps with continuous integration. As of today, I can't see any tool that's better than Jenkins."

"The onboarding of Jenkins should be smoother, and it should have more pipelines available as it's deployed on many different servers."

What is our primary use case?

I primarily use Jenkins to deploy APIs for microservices, creating pipelines and providing the source code link.

How has it helped my organization?

Jenkins helps to maintain continuous integration whenever we make changes in the code and to deploy the code whenever we do any check-ins.

What needs improvement?

The onboarding of Jenkins should be smoother, and it should have more pipelines available as it's deployed on many different servers. We should be able to do minimal configuration changes and deploy our API from multiple regions like AWS, GCP, or virtual environments like VM.

For how long have I used the solution?

I've been using Jenkins for six years.

What do I think about the stability of the solution?

Jenkins works perfectly well - we've never faced any outages or issues with it.

How was the initial setup?

The initial setup isn't difficult.

What about the implementation team?

We implemented using an in-house team.

What other advice do I have?

Jenkins is stable, user-friendly, and helps with continuous integration. As of today, I can't see any tool that's better than Jenkins. If you have very few APIs which can be deployed manually, I wouldn't recommend Jenkins. However, I would recommend it for those with multiple APIs and many clients, who are doing code changes on a daily basis. I would give Jenkins a rating of seven out of ten.