For the deployment of modules, we use Jenkins in our company.
Java 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?
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.
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?
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.
Senior Automation Engineer at a tech vendor with 10,001+ employees
Easy to learn, straightforward to set up, and has good documentation
Pros and Cons
- "It's very easy to learn."
- "We need more licensed product integrations."
What is our primary use case?
We primarily use the solution for CI, continuous integration, and as a content server.
What is most valuable?
The solution is quite scalable and user-friendly. It's very easy to learn.
The initial setup is straightforward.
It's stable.
The solution can scale.
It has good documentation to help with troubleshooting.
What needs improvement?
The solution needs more support for different Docker setups. Right now, it's a bit complicated. If there were better Docker integration, it would be ideal. Right now, there is no easy plug-in. You really have to explore it a bit more to figure out how to do it.
We need more licensed product integrations. For example, having a licensed integration with Jira would be great.
It is a bit limited in terms of its vision right now.
For how long have I used the solution?
I've been using the solution for three years.
What do I think about the stability of the solution?
The solution is stable. Sometimes the host server may be down. However, most of the time, it's stable.
I'd rate the stability nine out of ten.
What do I think about the scalability of the solution?
It's a pretty scalable solution. We find it easy to expand.
We're using it for a large application and haven't had any issues. It's a bit close sometimes; however, it doesn't crash at regular intervals. Sometimes there might be some server down or something that might cause an issue.
I'd rate the scalability nine out of ten.
We have about 300 or more people using the solution. We tend to use the product on a weekly basis.
How are customer service and support?
It is an open-source solution and has good documentation.
Which solution did I use previously and why did I switch?
I've also used Bamboo, which is a bit more user-friendly. It has good integrations and licensing.
How was the initial setup?
The solution offers a very straightforward setup. If you have a little bit of technical knowledge, it shouldn't give you any trouble. I'd rate the ease of setup nine out of ten.
What's my experience with pricing, setup cost, and licensing?
The solution is open-source.
What other advice do I have?
We're a partner.
Before using the solution, it is helpful to have some Git or CI/CD experience under your belt. It would help with context when starting to use Jenkins.
I'd rate the solution eight out of ten.
Which deployment model are you using for this solution?
Public Cloud
Disclosure: My company has a business relationship with this vendor other than being a customer: Partner
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.
Snr Tech Engineer at a transportation company with 10,001+ employees
Provides a single-pane-of-glass view, but error messages need improvement
Pros and Cons
- "When we have manual tasks, we have to depend on multiple technical teams. With Jenkins, we can bring all the technologies together by the click of a button. We can see results without having to depend on different teams. Jenkins makes life easy for the database and DevOps teams."
- "Tasks such as deployment, cloning, database switchover, and all other database missions and tasks are being done through Jenkins. If a job does not go through, at times the error message does not clearly indicate what caused the failure. I have to escalate it to the Jenkins DevOps team just to see what caused the failure. If the error message is clear, then I wouldn't have to escalate the issue to different teams."
What is our primary use case?
We use Jenkins for database products and automation of other applications as well.
What is most valuable?
When we have manual tasks, we have to depend on multiple technical teams. With Jenkins, we can bring all the technologies together by the click of a button. We can see results without having to depend on different teams. Jenkins makes life easy for the database and DevOps teams.
What needs improvement?
Tasks such as deployment, cloning, database switchover, and all other database missions and tasks are being done through Jenkins. If a job does not go through, at times the error message does not clearly indicate what caused the failure. I have to escalate it to the Jenkins DevOps team just to see what caused the failure. If the error message is clear, then I wouldn't have to escalate the issue to different teams.
For how long have I used the solution?
I've been working with Jenkins for two years.
What do I think about the stability of the solution?
On a scale from one to ten, I would rate Jenkin's stability at three.
What do I think about the scalability of the solution?
It is scalable because the Jenkins jobs are in AWS, whereas the deployments are being done on-premises. My understanding is that these will be brought on-premises as well.
We have 10 plus users for the database and application teams. We have less than 50 databases.
What other advice do I have?
If you want to have a single-pane-of-glass view in terms of automation, you can go for Jenkins. It does the job it's supposed to do. Therefore, I would give this solution a rating of seven out of ten.
Which deployment model are you using for this solution?
On-premises
Disclosure: My company has a business relationship with this vendor other than being a customer: Partner
Infrastructure Solutions Architect at a real estate/law firm with 10,001+ employees
Great performance, and easy setup, and good integration with other solutions
Pros and Cons
- "The initial setup is pretty simple."
- "It would be helpful if they had a bit more interactive UI."
What is our primary use case?
We usually just use Jenkins for the CI, continuous integration, part. That is the use case we have.
What is most valuable?
The performance is fine. With the huge chunk of connectors that it has, you can literally connect to anything, and you can add anything in the pipeline. The connector parts are seamlessly able to integrate into different products and systems. That is the best part.
The initial setup is pretty simple.
It's stable.
Whatever is commonly used and whatever I have required, I have always found that Jenkins has integration with those platforms. I'm fully satisfied on that front.
What needs improvement?
It would be helpful if they had a bit more interactive UI.
For how long have I used the solution?
I've been using Jenkins for a while. I've used it at this organization and in my past organization.
What do I think about the stability of the solution?
The solution is stable. We haven't had any real issues. There are no bugs or glitches. It doesn't crash or freeze.
What do I think about the scalability of the solution?
I can't comment on scalability as I have never really tried to scale it previously. It's not part of our requirements.
I'm not sure how many people in our organization actually use the solution.
How are customer service and support?
I've never needed that assistance of technical support. I can't speak to how useful they are if you run into issues.
How was the initial setup?
The implementation process is pretty straightforward. It's not too complex.
I can't recall exactly how long it took to deploy.
What's my experience with pricing, setup cost, and licensing?
Licensing is not my domain. I can't speak to the exact costs.
What other advice do I have?
Many teams use Jenkins here. Some may use it on the cloud, and others may use it on-premises.
I'm using the latest version of the solution.
I'd rate the solution nine out of ten. The reason we love it is the huge amount of connectors that Jenkins has. It has seamless connectivity with literally every product from Octopus, and you can integrate everything into your pipeline seamlessly. That was the reason we switched to Jenkins.
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 Coforge Growth Agency
An open source automation server with a useful business logs feature
Pros and Cons
- "I like the business logs. It's a very useful tool. Client-server communication is also very fast."
- "It would be better if there were an option to remove its Java dependency. This would make it more compatible with other software, and it could be much better. At present, we have to depend on Java whenever we want to deploy agents."
What is our primary use case?
We use Jenkins for the continuous integration of our jobs and products. We do have a couple of jobs that were created through Jenkins, and it's logical to start like that, as it requires the Java framework to run on Jenkins. We have the developer code; we begin with the power and the PSQL.
What is most valuable?
I like the business logs. It's a very useful tool. Client-server communication is also very fast.
What needs improvement?
It would be better if there were an option to remove its Java dependency. This would make it more compatible with other software, and it could be much better. At present, we have to depend on Java whenever we want to deploy agents.
For how long have I used the solution?
I have been using Jenkins for about two years.
What do I think about the stability of the solution?
Jenkins is a stable product.
What do I think about the scalability of the solution?
Jenkins is a scalable product.
How was the initial setup?
The initial setup is straightforward.
What other advice do I have?
I would tell potential users that Jenkins is a very good tool, which I highly recommend. It's very helpful for the continuous integration of any products. For example, if you want to dial up some things on production and want to go live, we can continuously integrate them. We can put it onto the report starting from the no-code and the subsequent environment and letters. So, Jenkins is very highly recommended.
On a scale from one to ten, I would give Jenkins a ten.
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?
Amazon Web Services (AWS)
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Senior Software Tester at SMARTe Inc
Efficient for Pipelines, easy to deploy and reliable solution
Pros and Cons
- "Jenkins is very user-friendly."
- "Performance-wise. This needs to be improved. Not only performance-wise, some functionality or some features can be added to Jenkins."
What is our primary use case?
We're using Jenkins for projects. We just need to run Jenkins pipelines and stuff.
We use iPlus for web application testing automation. Multiple people can work on the same piece of code. Once we push the code to the Git repositories, by default, we need to check if it's working and if the code passes the tests.
If any tests fail, we need to verify the logs in Jenkins. So, those are the main things we do with Jenkins.
What is most valuable?
Pipelines are the most valuable feature. We mostly work on pipelines; it's only because we have to verify the nightly build sign to see whether it is correctly done or not. So, for that kind of function, we usually work on the technical side.
What needs improvement?
Performance-wise. This needs to be improved. Not only performance-wise, some functionality or some features can be added to Jenkins.
Suppose we used to get a notification for part or field test cases. So that can also be improved on the technical side. We can get a notification through email or Slack channel or Teams channel. So that kind of notification also, they can also be improved on the technical side.
For how long have I used the solution?
I have been using Jenkins for six to eight months.
What do I think about the stability of the solution?
I would rate the stability a ten out of ten. I didn't face any crashes. It is hundred percent stable.
What do I think about the scalability of the solution?
I would rate the scalability a nine out of ten. We have multiple vendors, so we care. We are also one of the vendors for this project.
So in our project, we are using almost 20 to 25 members using Jenkins.
How was the initial setup?
I would rate my experience with the initial setup a nine out of ten, where one is difficult, and ten is easy.
Jenkins is very user-friendly.
The time taken for deployment depends on the performance of the engine. Sometimes, it may be slow. Usually, we won't face a performance issue. So, within a fraction of a second or within a fraction of a minute, the deployment can be done.
The deployment depends upon the code. If it is a small piece of code or it's a large piece of code. So it depends on the code.
What about the implementation team?
We have a separate DevOps team for maintenance and other tasks.
What's my experience with pricing, setup cost, and licensing?
This is not open source. It's price-based, for example, premium-based.
What other advice do I have?
Stability-wise, reliability-wise, and performance-wise, it is a good tool.
Overall, I would rate the solution 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 Operations Engineer at Wells Fargo
Excellent pipeline feature
Pros and Cons
- "Jenkins' most valuable feature is Pipeline."
- "Jenkins takes a long time to create archive files."
What is our primary use case?
I mainly use Jenkins to create automatic triggers for pushing code.
What is most valuable?
Jenkins' most valuable feature is Pipeline.
What needs improvement?
Jenkins takes a long time to create archive files.
What do I think about the stability of the solution?
Jenkins' stability is good, and we haven't had any issues with downtime.
What do I think about the scalability of the solution?
Jenkins is scalable in the sense that we can develop as many jobs as necessary.
How are customer service and support?
Jenkins' technical support team is small but helpful.
How would you rate customer service and support?
Positive
How was the initial setup?
The initial setup isn't very complex, though it may take some time to create end scripts because it lies in the backend and needs to work during free integration time.
What about the implementation team?
We used a uDeploy IBM product and team.
What other advice do I have?
I would rate Jenkins 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.
Facilities And Administration at LTI - Larsen & Toubro Infotech
Offers an open-source version, is very mature and integrates well with other solutions
Pros and Cons
- "Jenkins is a very mature product."
- "The enterprise version is less stable than the open-source version."
What is our primary use case?
Jenkins is basically used as a CI/CD tool, wherein you can integrate multiple tools that are part of your delivery pipeline. Jenkins is basically a controller for your delivery. For example, what happens, when it happens, and in what sequence it happens can be controlled by Jenkins.
What is most valuable?
Jenkins is a very mature product.
It has got a lot of support as far as integrating Jenkins with other tools is concerned.
There are a lot of plugins as well if you want to enable any feature or any automation as part of your delivery pipeline. There are a lot of plugins, actually, which are available both as part of an open-source as well as a commercial ecosystem.
It is easy to configure and easy to scale as well.
The initial setup is easy.
What needs improvement?
The enterprise version is less stable than the open-source version.
Security is one area that is lacking a bit. You need to have that extra work done when you are adopting Jenkins. There are some features here and there, however, if security overall can be improved, that would be really great.
For how long have I used the solution?
I've used the solution for more than ten years.
What do I think about the stability of the solution?
The solution is stable. It's reliable. There are no bugs or glitches and it doesn't crash or freeze.
What do I think about the scalability of the solution?
It is scalable. Jenkins can be implemented in a master play mode. You can have multiple masters and you can have multiple notes on which you can execute your jobs, which makes it very scalable.
We have about 500 people using Jenkins.
How are customer service and support?
We've never contacted external support. We've only dealt with internal support. Internal support is very well educated in terms of supporting Jenkins and other tools of concern. I'm very satisfied.
Which solution did I use previously and why did I switch?
Jenkins was the first product I used. Apart from Jenkins, there are other tools I've used, like Bamboo. Then, specific to the cloud, we have other DevOps services, and other pipelines. I have used multiple options. Still, I'm kind of a Jenkins fan. I definitely recommend Jenkins over other tools.
How was the initial setup?
The initial setup is very easy. It's not overly complex or difficult. You can enable a Jenkins pipeline, I would say, and a day, or less than a day.
We have about ten staff members that can handle deployment and maintenance. There are managers, developers, and DevOps teams, and then there are SYSops, admins, and DBAs. All these factors are there.
What about the implementation team?
We handled the implementation ourselves, in-house. We didn't need any integrators or consultants.
What's my experience with pricing, setup cost, and licensing?
One good thing about Jenkins is there are two flavors. One is open-source and the other is the commercial or the enterprise edition. The open-source version is pretty stable. For the security concern, you can add your own security-related intervention to make it that much more secure.
For the enterprise edition, you have a cloud-based which actually provides the commercial Jenkins version. Apart from security, they have come up with upgraded versions of Jenkins, for example, Jenkins Access Control and Jenkins Two-point Access Control. You can get added all kinds of features and the ease of implementing or managing your product. As I mentioned, Jenkins open-source is actually more stable and mature if you compare it to the enterprise version.
What other advice do I have?
The solution can be on-premises or in the cloud.
I'd recommend the solution to others.
I'd rate it ten 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: 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)?