I am using Jenkins for my automated deployments for one of my projects.
Senior Software Engineer, Middleware Development at a financial services firm with 5,001-10,000 employees
Provides the ability to write scripts, however it would benefit from improved customization
Pros and Cons
- "The most valuable features of Jenkins are the integration with GitHub, and the automation for deployment."
- "There are some difficulties when we need to execute the DB script."
What is our primary use case?
What is most valuable?
The most valuable features of Jenkins are the integration with GitHub and the automation for deployment.
Jenkins has a good user interface, and it is also able to write scripts.
What needs improvement?
There are some difficulties when we need to execute the DB script. I would like to see more simplified and improved customization in the next release of Jenkins.
For how long have I used the solution?
I have been using Jenkins for three months.
Buyer's Guide
Jenkins
October 2024
Learn what your peers think about Jenkins. Get advice and tips from experienced pros sharing their opinions. Updated: October 2024.
814,649 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?
Jenkins currently meets our needs in terms of scalability. We have 20 users split between two teams that are using the solution.
How are customer service and support?
We use the online documentation for support, it is sufficient and has everything we need.
Which solution did I use previously and why did I switch?
We also use Bamboo. Bamboo is more difficult to use than Jenkins. Jenkins is better with respect to networking.
How was the initial setup?
The initial setup of Jenkins is easy. However, it was easy because I was working with Java and Jenkins is Java-based.
Overall, I would rate the ease of the initial installation of the solution a four out of five.
What about the implementation team?
The implementation was done in-house.
What's my experience with pricing, setup cost, and licensing?
Jenkins is open-source, so it is free.
What other advice do I have?
Overall, 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.
DevOps Consultant at Deloitte
An unsatisfactory user interface and the documentation is not helpful
Pros and Cons
- "The solution is scalable and concurrent users have access to the platform."
- "The documentation is not helpful, as it is not user-friendly."
What is our primary use case?
We use this product as an open-source CI/CD. It allows integration, building pipelines, and even linking them to Azure or AWS platforms. It is an open-source tool. However, I wouldn't call it a public cloud. I would refer to it as an open-source tool for continuous integration and deployment. It can be integrated across every platform.
Our primary use case for this solution is creating pipelines for some projects we work on. Additionally, we use it to build pipelines and provide them with commands. For example, if we want to make a Docker image or send the deployments to Azure then we can integrate them into the Jenkins app service instead of Azure DevOps.
What needs improvement?
The user interface could definitely be improved, and I rate it close to zero. It isn't very good, and I am sure why it has not been worked on. The user interface could definitely be improved.
For how long have I used the solution?
We have been using this solution for approximately a year and a half and are currently using the latest version.
What do I think about the stability of the solution?
The solution is stable but it is slow. It is a free service so I can't complain about the time it takes.
What do I think about the scalability of the solution?
The solution is scalable and concurrent users have access to the platform. Currently, only a few people in our company are using this product.
How are customer service and support?
I have not contacted customer service and support.
How was the initial setup?
The initial setup was difficult. It is not easy to comprehend, and I recommend having a hands-on tutor or experience for you to be able to use it effectively. Additionally, the documentation is not helpful, as it is not user-friendly. I am unsure if this is because it is an open-source product, but it can definitely be improved.
It took approximately two hours to set up from scratch. In order to create the Docker image dependencies that need to be integrated need to be checked. The required keys also need to be identified because some SSH keys might be needed.
Which other solutions did I evaluate?
We chose this solution because it is in line with the budget and customer preferences.
What other advice do I have?
I rate this product a four out of ten. I would advise people using this product for the first time to review the provided documentation and watch some YouTube videos on the setup process while trying to understand the platform itself. The documentation is essential as it allows for a better explanation of some features and YouTube assists with troubleshooting. The product is affordable, but the user interface needs to be improved.
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Buyer's Guide
Jenkins
October 2024
Learn what your peers think about Jenkins. Get advice and tips from experienced pros sharing their opinions. Updated: October 2024.
814,649 professionals have used our research since 2012.
Cloud Engineer at a retailer with 10,001+ employees
Beneficial plugin integration, useful elastic management, and reliable
Pros and Cons
- "Jenkins can be used for elastic management, if you have any sensitive data or credentials you can use them across the environment. Additionally, the solution is easy to use and can be used across multiple use cases."
- "The solution could improve by having more advanced integrations."
What is our primary use case?
There are many use cases for Jenkins. We have an AWS infrastructure in which we have created templates for the provisioning of the infrastructure, and for the infrastructure network appliance, we use Jenkins.
For the builds, we use Docker images, Maven, Gradle, and other builds. We send all the build environments to the Artifactory Servers running Jenkins.
For any deployments to the systems, such as any standalone machines, Kubernetes cluster, or Auto Scaling groups, we use the Jenkins.
If a Kubernetes cluster is ready and you want to have other external configurations we use Jenkins for all of the configuration setups.
Jenkins can be used to check vulnerabilities of any system or Docker images.
What is most valuable?
The most valuable features I have found are it can integrate other services as a plugin. For example, if you want to integrate GitHub, or third-party tools, such as Prisma scan, you can have them as plugins and you start using them.
Jenkins can be used for elastic management, if you have any sensitive data or credentials you can use them across the environment. Additionally, the solution is easy to use and can be used across multiple use cases.
What needs improvement?
The solution could improve by having more advanced integrations.
For how long have I used the solution?
I have been using Jenkins for approximately four years.
What do I think about the stability of the solution?
The solution is stable. However, if you have any network interruption or any server failure it will not be stable.
What do I think about the scalability of the solution?
I have used the stand-alone Jenkins systems and I have other slaves configured with different systems or Docker containers and it has been operating well.
The scalable depends on the environment, if you want to have scalability it is possible. However, if there was a specific option to scale Jenkins systems it would be great.
We have approximately 250 users using this solution.
How are customer service and technical support?
I have not used the technical support from Jenkins but I have used the online forums which have been helpful in answering questions.
Which solution did I use previously and why did I switch?
I have previously used GitLab and Azure DevOps tools. I have found them both to be more complicated than Jenkins and this is why I switched. I am more familiar with Jenkins and this is another factor of why I use it.
How was the initial setup?
The installation is straightforward. All you have to do is update your repository and then install it. There are certain configurations needed after the installation, such as providing the secret key, accessing the server, managing the user access for separate groups, for example, development, performance, and QA groups all need different access levels assigned. It does not take more than 10 minutes.
What about the implementation team?
We did the implementation ourselves. Additionally, we can create scripts to do the configurations, this reduces the time needed for us to do them individually.
I am a DevOps engineer and we configure or automate deployments, schedule deployments, and then giving access to certain teams, such as the QA teams. They login in the morning and then if they want any new deployments, they can get it done.
There is a development team to a certain environment, such as test environments, where they can test their code. They have a particular job and can do the deployments by themselves.
What's my experience with pricing, setup cost, and licensing?
Jenkins is a free open-source server.
What other advice do I have?
I would recommend this solution to others.
I rate Jenkins a nine out of ten.
Which deployment model are you using for this solution?
Hybrid Cloud
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Senior site reliability engineer at Next think india
Time-saving automation with security benefits but needs improvement in job sequence reliability
Pros and Cons
- "Jenkins is particularly valuable since it saves time by automating manual tasks."
- "There are some issues with Jenkins, especially with the SIP job."
What is our primary use case?
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.
How has it helped my organization?
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.
What is most valuable?
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.
What needs improvement?
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.
For how long have I used the solution?
I have around eight years of experience working with Jenkins.
What do I think about the stability of the solution?
I would rate Jenkins' stability as seven out of ten. The software is quite reliable, but there is room for improvement.
What do I think about the scalability of the solution?
Jenkins is scalable; you can add multiple worker nodes to manage load effectively. I would rate its scalability as eight out of ten.
How are customer service and support?
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.
How would you rate customer service and support?
Neutral
Which solution did I use previously and why did I switch?
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.
How was the initial setup?
The initial setup of Jenkins is fairly easy, especially for someone with my background. It's a straightforward process.
What other advice do I have?
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.
Which deployment model are you using for this solution?
Hybrid Cloud
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Last updated: Oct 21, 2024
Flag as inappropriateSenior Quality Engineer, Cloud Platform Engineer at Belong
A free tool that has broad community support
Pros and Cons
- "The deployment of traditional Jenkins is easy."
- "Jenkins is an old product, and we encounter performance issues and slow response. Also, some of the plugins are not stable."
What needs improvement?
Jenkins is an old product, and we encounter performance issues and slow response. Also, some of the plugins are not stable.
For how long have I used the solution?
I have been working with the product for eight years.
What do I think about the stability of the solution?
I rate Jenkins' stability a six out of ten.
What do I think about the scalability of the solution?
I rate the product's scalability an eight out of ten. My company has 150 users for Jenkins.
How was the initial setup?
The deployment of traditional Jenkins is easy. I rate cloud-based deployment a five out of ten. It takes half and hour to complete.
What's my experience with pricing, setup cost, and licensing?
We use the tool's free version.
What other advice do I have?
Jenkins has broad community support. I rate it a nine out of ten.
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Senior Test Engineer at a outsourcing company with 201-500 employees
This is an open-source solution with a vast number of resources available online
Pros and Cons
- "The solution is scalable and has a large number of plugins that can help you scale it to your needs."
- "The solution's UI can use a facelift and the logs can use more detailed information."
What is our primary use case?
The solution is a continuous integration tool.
What is most valuable?
The most valuable features of the solution are the vast number of resources available online to all users and that it is open source.
What needs improvement?
The solution can be improved by introducing a handbook describing the variety of plugins that are available and what each one is used for. There are so many plugins if you don't have experience with them you can't create a properly working CI pipeline. The addition of automated plugins can improve the solution.
The solution's UI can use a facelift and the logs can use more detailed information.
For how long have I used the solution?
I have been using the solution for one and a half years.
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 and has a large number of plugins that can help you scale it to your needs.
How was the initial setup?
Aside from having to select the appropriate plugins the initial setup is straightforward.
What about the implementation team?
The implementation was done in-house.
What's my experience with pricing, setup cost, and licensing?
The solution is open source.
Which other solutions did I evaluate?
Before choosing the solution I evaluated TeamCity and GitHub Actions.
What other advice do I have?
I give the solution eight out of ten.
The solution has several advantages over its competition because it doesn't require a license, is easy to integrate, and there are a lot of free resources and information available online.
I recommend the solution and suggest to anyone thinking about using it to first familiarize yourself with the plugins and know what it is you want to get out of the product before installing it.
There are over 2000 people in our organization and over 80 percent of our project use this solution.
The solution has readily available documentation and support that can be found online.
Which deployment model are you using for this solution?
Public Cloud
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Other
Disclosure: I am a real user, and this review is based on my own experience and opinions.
DevOps engineer at Vvolve management consultants
Open-source tool for continuous deployment but requires enhanced UI
Pros and Cons
- "It offers continuous deployment and continuous testing. It enables us to figure out anything."
- "The user interface could be improved, and its reporting capabilities need enhancement. The plugins could be more effective."
What is our primary use case?
Jenkins is a tool for continuous integration and continuous deployment. It is open-source automation software that aids in deploying software, executing tasks, and creating pipelines. Jenkins is widely used to automate the building, testing, and deployment of applications through pipelines designed to streamline the development process.
What is most valuable?
It offers continuous deployment and continuous testing. It enables us to figure out anything.
What needs improvement?
The user interface could be improved, and its reporting capabilities need enhancement. The plugins could be more effective. Additionally, monitoring Jenkins can be somewhat challenging.
For how long have I used the solution?
I have been using Jenkins for three to four years.
What do I think about the stability of the solution?
The product is stable.
What do I think about the scalability of the solution?
The solution is scalable, but integrating it with other servers is a bit complicated. Seven people are using it.
How was the initial setup?
The initial setup is challenging. It is deployed within the target environment and acts as middleware.
What other advice do I have?
If we want to automate the IPP, the best approach is to start with Jenkins because it provides a solid foundation as an open-source automation tool. Once we have established our basic automation with Jenkins, we can consider migrating to cloud environments such as Azure or other cloud platforms for scalability and additional features.
If there are constraints, especially when starting with basic needs, Jenkins is the best open-source tool because it is free and works like other tools. However, with the rise of cloud technologies and powerful solutions, Jenkins remains a strong choice if our system is on-premises.
Overall, I rate the solution a six 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.
Last updated: Jun 26, 2024
Flag as inappropriateJava Software Engineer (Future Innovator) at Telenor Microfinance Bank (TMB)
A solution useful for interface upload and module deployment
Pros and Cons
- "I am not aware of the available options in the market right now compared to Jenkins, but I am pretty much happy with the service that Jenkins is providing our company."
- "Improvement-wise, I would want the solution's user interface to be changed for the better. In short, the solution can be made more user-friendly."
What is our primary use case?
For the deployment of modules, we use Jenkins in our company.
What is most valuable?
My core work does not involve the use of Jenkins. It is something we use in the deployment process. Basically, the solution is used for interface upload and module deployment.
What needs improvement?
Improvement-wise, I would want the solution's user interface to be changed for the better. In short, the solution can be made more user-friendly.
I feel that Jenkins should make a manual or provide instructions to those planning to use the solution. Our organization has people working in the DevOps team with around ten years of experience. So, people who are fresh graduates would not know how to operate Jenkins. There was an incident in the past in which the organization deleted the production pipeline, and this was because the instructions related to the solution weren’t clear. If the instructions had been provided and the solution had a normal user interface, such an issue could have been avoided altogether.
For how long have I used the solution?
I have used Jenkins for two and a half years. Though I am not very sure, I would say that I am using the solution's latest version. If you consider the technical side of the solution, then we are using in our company the same one being used by YouTube and Netflix.
What do I think about the stability of the solution?
Stability-wise, it's a pretty decent tool. Basically, It's an average product. So, I won't rate it the best or worst, as it's somewhere in the middle. If I was given to choose a better deployment service, I would definitely use that service rather than using Jenkins. I rate the solution's stability a six out of ten.
What do I think about the scalability of the solution?
I rate the solution's scalability somewhere between seven to eight out of ten. Approximately five to ten people in my company are using Jenkins. If we plan to get more modules in our company, we will have to increase the number of employees. Currently, we don't have any plans to increase the use of the solution.
Which solution did I use previously and why did I switch?
I am not aware of the available options in the market right now compared to Jenkins, but I am pretty much happy with the service that Jenkins is providing our company.
How was the initial setup?
We get involved in web testing, development, and PROD for the solution's deployment process. However, I am not aware of the core setup process for Jenkins. Also, we are not involved in the pipeline readiness process, as the DevOps team does it. Therefore, I am not aware of how the initial setup was done.
Around five to ten people from the DevOps team are required to deploy and maintain the solution. Also, the deployment model for the solution is a cloud-based one. It only takes approximately five to ten minutes to deploy the solution.
What's my experience with pricing, setup cost, and licensing?
In our company, we do pay for the licensing of the solution.
What other advice do I have?
I would definitely recommend the solution to those planning to use it in the future. Overall, I rate the solution an eight out of ten.
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: October 2024
Product Categories
Build AutomationPopular Comparisons
Microsoft Azure
GitLab
VMware Tanzu Platform
Tekton
AWS CodePipeline
Bamboo
Heroku
TeamCity
Harness
Chef
CircleCI
AWS CodeStar
GoCD
Bazel
Digital.ai Release
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)?