AbhishekSingh11 - PeerSpot reviewer
Infrastructure Solutions Architect at a real estate/law firm with 10,001+ employees
Real User
Top 5Leaderboard
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.

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

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.
PeerSpot user
Mike Schinkel - PeerSpot reviewer
President at NewClarity Consulting LLC
Real User
Top 5Leaderboard
If you think it's going to save you money because it's open source, think again
Pros and Cons
  • "I like that you can find a wide range of plugins for Jenkins."
  • "Jenkins is an open-source solution, and people tend to stay on the same version for a long time. When you look for an answer on Google, you often find something that doesn't relate to your implementation. The plugins are both the aspect of Jenkins and also one of the worst because the plugins can have different versions, so it's hard to figure out how to solve the problems."

What is our primary use case?

We were developing software, which would get built after we committed to version control. Jenkins would pick it up, build the software, run tests on it, and upload it to JFrog if everything was okay.

How has it helped my organization?

Jenkins automated the build and test portion of the CI/CD pipeline. 

What is most valuable?

I like that you can find a wide range of plugins for Jenkins.

What needs improvement?

Jenkins is an open-source solution, and people tend to stay on the same version for a long time. When you look for an answer on Google, you often find something that doesn't relate to your implementation. The plugins are both the aspect of Jenkins and also one of the worst because the plugins can have different versions, so it's hard to figure out how to solve the problems.

For how long have I used the solution?

I used Jenkins for about six months when I worked at HPE. I was at HPE for a year.

What do I think about the stability of the solution?

I wouldn't call Jenkins rock solid. It certainly requires ongoing administration.

What do I think about the scalability of the solution?

Jenkins is scalable. HPE used Jenkins across the entire company, so it had a large number of users. 

How are customer service and support?

It's open source, so I guess there are some options for technical support, but I didn't have access to it.

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

I use CircleCI, which is a platform-as-a-service solution. Since I left HPE, I've used App Actions, and I would prefer either over Jenkins.

How was the initial setup?

I didn't set Jenkins up, but I believe it's pretty complex.

What other advice do I have?

I rate Jenkins two out of 10.  If you think it's going to save you money because it's open source, think again. Find an alternative, such as GitHub Actions or GitLab.

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 2024
Learn what your peers think about Jenkins. Get advice and tips from experienced pros sharing their opinions. Updated: March 2024.
765,386 professionals have used our research since 2012.
Sajadur Rahman - PeerSpot reviewer
Senior Software Engineer, Middleware Development at a financial services firm with 5,001-10,000 employees
Real User
Top 20
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?

I am using Jenkins for my automated deployments for one of my projects.

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.

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.
PeerSpot user
Akinwale Awoyele - PeerSpot reviewer
DevOps Consultant at Deloitte
Real User
Top 10
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.
PeerSpot user
RohanBhosle - PeerSpot reviewer
Facilities And Administration at LTI - Larsen & Toubro Infotech
Real User
Top 10
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.
PeerSpot user
Cloud Engineer at a retailer with 10,001+ employees
Real User
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.
PeerSpot user
Rajeshkumar Gone - PeerSpot reviewer
Senior Software Engineer at Aviso AI
Real User
Top 20
A good web development solution that lacks in mobile development functionality
Pros and Cons
  • "We really appreciate that this solution is plug and play. When coding in the version control system, this product completes the build process automatically."
  • "We would like to see the addition of mobile simulators support to this solution, as part of its open-source offering. We currently have to carry out manual testing for these platforms."

What is our primary use case?

We use this solution to build, test, and then deploy new software to the FTP server.

How has it helped my organization?

This solution has improved our organization with how much time it saves when coding.

What is most valuable?

We really appreciate that this solution is plug and play. When coding in the version control system, this product completes the build process automatically.

What needs improvement?

We would like to see the addition of mobile simulators support to this solution, as part of its open-source offering. We currently have to carry out manual testing for these platforms.

For how long have I used the solution?

We have worked with this solution for around four years.

What do I think about the stability of the solution?

We have found the stability of this solution to be good.

What do I think about the scalability of the solution?

Due to the lack of mobile simulators, we have not scaled this solution.

How are customer service and support?

We have not had to contact the technical support team; the official documentation provided has resolved any issues we came across.

How was the initial setup?

We found the initial setup of this solution to be okay. The setup isn't complicated, but there is some step by step documentation provided that will need to be read and followed during the process.

The deployment of the product took one or two days initially, and only took one person to action.

What about the implementation team?

We carried out implementation and deployment of this product using our in-house team.

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

This is an open-source solution for the basic features. However, if an organization wishes to include specific functionality, outside of the basic package, there are extra costs involved.

Which other solutions did I evaluate?

We previously trialed an AWS-based product. However, it was complex to use and conflicted with some of our existing software.

What other advice do I have?

We highly recommend this solution for web development. However, for mobile development, it may be better for organizations to consider other options.

I would rate this solution a five 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.
PeerSpot user
Software Engineer at a financial services firm with 10,001+ employees
Real User
Top 5Leaderboard
It's a scalable, open-source tool with multiple plugins that's easy to use and set up.
Pros and Cons
  • "We can schedule anything with Jenkins, which is useful for deployment or anything that requires scheduling. It also has multiple plugins we can use for Maven, JUnit, etc."
  • "Jenkins could have better cloud functionality. Currently, we are using the existing legacy model, but we are moving toward the cloud, so it would be great if they could improve in that area. In the future, I would like more cloud features and related training materials, like a video tutorial."

What is our primary use case?

We use Jenkins to trigger the URL and necessary files in a batch. Jenkins is integrated with Jira and Litmus. We'll put a URL into Jenkins and trigger it. We can schedule it to run overnight every day, week, month, etc. 

Multiple teams are using Jenkins, and it's integrated with multiple Jira plugins. I believe around 250 people using it.

What is most valuable?

We can schedule anything with Jenkins, which is useful for deployment or anything that requires scheduling. It also has multiple plugins we can use for Maven, JUnit, etc.

What needs improvement?

Jenkins could have better cloud functionality. Currently, we are using the existing legacy model, but we are moving toward the cloud, so it would be great if they could improve in that area. In the future, I would like more cloud features and related training materials, like a video tutorial. 

For how long have I used the solution?

I've been using Jenkins for one year, and I know about related automation tools like Selenium, Tosca, etc.

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

Jenkins' main advantage over other solutions is multiple plugins and ease of setup. Open-source and secured versions are also available, so maybe that's why there are multiple processes. Other deployment tools cost more, and the setup is messy. These are some reasons management decided to use Jenkins instead of other solutions.

How was the initial setup?

The Jenkins setup is easy because it's open-source, and we can get a community edition. We don't need to do anything. We only need to install it and it's ready to use. The total deployment time depends on how long you have to code. In my case, it generally takes half an hour to one hour.

What other advice do I have?

I rate Jenkins eight out of 10. It's a scalable, open-source tool with multiple plugins. It's easy to use and set up. I don't rate it 10 because there is room for improvement in terms of the cloud and related capabilities. 

If somebody wants to use Jenkins, they need to first consider the scope. What is the scope, and what tech are you using? Jenkins is easy to set up, and we can integrate it with multiple technologies, whether a .NET application or anything else. We can deploy the code and can run with that. 

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