Jenkins Reviews

Jenkins is used for continuous automation of the various stages of the software development life cycle, such as building, testing, and deploying code chains. Jenkins supports continuous integration, allowing developers to integrate their code chain into a shared repository multiple times in a day.

Jenkins has a large number of plug-ins available for source code management, build tools, and testing. Jenkins integrates with various version control systems like Git and Bitbucket. Since it has a pipeline, Jenkins supports the creation of complex builds and deployment for a flow using the pipeline plugins.

Jenkins provides security features such as user authentication, authorization, and role-based access control. The solution integrates with external identity providers for authorization.

Jenkins optimizes the CI/CD process, enhances automation, and ensures efficiency and management of our build and deployment pipeline. It is easy for somebody to learn to use Jenkins.

Jenkins should adopt the Pipeline as Code approach by building a deployment pipeline using the Jenkins file. The solution should also include parallel build, artifact management, and automated matter testing.

I have been using Jenkins for one year.

Jenkins is a stable solution.

More than five people are using the solution in our organization.

The solution’s initial setup is easy.

Jenkins is an open-source platform.

Jenkins is deployed on the cloud in our organization. The solution is installed in our AWS server. The solution is widely used to build, develop, and automate projects. The solution facilitates continuous integration and continuous delivery by automating the building, testing, and deployment of code change.

We update Jenkins plug-ins, configure Jenkins with JVM, and always review and optimize our job configurations. You can consider using a cloud-based scaling solution to add or remove builds dynamically based on demand. Platforms like AWS EC2 and Kubernetes can be integrated with Jenkins.

Overall, I rate the solution ten out of ten.

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.

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 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.