Try our new research platform with insights from 80,000+ expert users
Staff Engineer - Product and Platform Engineering at Altimetrik (Deployed at FORD)
Real User
Great open-based framework, but the integration support and reporting could be better
Pros and Cons
  • "Jenkins's open-based framework is very valuable."
  • "It can be improved by including automated mobile reporting integrations."

What is our primary use case?

We use this solution in conjunction with Java which is installed. We have to give it the main part, our desk framework and the GI repository. The solution automatically takes the code from the GI repository and automatically executes it as a face task. It could be done at a set time for minutes, hours, and any day of the week. For example, if we want to get it right every day, it has to be set automatically to take the quote.

What is most valuable?

Jenkins's open-based framework is very valuable. Most of the time, we go open-based and use any test automation, not only for the automation framework but for the developers. They will trigger the jobs also using Jenkins with blue ocean, but there is a cost, and anything you need can be related to Java. For example, if you want to build your application and deploy it, Jenkins takes one day compared with CA or other circles, and in addition, the bamboo Jenkins is a popular solution.

What needs improvement?

The solutions integrations support and reporting could be improved. Currently, Jenkins provides the features automatically. However, if we can trigger the job from our mobile, that would be great. We have done it once, but the next time we tried, it did not work. For example, when I was in India, I tried to execute our Jenkins job but could not. However, when I put the privacy on my data and phone, I connected to the VPN, and it automatically triggered.

For how long have I used the solution?

We have been using this solution as users for over six years and are currently using version 2.23.1.

Buyer's Guide
Jenkins
March 2025
Learn what your peers think about Jenkins. Get advice and tips from experienced pros sharing their opinions. Updated: March 2025.
842,690 professionals have used our research since 2012.

What do I think about the stability of the solution?

The solution is stable.

What do I think about the scalability of the solution?

The solution is scalable. We can also add users for the particular solution, but that does not apply to the free version. We use the enterprise edition. Enterprise edition means it creates the domain for automation. Public members, can't access this edition, so if you're adding users for your members or groups, you have to go for the land visitation and the maintenance.

In my organization, over 50 users use this solution, specifically developers and QA leads. Not everyone has access to Jenkins because of the use of only one username and password. For example, if I'm developing scripts, my team members also develop them, and we push into the solution. But for Jenkins, it's only one access.

How are customer service and support?

We do not have any experience with customer service and support.

How was the initial setup?

 The initial setup is easy. If you follow the documentation, it only takes a maximum of 20 minutes.

Which other solutions did I evaluate?

We chose this solution because the deployment was right. We have to go further when it comes to the interface edition. Also, it's less when you are competitive with the travel CVA and the bamboo, and we will find the resources using Jenkins easily when it comes to the market level. So that's why we preferred Jenkins.

What other advice do I have?

I rate this solution a seven out of ten. My advice is to go for the proof of concept. Go with the open source and follow this solution because it works. If you get a paid version, you'll have a trial version for some days. If it suits your requirements, then you can purchase it. Otherwise, if you purchase it and it does not meet your needs, then it's a waste of money. See how you can model the integrations, the automation, and the frameworks and then go further into the interface solution.

The solution is good but it can be improved by including automated mobile reporting integrations.

Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
Senior Team Lead at Peristent Systems
Real User
Simple setup, high availability, and scalable
Pros and Cons
  • "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."

What is our primary use case?

We use Jenkins for management purposes.

What is most valuable?

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.

What needs improvement?

Jenkins could improve the integration with other platforms.

For how long have I used the solution?

I have been using Jenkins for approximately two years.

What do I think about the stability of the solution?

Jenkins is stable.

What do I think about the scalability of the solution?

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.

How are customer service and support?

I have not contacted the support from Jenkins.

How was the initial setup?

The initial implementation of Jenkins is simple.

What about the implementation team?

The installation of Jenkins is done by our team.

What other advice do I have?

I would recommend this solution to others.

I rate Jenkins an eight out of ten.

Which deployment model are you using for this solution?

