Jenkins Reviews

We use Jenkins to remove human error when completing multiple deployments. 

The most valuable aspect of this solution is that there are multiple features. We can abstract certain variables and then build our deployment routine while being able to do some abstraction onto the SSH connections. 

We can access a history of the different deployments so that we know whenever we have an issue. Problems are well documented so we can actually go back into your deployment history when necessary.

This solution could be improved by removing the storage of unnecessary data such as the history of test deployments that were unsuccessful. 

In a future release, we would like to have access to more third party plugins and would like to integrate with tools like Kubernetes.

We have been using this solution since 2014. 

This is generally a stable solution. Sometimes we have experienced some issues but they have been minor. 

We have previously used an FTP server and we would copy and paste the files manually. I still prefer to use Bash scripts directly and deploy using SSH, or there are situations where we will not use an application because it would be overkill for such a simple deployment. We continue to use alternatives alongside Jenkins because sometimes it is pointless to build an entire Jenkins job just for deploying a website.

There is a learning curve at the beginning. Jenkins could have setup wizards that could help you start off instead of having to rely on someone, reading a manual or completing an online tutorial.

We've done everything in-house. 

We use the open source solution.

There might be unnecessary overheads if you're trying to use Jenkins for very simple deployments. I would say make sure that you actually need to use Jenkins for specific actions.

I would rate this solution a ten 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.

I mainly use Jenkins to create automatic triggers for pushing code.

Jenkins' most valuable feature is Pipeline.

Jenkins takes a long time to create archive files.

Jenkins' stability is good, and we haven't had any issues with downtime.

Jenkins is scalable in the sense that we can develop as many jobs as necessary. 

Jenkins' technical support team is small but helpful.

Positive

The initial setup isn't very complex, though it may take some time to create end scripts because it lies in the backend and needs to work during free integration time.

We used a uDeploy IBM product and team.

I would rate Jenkins eight out of ten.

We use this product as an open-source CI/CD. It allows integration, building pipelines, and even linking them to Azure or AWS platforms. It is an open-source tool. However, I wouldn't call it a public cloud. I would refer to it as an open-source tool for continuous integration and deployment. It can be integrated across every platform.

Our primary use case for this solution is creating pipelines for some projects we work on. Additionally, we use it to build pipelines and provide them with commands. For example, if we want to make a Docker image or send the deployments to Azure then we can integrate them into the Jenkins app service instead of Azure DevOps.

The user interface could definitely be improved, and I rate it close to zero. It isn't very good, and I am sure why it has not been worked on. The user interface could definitely be improved.

We have been using this solution for approximately a year and a half and are currently using the latest version.

The solution is stable but it is slow. It is a free service so I can't complain about the time it takes.

The solution is scalable and concurrent users have access to the platform. Currently, only a few people in our company are using this product.

I have not contacted customer service and  support.

The initial setup was difficult. It is not easy to comprehend, and I recommend having a hands-on tutor or experience for you to be able to use it effectively. Additionally, the documentation is not helpful, as it is not user-friendly. I am unsure if this is because it is an open-source product, but it can definitely be improved.

It took approximately two hours to set up from scratch. In order to create the Docker image dependencies that need to be integrated need to be checked. The required keys also need to be identified because some SSH keys might be needed.

We chose this solution because it is in line with the budget and customer preferences. 

I rate this product a four out of ten. I would advise people using this product for the first time to review the provided documentation and watch some YouTube videos on the setup process while trying to understand the platform itself. The documentation is essential as it allows for a better explanation of some features and YouTube assists with troubleshooting. The product is affordable, but the user interface needs to be improved.

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're deploying our pipeline through CI/CD with both engines, most use it for CI purposes only. We are building our CAR files and deploying them in the endpoint cluster, such as Kubernetes as well as on-premise systems. We are using the management where I can write playbooks and deploy them. I call the playbook through the Jenkins Groovy script. We can do multiple instances, at a single time. 

The most valuable feature of Jenkins is its open source.

The disadvantage of Jenkins is writing Groovy scripts. There are other CI tools where you do not need to write this many scripts to manage and deploy.

I have been using Jenkins for approximately three years.

Jenkins is stable.

The scalability is easy in Jenkins because we are using a master and worker node architecture.

We have many departments using this solution in my company, such as DevOps and Automation teams. 

The technical support was never used. We followed the standard documents. I never interacted with Jenkins technical because there is a wide user base online. Jenkins has been a long time in the market, we easily find help if needed. Similarly, how Python codes are molded and a lot of companies are using it. You can easily find a solution if you're stuck.

Jenkins is easy to set up. The full deployment can take some time if there is a lot of data to be accessed. There are the data analysis files, and queries, and we need to update everything in the end systems, such as a center DB. This can take some time, approximately half an hour due to the large file size. The majority of things can be deployed within five to seven minutes.

There is a cost saving by using Jenkins because instead, we do not have to depend on the public cloud or any private cloud CI tools.

We are using the free version of Jenkins. There are no costs or licensing.

I advise others that want to try Jenkins to first test it locally and then they can integrate it with the cloud. Whoever wants to use the continuous integration tools, should first go with Jenkins and then, later on, they can try other market available tools.

I rate Jenkins a nine out of ten.