We are using the solution for integration purposes. We have our own DevOps pipeline. Jenkins is the key tool that is being used in the entire DevOps journey. It's like an automation build tool. It's a CI/CD: continuous integration and continuous deployment
DevOps Engineer at a financial services firm with 501-1,000 employees
Open-source and reliable but needs better documentation
Pros and Cons
- "It can scale easily."
- "They need to improve their documentation."
What is our primary use case?
What is most valuable?
We mostly enjoy the multi-branch pipeline support. We have multiple branches regarding, for example, the production environments. In this environment, we can use Jenkins for the deployment and integration of multiple branches.
The deploying and assessing of the development of our code and our application has been really useful.
It's getting a bit easier for us to use Jenkins, and it is really helping us.
The solution is stable.
It can scale easily.
Jenkins is pretty flexible and integrates with many products. As of now in the market, there is no vendor dependency. They are providing a lot of plugins, so it's not very difficult to integrate with others.
What needs improvement?
If they could provide some release management and integrated security like JFrog Xray and JFrog SonarQube, that would be ideal. If they could have a built-in security assessment, like a run times security assessment, or some engine within Jenkins, that would be great. We are expecting a collaborative solution. We'd prefer not to have to go through third parties. We want everything in a single place and without having to deal with extra applications and expenses.
I would want to see if they can add some security engines or security modules within the Jenkins portal so people wouldn't have to buy or go for some other outside products. As of now, security is the biggest concern. That should be the first priority after any technology.
They need to improve their documentation. When you compare it to Red Hat documentation which is very nice, you find that Jenkins does not provide much helpful documentation.
The product needs to showcase more use cases.
For how long have I used the solution?
I've used the solution for eight to ten years.
Buyer's Guide
Jenkins
November 2024
Learn what your peers think about Jenkins. Get advice and tips from experienced pros sharing their opinions. Updated: November 2024.
816,406 professionals have used our research since 2012.
What do I think about the stability of the solution?
The stability is good. it's reliable. I'd rate the stability four out of five.
What do I think about the scalability of the solution?
The solution can scale quite well.
We only have 20 to 30 users on the product right now. It's something our development team uses daily.
How are customer service and support?
The other people handle support cases. I'm not quite sure how quickly they respond since we have different infra teams, so they handle all these cases.
Which solution did I use previously and why did I switch?
The only competitor to Jenkins is Argo CD for Jenkins. We are not using it yet.
The approach is now changing to GitOps. People are moving towards the GitOps rather than the old DevOps model. That's where the Argo CD or Flex comes in as alternative tools that are picking up interest in the market.
How was the initial setup?
It would be easier to set up the solution if they offered better documentation. With more direction, it would be easier to deploy the solution. The steps shown in the documentation are not very clear.
It shouldn't be like a puzzle. I have to search everywhere, every time, and Google what I need. Rather than going to blogs and some open-source community blogs, it's better to have its own documentation. It should be very straightforward and clearly show the steps, the minimum requirements, and the bottlenecks. It should all be centralized as well.
I'd rate the setup process a three out of five in terms of ease of implementation.
What's my experience with pricing, setup cost, and licensing?
I'm not sure of the exact pricing of the product. My understanding is that it is not very expensive. It's an open-source tool. They do also have an enterprise version, which is what we use. It's the same tool whichever you use, however, with enterprise, you get support.
What other advice do I have?
We are customers of Jenkins.
I'd rate the solution seven out of ten.
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Senior Consultant and Trainer at Foreach Code Factory
Open source information server with multiple features including providing a comprehensive history of deployments
Pros and Cons
- "The most valuable aspect of this solution is that there are multiple features. We can abstract certain variables and then build our deployment routine while being able to do some abstraction onto the SSH connections."
- "This solution could be improved by removing the storage of unnecessary data such as the history of test deployments that were unsuccessful."
How has it helped my organization?
We use Jenkins to remove human error when completing multiple deployments.
What is most valuable?
The most valuable aspect of this solution is that there are multiple features. We can abstract certain variables and then build our deployment routine while being able to do some abstraction onto the SSH connections.
We can access a history of the different deployments so that we know whenever we have an issue. Problems are well documented so we can actually go back into your deployment history when necessary.
What needs improvement?
This solution could be improved by removing the storage of unnecessary data such as the history of test deployments that were unsuccessful.
In a future release, we would like to have access to more third party plugins and would like to integrate with tools like Kubernetes.
For how long have I used the solution?
We have been using this solution since 2014.
What do I think about the stability of the solution?
This is generally a stable solution. Sometimes we have experienced some issues but they have been minor.
Which solution did I use previously and why did I switch?
We have previously used an FTP server and we would copy and paste the files manually. I still prefer to use Bash scripts directly and deploy using SSH, or there are situations where we will not use an application because it would be overkill for such a simple deployment. We continue to use alternatives alongside Jenkins because sometimes it is pointless to build an entire Jenkins job just for deploying a website.
How was the initial setup?
There is a learning curve at the beginning. Jenkins could have setup wizards that could help you start off instead of having to rely on someone, reading a manual or completing an online tutorial.
What about the implementation team?
We've done everything in-house.
What's my experience with pricing, setup cost, and licensing?
We use the open source solution.
What other advice do I have?
There might be unnecessary overheads if you're trying to use Jenkins for very simple deployments. I would say make sure that you actually need to use Jenkins for specific actions.
I would rate this solution a ten 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.
Buyer's Guide
Jenkins
November 2024
Learn what your peers think about Jenkins. Get advice and tips from experienced pros sharing their opinions. Updated: November 2024.
816,406 professionals have used our research since 2012.
Principal DevOps Engineer at Guavus
There is a large user base to provide community support, which I find very valuable.
Pros and Cons
- "Jenkins is the most widely used development tool, so there are many plugins and it's easy to integrate. There is a large user base to provide community support, which I find very valuable. If I need to find a better way to do something, I can always get help from the community. Automation is about thinking outside of the box, and other users are constantly adding new plugins."
- "I would like them to provide space for people to have a central node that stores all the logs of workspace information in a distributed fashion to facilitate backup and restoration. Currently, everything is stored on one node, so you need to set up distributed storage or an endpoint that you can use for backing up your information."
What is our primary use case?
We use Jenkins for CI/CD application. It helps us develop and push out applications.
What is most valuable?
Jenkins is the most widely used development tool, so there are many plugins and it's easy to integrate. There is a large user base to provide community support, which I find very valuable. If I need to find a better way to do something, I can always get help from the community. Automation is about thinking outside of the box, and other users are constantly adding new plugins.
What needs improvement?
I would like them to provide space for people to have a central node that stores all the logs of workspace information in a distributed fashion to facilitate backup and restoration. Currently, everything is stored on one node, so you need to set up distributed storage or an endpoint that you can use for backing up your information.
For how long have I used the solution?
I have used Jenkins for five or six years.
What do I think about the stability of the solution?
Jenkins is highly stable.
What do I think about the scalability of the solution?
Jenkins can scale up. We have about 100-150 users working with it now.
How are customer service and support?
The documentation is extensive and community support is excellent.
How was the initial setup?
I rate Jenkins eight out of 10 for ease of setup. Jenkins evolved from running on a virtual machine to deploying inside Kubernetes, which has simplified the setup. Running Jenkins inside Kubernetes is straightforward. The only challenge is configuring the backup. We have two people maintaining Jenkins by updating the plugins and server about once every other month.
What about the implementation team?
We deployed Jenkins in-house.
What's my experience with pricing, setup cost, and licensing?
Jenkins is an open-source product, but you have the option to buy an enterprise license.
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.
Software Integration Engineer at Thales
Great price point, most popular automation in the world, with excellent task planning options.
Pros and Cons
- "Jenkins has excellent task planning features."
- "Partition security for the workflow of projects is not yet an option."
What is our primary use case?
We use Jenkins for integrated reporting. We have different projects that require coaching, gate configuration, and clone effects. We build packages, deploy, and upload-pack eights. We start at software changes and follow the process through to final testing and eventually launching.
What is most valuable?
Jenkins has excellent task planning features.
What needs improvement?
We have a variety of examples in our organization. We have security configurations that we would like to isolate across our platform. It is not always easy to control the permissions for each user. There are cases where I do not want everyone to have access to the technical aspect of a job or even that the job exists.
For how long have I used the solution?
I have been using Jenkins now for ten years.
What do I think about the stability of the solution?
We have found Jenkins to be very stable.
What do I think about the scalability of the solution?
I believe Jenkins is scalable. We have over two hundred users. We have plans to increase this number.
How are customer service and support?
We have not used technical support. We just Google, from the internet. Most of the time we can solve it on our side.
How was the initial setup?
The initial set-up is easy for a single-link system. For more complicated systems it is not easy. As a product, Jenkins has been in the top five for more than five years, so that is not a problem.
What about the implementation team?
We did an in-house implementation. We have an incremental process for deployment. We also have a complete patent for official patent deployment. We have two patents, one for development and one for official relief. We have an integration team that is responsible for these patents.
What's my experience with pricing, setup cost, and licensing?
Jenkins has a free licensing program.
What other advice do I have?
Jenkins is the most popular automation engine in the world. There are other options, but fewer users. There are some other choices in the market but Jenkins is definitely number one. I would 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.
Integrates with multiple tools like Bitbucket and makes life easier
Pros and Cons
- "Jenkins integrates with multiple tools like Bitbucket and makes life easier. We don't have to write a lot of code since a lot of libraries are available."
- "The product should provide more visualization as to how many pipelines are performing and how many builds are happening. It should also integrate with Kubernetes and OpenShift."
What is our primary use case?
We use Jenkins in CI/CD pipelines.
What is most valuable?
Jenkins integrates with multiple tools like Bitbucket and makes life easier. We don't have to write a lot of code since a lot of libraries are available.
What needs improvement?
The product should provide more visualization as to how many pipelines are performing and how many builds are happening. It should also integrate with Kubernetes and OpenShift.
For how long have I used the solution?
I have been working with the solution for one and a half years.
What do I think about the stability of the solution?
I would rate the product a nine out of ten.
What do I think about the scalability of the solution?
Jenkins is pretty scalable and I would rate it an eight out of ten. My company has more than 100 users for it. We use the tool every day.
How are customer service and support?
We report to our infrastructure team about the plugin issues.
Which solution did I use previously and why did I switch?
We wrote our own custom scripts before Jenkins.
How was the initial setup?
The tool requires maintenance whenever upgrades are available.
What's my experience with pricing, setup cost, and licensing?
We use the tool's open-source version which is free. There is an enterprise version which is expensive but comes with better support.
What other advice do I have?
I would 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.
Embedded Software Engineer at a manufacturing company with 201-500 employees
Flexible script customization, reliable, and scales well
Pros and Cons
- "The most valuable features of Jenkins are the integration of automatic scripts for testing and the user's ability to use any script."
- "Jenkins is not an easy solution to use and the configuration is not simple. They can improve the solution by adding a graphical interface that is more user-friendly."
What is our primary use case?
We are using Jenkins to automate the compilation and check the implementation from scripts for validation and testing. It's a useful tool for any developer.
If the code works fine in the company's development environment, it doesn't mean that it will be okay for other platforms. We're using Jenkins to test the server in platforms. It's very helpful.
How has it helped my organization?
Jenkins has improved our organization by allowing us to use automatic testing to cover all the various levels of software, which includes software embedded into hardware. It has been very difficult to be able to run tests in embedded software in the past.
What is most valuable?
The most valuable features of Jenkins are the integration of automatic scripts for testing and the user's ability to use any script.
What needs improvement?
Jenkins is not an easy solution to use and the configuration is not simple. They can improve the solution by adding a graphical interface that is more user-friendly.
For how long have I used the solution?
I have been using Jenkins for approximately one year.
What do I think about the stability of the solution?
The stability of Jenkins is good.
What do I think about the scalability of the solution?
Jenkins is scalable.
We have five people that are using this solution in my company.
How are customer service and support?
I have not used the support from Jenkins.
Which solution did I use previously and why did I switch?
I did not use a solution other than Jenkins.
How was the initial setup?
Jenkins is complex to implement.
What about the implementation team?
The implementation of the solution was done in-house. We use two or three people for the deployment.
What was our ROI?
The solution has had good value for the money we spent.
What other advice do I have?
My advice to others is this is a tool that will help save time have good coverage for the validation environment and test more hardware capabilities. For example, it can handle an embedded system and it can run any type of script.
I rate Jenkins a nine out of ten.
Which deployment model are you using for this solution?
Public Cloud
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Senior Director - Quality Engineering at mobileum
Easy to use and has a lot of integrations
Pros and Cons
- "Jenkins is very easy to use."
- "I would like to see even more integrations included in the next release."
What is our primary use case?
We use Jenkins to build and deploy our software.
What is most valuable?
Jenkins is very easy to use. It has a lot of integrations.
What needs improvement?
I would like to see more integrations included in the next release.
For how long have I used the solution?
I have been using Jenkins for two years.
What do I think about the stability of the solution?
Jenkins is a stable solution.
What do I think about the scalability of the solution?
Currently, we have 100 users working with Jenkins. We haven't had the need to scale the solution. We are satisfied with what we have.
How are customer service and support?
There hasn't been a need to contact technical support.
Which solution did I use previously and why did I switch?
Prior to using Jenkins, we were using Maven. We decided to switch because of the cloud enablement and the continuous integration.
How was the initial setup?
The initial setup of Jenkins is easy.
What about the implementation team?
We used an outside provider to install Jenkins.
What other advice do I have?
I would recommend Jenkins to anyone thinking of implementing it into their organization.
Overall, I would rate Jenkins a nine out of 10.
Which deployment model are you using for this solution?
Public Cloud
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Software Engineer at a financial services firm with 10,001+ employees
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.
Buyer's Guide
Download our free Jenkins Report and get advice and tips from experienced pros
sharing their opinions.
Updated: November 2024
Product Categories
Build AutomationPopular Comparisons
GitLab
VMware Tanzu Platform
Tekton
AWS CodePipeline
Bamboo
TeamCity
Harness
Chef
CircleCI
AWS CodeStar
GoCD
Bazel
Digital.ai Release
AWS CodeBuild
Travis CI
Buyer's Guide
Download our free Jenkins Report and get advice and tips from experienced pros
sharing their opinions.
Quick Links
Learn More: Questions:
- What are the differences among Jenkins, Urbancode build and ElectricAccelerator?
- How does Tekton compare with Jenkins?
- What are the differences among Jenkins, Urbancode build and ElectricAccelerator?
- Should project automation software be integrated with cloud-based tools?
- When evaluating Build Automation, what aspect do you think is the most important to look for?
- Is there a need for workflow automation?
- What is the Robotic Process Automation (RPA) life cycle?
- What is Automation as a Service (AaaS)?