On-premises
Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
Buyer's Guide
Jenkins
March 2025
Learn what your peers think about Jenkins. Get advice and tips from experienced pros sharing their opinions. Updated: March 2025.
842,690 professionals have used our research since 2012.
reviewer1727238 - PeerSpot reviewer
Software Engineer at a financial services firm with 10,001+ employees
Real User
Robust and secure tool for deployment
Pros and Cons
  • "Very easy to understand for newcomers."
  • "UI is quite outdated."

What is our primary use case?

My primary use case is as a CI pipeline in order to deploy onto the GCP. This allows us to push any changes into the master brand.

How has it helped my organization?

The major benefit of using Jenkins is that it's a very secure way of deploying something to the cloud. It has also improved the drawbacks of manual deployments by making them more robust and secure, and it helps the user avoid mistakes because all the checks are there in one script which can be used every time.

What is most valuable?

The most valuable feature of Jenkins is the logs it provides - these are very helpful in understanding error conditions so we can see where the problem lies and go in and check it. Another useful feature is the GUI, which estimates how long a particular model will need to be executed. It's also very easy to understand for newcomers. 

What needs improvement?

One area for improvement would be the UI, which currently looks quite outdated and requires the user to go through too many steps. In the next release, I would like to have the ability to use the command prompt to navigate between repositories and to enable features.

What do I think about the stability of the solution?

There are some minor bugs with this solution, but overall the stability is ok.

What do I think about the scalability of the solution?

Jenkins is very scalable.

How was the initial setup?

The initial deployment is easy if you are familiar with script creation - a person who is unfamiliar with this might have difficulties with setup. It can be set up by a single person in four to five hours.

What other advice do I have?

I would rate this solution as eight out of ten.

Which deployment model are you using for this solution?

On-premises
Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
PeerSpot user
Senior iOS Developer at a media company with 5,001-10,000 employees
Real User
​This is a very good, powerful and flexible product, but requires a lot of time investment to get the maximum out of it.

What is most valuable?

The Jenkins Job DSL plug-in is the most valuable.

How has it helped my organization?

We have been able to create CI jobs for each branch of our repository. Being able to test builds for each branch before it is merged to mainstream branch helped to improve stability of the app and have faster develop-test iterations.

What needs improvement?

The installation process could be simplified, especially on Mac OS X.

For how long have I used the solution?

I've used it for eight months.

What was my experience with deployment of the solution?

Yes because the installation process is not obvious.

What do I think about the stability of the solution?

The default settings do not work properly on Mac OS X. You have to tweak JVM parameters and allocate more heap memory as well as change other parameters to have a stable Jenkins server.

What do I think about the scalability of the solution?

I haven't had to scale up yet. We have one build box which is running two agents on it.

How are customer service and technical support?

Customer Service:

As this is open source, there is no such thing as customer service, but there is a big community to look for information and get answers.

Technical Support:

As this is open source, there is no such thing as tech support, but there is a big community to look for information and get answers.

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

Personally, I previously used Bamboo. I switched because I changed jobs and at my new place Jenkins had been used. It would unjustified to do a move from Jenkins to Bamboo, given that Jenkins is capable of performing same tasks.

How was the initial setup?

It was complex and additional knowledge about launch agents and daemons is required. There are at least three, if not four, different ways to install and configure Jenkins, which is not always good.

What about the implementation team?

We implemented it in-house.

What was our ROI?

It's high because the product is free.

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

The original setup. for us, was the cost of a new Mac Mini box which costs, from $1,000 to $2,000 depending on the configuration.

What other advice do I have?

This is a very good, powerful and flexible product, but requires a lot of time investment to get the maximum out of it.

Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
it_user217035 - PeerSpot reviewer
it_user217035Senior iOS Developer at a media company with 5,001-10,000 employees
Real User

mgrebenets.github.io
It's very subjective, just the way a blog post should be :)

See all 4 comments
Samim Kumar Patel - PeerSpot reviewer
Cloud Architect & Devops engineer at KdmConsulting
Real User
Stable, secure, with good plugins
Pros and Cons
  • "Jenkins has built good plugins and has a good security platform."
  • "Jenkins needs a faster deployment process."

What is our primary use case?

Jenkins has good plugins and a secure platform.

