Jenkins Reviews

We use Jenkins in CI/CD pipelines. 

Jenkins integrates with multiple tools like Bitbucket and makes life easier. We don't have to write a lot of code since a lot of libraries are available. 

The product should provide more visualization as to how many pipelines are performing and how many builds are happening. It should also integrate with Kubernetes and OpenShift. 

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

I would rate the product a nine out of ten. 

Jenkins is pretty scalable and I would rate it an eight out of ten. My company has more than 100 users for it. We use the tool every day. 

We report to our infrastructure team about the plugin issues. 

We wrote our own custom scripts before Jenkins. 

The tool requires maintenance whenever upgrades are available. 

We use the tool's open-source version which is free. There is an enterprise version which is expensive but comes with better support. 

I would rate Jenkins a nine out of ten. 

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

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

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.

We have worked with this solution for around four years.

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

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

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

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.

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

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.

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

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.

We use Jenkins for deploying with GenX and work on the pipeline too. We engage in many activities using both Jenkins and GenX. 

I love Jenkins. I like that you work on anything, and you make anything. Jenkins is very important for my team. I am satisfied with the product.

Jenkins can be improved, but it's difficult for me to explain. The initial setup could be more straightforward. If you connect Jenkins with bookings and lockouts, it can be challenging.

I have been using Jenkins for three years.

Jenkins is a stable product.

Jenkins is a scalable solution. We have ten people using this product right now.

Technical support was very good.

On a scale from one to five, I would give technical support a five.

Positive

The initial setup depends on the project and related activities.

I have implemented this solution myself, and I have also used a consultant on other occasions.

Jenkins is not expensive and reasonably priced.

I would recommend Jenkins to potential users. You can use Jenkins with other products and make anything you like. 

On a scale from one to ten, I would give Jenkins a ten.

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 use Jenkins to build and deploy our software.

Jenkins is very easy to use. It has a lot of integrations.

I would like to see more integrations included in the next release.

I have been using Jenkins for two years.

Jenkins is a stable solution.

Currently, we have 100 users working with Jenkins. We haven't had the need to scale the solution. We are satisfied with what we have.

There hasn't been a need to contact technical support.

Prior to using Jenkins, we were using Maven. We decided to switch because of the cloud enablement and the continuous integration.

The initial setup of Jenkins is easy.

We used an outside provider to install Jenkins.

I would recommend Jenkins to anyone thinking of implementing it into their organization.

Overall, I would rate Jenkins a nine out of 10.

We use Jenkins for integrated reporting. We have different projects that require coaching, gate configuration, and clone effects. We build packages, deploy, and upload-pack eights. We start at software changes and follow the process through to final testing and eventually launching. 

Jenkins has excellent task planning features. 

We have a variety of examples in our organization.  We have security configurations that we would like to isolate across our platform. It is not always easy to control the permissions for each user. There are cases where I do not want everyone to have access to the technical aspect of a job or even that the job exists.

I have been using Jenkins now for ten years.

We have found Jenkins to be very stable.

I believe Jenkins is scalable. We have over two hundred users. We have plans to increase this number.

We have not used technical support. We just Google, from the internet. Most of the time we can solve it on our side.

The initial set-up is easy for a single-link system. For more complicated systems it is not easy. As a product, Jenkins has been in the top five for more than five years, so that is not a problem.  

We did an in-house implementation. We have an incremental process for deployment. We also have a complete patent for official patent deployment. We have two patents, one for development and one for official relief. We have an integration team that is responsible for these patents.

Jenkins has a free licensing program.

Jenkins is the most popular automation engine in the world. There are other options, but fewer users. There are some other choices in the market but Jenkins is definitely number one. I would rate Jenkins an eight out of ten.

We use Jenkins for management purposes.

The most valuable features of Jenkins are creating builds, and connecting them with Sonar for Sonar analysis. Additionally, we connect it with other vulnerability tools, such as WhiteSource which is useful.

Jenkins could improve the integration with other platforms.

I have been using Jenkins for approximately two years.

Jenkins is stable.

I have found Jenkins to be scalable.

We have different teams within our company using this solution with different types of setups. We have approximately 25 users using the solution.

I have not contacted the support from Jenkins.

The initial implementation of Jenkins is simple.

The installation of Jenkins is done by our team.

I would recommend this solution to others.

I rate Jenkins an eight out of ten.

The simplicity of Jenkins and the evolving ecosystem of Jenkins are most valuable. Today, you do not have to write a pipeline from scratch. The library functionality of Jenkins helps you to bring all those in ready-made, and you also get the best practices for them. That is a great feature of Jenkins, and that is why it is being used significantly.

Jenkins also helps you to be agnostic to cloud providers.

I would like to have an integrated dashboard on top of it and a better UX to look at. The dashboard could be better in terms of integration with other tools. We should be able to have a single pane of glass across all the tools that we use where Jenkins is the pipeline. This can be a very good upgrade to it.

I have been using this solution for about 10 years.

It is very stable.

It is highly scalable, and it can scale into different models.

In terms of its customers, I have worked with very big enterprises to small companies with about 100 people.

Jenkins is an open-source initiative. So, the support is more community-based. The community is great. I do not remember asking for help often because it is quite stable, but for any extensibility that can be built on it, the community is great. You can find lots of resources and helpful people.

It is definitely not complex. It might not be very easy for a newcomer, but it is in the easy to medium range to get started with.

As people are using it, they should come to the community and provide their input so that the community can grow better.

I would rate it an eight out of ten.