Jenkins Reviews

Jenkins is an old product, and we encounter performance issues and slow response. Also, some of the plugins are not stable. 

I have been working with the product for eight years. 

I rate Jenkins' stability a six out of ten. 

I rate the product's scalability an eight out of ten. My company has 150 users for Jenkins. 

The deployment of traditional Jenkins is easy. I rate cloud-based deployment a five out of ten. It takes half and hour to complete. 

We use the tool's free version. 

Jenkins has broad community support. I rate it a nine out of ten. 

As an administrator, I manage Jenkins. The development team uses it more frequently for automation and CI/CD.

Jenkins is a very good automation tool for building and deploying CI/CD. It is a good building tool and is the most popular tool for Java and microservices projects. Jenkins has a lot of built-in packages and tools.

The support for the latest Java Runtime Environment should be improved. We usually need support with Java Runtime Environment during the installation and administration of Jenkins.

Jenkins should add support for Java Runtime Environment.

We have been using Jenkins in our organization for the past five years.

Jenkins is a stable product.

The on-premise solution is used by seven people in our organization, including five people from the development team and two from infrastructure administration. So around seven people use Jenkins on-premise.

So far, I have never raised any support requests for Jenkins. I go through the Google online forum to solve the issues I usually face because it is an open-source deployment tool. However, I can rate it a six or seven out of ten.

Neutral

The setup is not that hard. If you are familiar with the Linux system and the Java Console, it is very easy to set up. It is easy to install and deploy.

Jenkins is an open-source tool.

Jenkins is Java-based. Our organization recently upgraded to Jenkins 2.390. We deploy Jenkins into VMware vCenter machines.

We use Amazon Web Services for pipeline automation on the cloud. I would recommend Jenkins to others. Jenkins is a popular CI/CD tool commonly used by DevOps teams. I rate Jenkins an eight out of ten.

For the deployment of modules, we use Jenkins in our company.

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.

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.

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.

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.

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.

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.

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.

In our company, we do pay for the licensing of the solution.

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.

We primarily use the solution for CI, continuous integration, and as a content server. 

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. 

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. 

I've been using the solution for three years. 

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.

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. 

It is an open-source solution and has good documentation. 

I've also used Bamboo, which is a bit more user-friendly. It has good integrations and licensing.

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. 

The solution is open-source. 

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.

We use Jenkins for database products and automation of other applications as well.

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.

I've been working with Jenkins for two years.

On a scale from one to ten, I would rate Jenkin's stability at three.

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.

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.

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

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.

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.

I have been using Jenkins for three months.

The solution is stable.

Jenkins currently meets our needs in terms of scalability. We have 20 users split between two teams that are using the solution.

We use the online documentation for support, it is sufficient and has everything we need.

We also use Bamboo. Bamboo is more difficult to use than Jenkins. Jenkins is better with respect to networking.

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.

The implementation was done in-house.

Jenkins is open-source, so it is free.

Overall, I would rate Jenkins a seven out of ten.

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.