Jenkins Reviews

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

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.

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

Over seven years.

No issues encountered.

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

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

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

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

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.

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

In-house.

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

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

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!

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.

I primarily handle Jenkins in my organization for tasks such as enabling CI/CD and infrastructure deployment. We deploy applications and automate processes using the open-source Jenkins solution rather than CloudBees.

Jenkins has been a good fit for our processes. We have biweekly sprints with continuous integration and delivery, enabling us to automate many tasks. This improves efficiency and fits well into our requirements.

Jenkins is particularly valuable since it saves time by automating manual tasks. It also securely stores secret information, supports a wide range of integration plugins, maintains deployment history, and allows seamless user onboarding with LDAP connectivity. Additionally, the setup is straightforward.

There are some issues with Jenkins, especially with the SIP job. When you run the SIP job, it triggers child jobs in a sequence, yet often fails post-completion. These issues are open in Jenkins, and while there are fixes and it remains usable, improvements are needed in this area.

I have around eight years of experience working with Jenkins.

I would rate Jenkins' stability as seven out of ten. The software is quite reliable, but there is room for improvement.

Jenkins is scalable; you can add multiple worker nodes to manage load effectively. I would rate its scalability as eight out of ten.

For Jenkins, being an open source solution, there is no official technical support available. You can raise issues in GitHub, however, it's primarily supported by an open-source community.

Neutral

Before Jenkins, we used shared groups to deploy, which was mostly a manual operation involving automated scripts. Jenkins replaced this by automating processes, which enhanced efficiency.

The initial setup of Jenkins is fairly easy, especially for someone with my background. It's a straightforward process.

Based on my experience, I would recommend Jenkins since it greatly automates processes, securely stores sensitive information, supports multiple integrations, and maintains deployment history effectively.

I'd rate the solution seven out of ten.

Jenkins has good plugins and a secure platform.

I have to take the source code, build it, and test it with SonarQube. After passing it, I make the container, and with this container, we deploy to Kubernetes.

Even though you can get into the public cloud, they have to improve the base layer on marketplaces.  

I have been using Jenkins for the past three years.

Jenkins is as stable as the public cloud. 

You have to manually scale Jenkins.

The setup of Jenkins takes a lot of time. Having faster deployment would be helpful.

The time has come for companies to move to containers. I believe that Kubernetes services are based on the customer's needs in a secure manner. People will go with AWS or GCP.

I would rate Jenkins an eight on a scale of one to ten.

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

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

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.

I've been using Jenkins for six years.

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

The initial setup isn't difficult.

We implemented using an in-house team.

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.