Jenkins Reviews

We use Jenkins for management purposes.

The most valuable features of Jenkins are creating builds, and connecting them with Sonar for Sonar analysis. Additionally, we connect it with other vulnerability tools, such as WhiteSource which is useful.

Jenkins could improve the integration with other platforms.

I have been using Jenkins for approximately two years.

Jenkins is stable.

I have found Jenkins to be scalable.

We have different teams within our company using this solution with different types of setups. We have approximately 25 users using the solution.

I have not contacted the support from Jenkins.

The initial implementation of Jenkins is simple.

The installation of Jenkins is done by our team.

I would recommend this solution to others.

I rate Jenkins an eight 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 used it for building Java applications. It provides some excellent plug-ins like Repository connector plugin, Sonar Qube plug in and J-Unit plugin.

It provides a very user-friendly methodology to build applications. It can be very easily integrated with your repository containing the source code. It builds your applications in a user-friendly manner by just adding the repository URL.

One needs to be very careful with the POM file as it takes all the dependencies from the POM to build the application. I would not call it a drawback but a caution.

I've used it for 10 months.

Issues with deployment occur primarily because of incorrect run time dependencies. The stack trace of the console can be used to encounter such problems effectively

Occasional technical glitches after upgrades.

Easy to run multiple instances simultaneously.

8/10

7/10

We didn't have any solution in place previously.

Initial set-up needs caution in mentioning the dependencies i.e. both runtime and compile time.

We did it in-house.

I believe it's good value.

It can be used effectively with technical expertise.

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.

When have to execute continuous testing with schedules and after test, if we want to run additional validation and verification we use Jenkins. 

Jenkin can do additional validation of our test executions of the results and collects data points.

The most valuable features of Jenkins are its ease of use and good plugins available. You are able to connect to a lot of solutions.

Jenkins can improve by continuing to add additional plugins for all the new solutions that are coming out within the cloud sphere.

I have been using Jenkins for approximately two years.

The stability of Jenkins has been good in my usage.

Jenkins has been scalable.

I have not needed to contact the support.

I have previously used Bamboo, but it is a smaller solution than Jenkins.

The initial setup of Jenkins is straightforward. The process took a couple of minutes.

We are using the freeware version of Jenkins.

I recommend Jenkins to others.

I rate Jenkins a nine out of ten.

We used it for continuous integration and had its latest version in the previous organization. I am now using Azure DevOps.

It is open source, flexible, scalable, and easy to use. It is easy to maintain for the administrator. It is a continuous integration tool, and its enterprise version is quite mature.

It has good integrations and plug-ins. Azure DevOps can also be integrated with Jenkins.

Its schedule builds need improvement. It should have scheduling features in the platform rather than using external plug-ins.

I used this solution for around one and a half years.

It is scalable. We had five users of this solution.

We were using another solution from Automic.

It is easy and quick to install. It took us less than an hour.

I installed it. You just need a single resource for its deployment and maintenance.

There is no cost. It is open source.

I would recommend this solution. It is good for small companies but not for big companies. It has a good interface and was easy to customize. We were also using another plug-in to enhance the user interface.

I would rate Jenkins a seven out of ten.

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.

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.