What is most valuable?

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.

What needs improvement?

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

For how long have I used the solution?

I have been using Jenkins for the past three years.

What do I think about the stability of the solution?

Jenkins is as stable as the public cloud. 

What do I think about the scalability of the solution?

You have to manually scale Jenkins.

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

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

What other advice do I have?

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.

Which deployment model are you using for this solution?

On-premises
Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
Sanjeeb Pandey - PeerSpot reviewer
DevOps Architect at a tech vendor with 10,001+ employees
Real User
Top 20
Plenty of plugins, lightweight installation, and effective third-part tool integration
Pros and Cons
  • "We are using the open-source version and there is a lot of plugins and features that are available and it works on agents for free. In other solutions, it will cost extra to use them with the agent."
  • "The UI of Jenkins could improve."

What is our primary use case?

We use Jenkins for building our applications, deploying our applications, and some automation tasks.

What is most valuable?

We are using the open-source version and there is a lot of plugins and features that are available and it works on agents for free. In other solutions, it will cost extra to use them with the agent.

What needs improvement?

The UI of Jenkins could improve.

For how long have I used the solution?

I have been using Jenkins for approximately six years.

What do I think about the stability of the solution?

Jenkins is stable. It provides all the required features for stability, such as backups.

What do I think about the scalability of the solution?

Jenkins is scalable because it is open source and it integrates with other third-party vendor tools which are currently in the market, such as Microsoft Azure or Amazon AWS. It gets very well integrated with all the new tools, it doesn't remain isolated.

We have multiple projects that are using this solution and each project has multiple users. In one project we could have 50 users or in another 10 users are using it.

How are customer service and support?

We didn't face any issues to escalate to Jenkins for technical help.

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

We have previously used Bamboo. I use both Jenkins and Bamboo per our project requirements. Jenkins is more suitable for commercial projects and is more scalable and flexible as compared to other tools because its core focus is on integrating and updating automatically.

How was the initial setup?

The initial setup of Jenkins was straightforward. It's very lightweight and it only requires Java on your system as a requirement.

What about the implementation team?

We did the implementation of the solution ourselves with our team.

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

We are using the free version of Jenkins. There is not a license required to use the solution because it is open-source.

What other advice do I have?

My advice to others is to explore Jenkins well and it is integrated with the scripting site. Teams should explore the scripting part of the Jenkins because everybody's nowadays is writing pipeline as a code for automating their operations. They should try to utilize the new feature provided to them, such as pipeline as a code. 

It does not matter what solution they are using, such as Microsoft Azure DevOps or Amazon AWS DevOps, Jenkins will integrate with other solutions. They should try and use Jenkins even if they're using some other tool.

I rate Jenkins an eight out of ten.

Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
reviewer1454061 - PeerSpot reviewer
Performance Test Line manager at a tech vendor with 10,001+ employees
Real User
Easy to use, effective plugins, and straightforward installation
Pros and Cons
  • "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."

What is our primary use case?

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.

What is most valuable?

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.

What needs improvement?

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

For how long have I used the solution?

I have been using Jenkins for approximately two years.

What do I think about the stability of the solution?

The stability of Jenkins has been good in my usage.

What do I think about the scalability of the solution?

Jenkins has been scalable.

How are customer service and support?

I have not needed to contact the support.

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

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

How was the initial setup?

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

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

We are using the freeware version of Jenkins.

What other advice do I have?

I recommend Jenkins to others.

I rate Jenkins a nine out of ten.

Which deployment model are you using for this solution?

On-premises
Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
Ismail Kiswani - PeerSpot reviewer
Manager at Al-kiswani
Real User
Top 20
Open source, flexible, scalable, and easy to use, but needs scheduling features
Pros and Cons
  • "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."

What is our primary use case?

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

What is most valuable?

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.

What needs improvement?

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

For how long have I used the solution?

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

What do I think about the scalability of the solution?

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

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

We were using another solution from Automic.

How was the initial setup?

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

What about the implementation team?

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

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

There is no cost. It is open source.

What other advice do I have?

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.

Which deployment model are you using for this solution?

On-premises
Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user