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.

We use this solution for repeatable testing of code for regression and design conformance in a medical and scientific environment.

Jenkins has allowed for streamlined automated testing, building, and smoke testing of release candidates.

A lot of support material exists via a single web search of exactly what you're looking for.

I think an integrated help button, that respected the context of the change/work in hand, would be a worthwhile improvement.

I have been using this solution for four years.

The feature of this product that is most valuable to me is the robust community support plugins.

Jenkins has greatly improved the time it takes to deliver a software package to the market.

I can't think of any at the moment.

I have used Jenkins and Hudson for about four years.

No issues encountered.

No issues encountered.

No issues encountered.

The community of people who use this open source tool are very helpful.

No previous solution used.

Jenkins is very straightforward to install. Basically, it's a Java app that runs on an app server.

We implemented Jenkins in-house.

100% since it is open source.

No setup/;day to day costs.

Yes, we also looked at Hudson and Cruise Control.

Invest in time reading the support forums and newsgroups. Collaborate with other professionals.

We use this solution for Build & Deploy Automation. It is integrated with Git or TFS, Nexus and Ansible for deploying to premises servers in Linux or Windows.

This solution provides us more effective ALM and deployment automation compared to the previous solution with Serena (now Micro Focus) Dimensions CM.

The most valuable features are Jenkins Pipelines for ALM and full Deploy Cycle. This solution fully integrates with a lot of other solutions like Git, TFS, Nexus, SonarQube, etc.

I would like to have more Steps commands for better integration with other platforms.

Better and easy-to-use integration with Docker would be an improvement.

We use Jenkins to automatically build Python binaries into several OS's i.e. OS X, Ubuntu, Windows 32-bit and Windows 64-bit.

We are a company run by remote workers. Using Jenkins really helps us in moving our products forward into a number of different customer segments.

I think the UI and the UX can be improved. In our case, we have several products built using Jenkins. It is quite difficult to navigate into the latest stable build in a given OS.

Two years.

No stability issues.

No scalability issues. As long as the configuration is set correctly, there is nothing difficult in scaling up.

Jenkins is a free and open source application. So, StackOverflow is more than enough for us.

From the very beginning, we wanted to target OS X, Ubuntu and Windows users. At first, the developer would manually create some builds and put them in Gdrive to be tested. We started to use Jenkins when we had some multiple developers and testers and needed a system to manage and automatically build our products.

In my company, my role is a software tester. I don't know whether the setup is difficult or not.

We went directly to Jenkins.

Don't focus on the fact that Jenkins is open source. It is tough as a rock.

This software is ideal for you who work in software development especially those using Agile methodology.

Jenkins is used for triggering my test automation. I use Selenium WebDriver for test automation.

The most valuable features of Jenkins are the ease of use and the information about how to use the features is readily available on the internet. Additionally, with the solution, I can use other reporting tools, such as Flow.

Jenkins could improve by adding the ability to edit test automation and make time planning better because it is difficult. It should be easier to do.

I have been using Jenkins for three years.

Jenkins has been stable in my usage. However, I have had colleagues say they have had stability problems. They experienced these problems after six months to a year of use.

We have approximately four engineers using Jenkins and they use it as needed. It could be weekly or monthly.

There is not any support for the solution since it is open-source. However, you can find all the information needed online.

For triggering I use Jenkins, but for local systems, I used Selenium WebDriver. Additionally, I have used Cypress.

The initial setup of Jenkins is in the medium-difficult range.

Jenkins is a free solution, it is open source.

I rate Jenkins a seven out of ten.

We use it as a pipeline and for the whole development life-cycle. We even built the whole infrastructure and use it with cloud formation. In AWS, we use it with cloud formation when we build the infrastructure as a code.

It's fantastic. I like it, and I have no problem with it. It's very small, easy to use, and very straightforward.

It would help if they offered more integrations.

I have been using Jenkins for about two years.

It's very flexible, and you can add a lot of applications there to develop and more. We have about five guys using it, but we also have a very big development team with over 50 developers.

I installed it a couple of times, and the initial setup was easy. I didn't have any difficulties when it came to deployment.

I installed Jenkins by myself.

I would recommend this solution, but it depends on the project. It has a lot of support, and it's been in the market for a long time. Many big organizations also use it.

On a scale from one to ten, I would give Jenkins a nine.

We use a Hybrid cloud. We are deploying internally on our own servers i.e. our virtual servers in Microsoft Azure. We have 6 engineers using Jenkins Primer. It is only for internal use. We use it for the automation pipeline in our development of software. It compiles and moves the software to deployment in the Microsoft Azure cloud. We also use Jenkins to generate documentation for all the software.

The documentation could be more friendly, and more examples of how to use it. This would make for easier implementation in several environments.

Jenkins is very stable.

We read all the documentation. We also took online training on the internet, which included videos and training tasks. It takes some study and learning, but we don't experience any technical problems.

It took a few weeks for the initial installation of the Jenkins server to set up the development virtual pipeline.

The implementation was undertaken by developers and other internal staff.

I would rate Jenkins 9 out of 10.