Jenkins Reviews

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.

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

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.

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

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

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

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

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.

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

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.

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

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.

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. 

I've used the solution for eight to ten years.

The stability is good. it's reliable. I'd rate the stability four out of five. 

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.

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.

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.

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.

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.

We are customers of Jenkins.

I'd rate the solution seven out of ten.

We use Jenkins for CI/CD application. It helps us develop and push out applications. 

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. 

I have used Jenkins for five or six years.

Jenkins is highly stable. 

Jenkins can scale up. We have about 100-150 users working with it now. 

The documentation is extensive and community support is excellent.

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. 

We deployed Jenkins in-house.

Jenkins is an open-source product, but you have the option to buy an enterprise license.

We usually just use Jenkins for the CI, continuous integration, part. That is the use case we have.

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.

It would be helpful if they had a bit more interactive UI.

I've been using Jenkins for a while. I've used it at this organization and in my past organization.

The solution is stable. We haven't had any real issues. There are no bugs or glitches. It doesn't crash or freeze. 

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.

I've never needed that assistance of technical support. I can't speak to how useful they are if you run into issues. 

The implementation process is pretty straightforward. It's not too complex. 

I can't recall exactly how long it took to deploy.

Licensing is not my domain. I can't speak to the exact costs. 

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.

The solution is a continuous integration tool.

The most valuable features of the solution are the vast number of resources available online to all users and that it is open source.

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.

I have been using the solution for one and a half years.

The solution is stable.

The solution is scalable and has a large number of plugins that can help you scale it to your needs.

Aside from having to select the appropriate plugins the initial setup is straightforward.

The implementation was done in-house.

The solution is open source.

Before choosing the solution I evaluated TeamCity and GitHub Actions.

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.

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

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

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

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

The solution is stable.

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

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

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

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

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

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

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

We are using Jenkins for running our test jobs, and multi-cluster deployments in the cloud.

The most valuable feature of Jenkins is its continuous deployment. We can deploy to multi-cluster and multi-regions in the cloud.

Jenkins could improve by allowing more scripting languages. We need to use Groovy scripting and it is difficult to debug and it is not ideal for creating file scripts. We tried to search for assistance but we did not find much help.

I have been working with Jenkins for approximately three years.

Jenkins is not always stable. We have encountered approximately 20 percent downtime.

The scalability of Jenkins could improve. If we are running a lot of jobs, it is not scaling up or down very well.

We have multiple jobs running and they can be between 50 to 100 at a time.

I have not used another solution prior to Jenkins.

The initial setup of Jenkins is a one-click deployment to multiple regions which is helpful. Additionally, it is easy to configure, and it is straightforward.

Jenkins is easy to maintain.

My advice to others is they should use Jenkins in the cloud. If they try to access the solution outside of the cloud environment, you need to configure whitelists and other configurations and keep an eye on them.

I rate Jenkins a seven out of ten.

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.

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.

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.

I've used the solution for more than ten years. 

The solution is stable. It's reliable. There are no bugs or glitches and it doesn't crash or freeze.

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.

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.

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.

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.

We handled the implementation ourselves, in-house. We didn't need any integrators or consultants.

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.

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.