Jenkins Reviews

Jenkins is a tool for continuous integration and continuous deployment. It is open-source automation software that aids in deploying software, executing tasks, and creating pipelines. Jenkins is widely used to automate the building, testing, and deployment of applications through pipelines designed to streamline the development process.

It offers continuous deployment and continuous testing. It enables us to figure out anything.

The user interface could be improved, and its reporting capabilities need enhancement. The plugins could be more effective. Additionally, monitoring Jenkins can be somewhat challenging.

I have been using Jenkins for three to four years.

The product is stable.

The solution is scalable, but integrating it with other servers is a bit complicated. Seven people are using it.

The initial setup is challenging. It is deployed within the target environment and acts as middleware.

If we want to automate the IPP, the best approach is to start with Jenkins because it provides a solid foundation as an open-source automation tool. Once we have established our basic automation with Jenkins, we can consider migrating to cloud environments such as Azure or other cloud platforms for scalability and additional features.

If there are constraints, especially when starting with basic needs, Jenkins is the best open-source tool because it is free and works like other tools. However, with the rise of cloud technologies and powerful solutions, Jenkins remains a strong choice if our system is on-premises.

Overall, I rate the solution a six 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.

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.

We are an automotive infotainment software provider. Our products are for infotainment. We have displays or music systems that are dealing with the Android operating system, and we are using Jenkins for some of the jobs.

We have two deployment models. One is on-premises, and the other one is the private cloud.

As an organization, we have multiple products and variants. For example, a customer or OEM has multiple car lines or brands. There is a common platform, and Jenkins is helping with the source code. From this common platform, each of the variants is taken for the build. We don't need to build and test. 

We get to see the results, and it is also useful to see the status in terms of success, failure, or any issue. We are able to get the status for a variant. It is connected to other dashboards such as Grafana, and we are able to see everything in one place. 

It has been helpful in monitoring the progress and understanding how the daily build is happening. It gives us confidence that the products that we have built are shippable. We are able to get the status of whether a product is shippable or has a problem. This is the advantage that we have from an organizational standpoint.

The auto-schedule feature is valuable. Another valuable feature is that Jenkins does not trigger a build when there is no change in any of the systems. Jenkins also supports most of the open-source plug-ins. 

There are a lot of things that they can try to improvise. They can reduce a lot of configurations. It is currently supporting Groovy for scripting. It would be really good if it can be improvised for Python because, for most of the automation, we have Python as a script. It would be good if can also support Python.

We have a lot of Android builds. These Android builds can be a part of Jenkins. It can have some plug-ins or configurations for Android builds. There should also be some internal matrix to check the performance. 

We also want to have more REST API support, which is currently not much in Jenkins. We are not able to get more information about running Jenkins. More REST API support should be provided.

I have been using this solution for almost six years.

It has been pretty stable. We haven't faced any issues. If you are running Jenkins in any lower hardware, or your machine or hardware is not that compatible, you might see some memory or Java issues. If you are running Jenkins in a good hardware environment, you don't see any problem. When you have the right hardware and proper memory, there is no problem.

Scalability is one of the challenging parts. Before the Docker area, we had a lot of challenges in terms of scaling because in one product, we had version 2.215, and in another product, we had a different version. If you want to migrate from one version to another or if you want to pull a different product, it took some time. It took two weeks time to set it up in a different environment. With the help of Kubernetes and Docker, we are able to spin off a couple of clusters with the Jenkins master. It is helping us a lot.

We have around 4,000 users for multiple Jenkins. We are a product-based company. Our products are built daily by using Jenkins. Out of 4,000, 60% of the users are using it for development and continuous release purposes. It is also used for nightly builds.

For support, we have only reached out to the open-source community. We find information on the web, and with trial and error, we are able to solve problems.

If you get any licensed product, you get support, but with open-source solutions, you don't get such support. So, we are fully dependent on the Jenkins community and people with some experience for fixing the issues.

It is straightforward. We have the software, and we create a Docker file. We use Jenkins as a master for our project, and we also build all plug-ins and create one Docker image. We give a single command to some administrative people to install the master.

In terms of deployment duration, we have an automated Docker setup, which hardly takes one day. The manual method would take a week.

There are a lot of frequent virtual updates from Jenkins. If there is a change, we put it into our Docker container, and then we will check and confirm it, which is a good part. If you are not going for Docker, there is a short maintenance period. For example, one version might support a plug-in, but another version might not support the same plug-in. In such a case, we have to deprecate the plug-in and go for another part.

We have 24/7 IT support at the global level. For any issues, we are able to take help. For master, we have one person dedicated not only to Jenkins but also to other deployments and technologies.

We tried CircleCI and Concourse, but we went ahead with Jenkins.

For a person who wants to get started with Jenkins, I would advise initially deploying Docker with Jenkins. You can also create a shared library in Jenkins. You should have some basic knowledge of the Groovy script.

I would rate Jenkins an eight 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.

I can install Jenkins for integration from multiple developers and automate application delivery, staging, and production environments.

Jenkins is very useful. I can install Jenkins for integration from multiple developers and automate application delivery, staging, and production environments. It's very easy.

I do not have any notes for improvement.

The scalability of Jenkins is good.

I never have had to contact their support team for any reason.

I also considered using CodeDeploy or Jenkins.

I would give Jenkins a rating of nine on a scale from one to ten.