Jenkins Reviews

We use it as a pipeline and for the whole development life-cycle. We even built the whole infrastructure and use it with cloud formation. In AWS, we use it with cloud formation when we build the infrastructure as a code.

It's fantastic. I like it, and I have no problem with it. It's very small, easy to use, and very straightforward.

It would help if they offered more integrations.

I have been using Jenkins for about two years.

It's very flexible, and you can add a lot of applications there to develop and more. We have about five guys using it, but we also have a very big development team with over 50 developers.

I installed it a couple of times, and the initial setup was easy. I didn't have any difficulties when it came to deployment.

I installed Jenkins by myself.

I would recommend this solution, but it depends on the project. It has a lot of support, and it's been in the market for a long time. Many big organizations also use it.

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

In this solution, you can write scripts and put job parameters in them with time and dates when to activate. We can create a web book that is automatically configured. The automated elements are easy to use and you can put them into your server. Additionally, there are plenty of plugins available. You can use the plugins to push your code into a target or container. There are many features available in this solution.

The scriptwriting process could be improved in this solution in the future.

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

The solution is stable.

We have not had any issues with scaling the solution.

I have previously used Bamboo and it is really easy to use, user-friendly, and the UI well designed. The control output of Bamboo is highly interactive for the user. 

I have also previously used Sonar but it is a lot different than this solution and Bamboo.

The solution is one of the lowest costs compared to competitors.

When selecting a solution I would advise checking their budget, the volume size they are performing, and what full-stack they are performing on. Based on this information, they can better determine what solution is best for them. If they have a low budget this solution would be great for them. 

I rate Jenkins an eight out of ten.

We use a Hybrid cloud. We are deploying internally on our own servers i.e. our virtual servers in Microsoft Azure. We have 6 engineers using Jenkins Primer. It is only for internal use. We use it for the automation pipeline in our development of software. It compiles and moves the software to deployment in the Microsoft Azure cloud. We also use Jenkins to generate documentation for all the software.

The documentation could be more friendly, and more examples of how to use it. This would make for easier implementation in several environments.

Jenkins is very stable.

We read all the documentation. We also took online training on the internet, which included videos and training tasks. It takes some study and learning, but we don't experience any technical problems.

It took a few weeks for the initial installation of the Jenkins server to set up the development virtual pipeline.

The implementation was undertaken by developers and other internal staff.

I would rate Jenkins 9 out of 10.

We used it for continuous integration and had its latest version in the previous organization. I am now using Azure DevOps.

It is open source, flexible, scalable, and easy to use. It is easy to maintain for the administrator. It is a continuous integration tool, and its enterprise version is quite mature.

It has good integrations and plug-ins. Azure DevOps can also be integrated with Jenkins.

Its schedule builds need improvement. It should have scheduling features in the platform rather than using external plug-ins.

I used this solution for around one and a half years.

It is scalable. We had five users of this solution.

We were using another solution from Automic.

It is easy and quick to install. It took us less than an hour.

I installed it. You just need a single resource for its deployment and maintenance.

There is no cost. It is open source.

I would recommend this solution. It is good for small companies but not for big companies. It has a good interface and was easy to customize. We were also using another plug-in to enhance the user interface.

I would rate Jenkins a seven out of ten.

We use this solution for repeatable testing of code for regression and design conformance in a medical and scientific environment.

Jenkins has allowed for streamlined automated testing, building, and smoke testing of release candidates.

A lot of support material exists via a single web search of exactly what you're looking for.

I think an integrated help button, that respected the context of the change/work in hand, would be a worthwhile improvement.

I have been using this solution for four years.

We use this solution for Build & Deploy Automation. It is integrated with Git or TFS, Nexus and Ansible for deploying to premises servers in Linux or Windows.

This solution provides us more effective ALM and deployment automation compared to the previous solution with Serena (now Micro Focus) Dimensions CM.

The most valuable features are Jenkins Pipelines for ALM and full Deploy Cycle. This solution fully integrates with a lot of other solutions like Git, TFS, Nexus, SonarQube, etc.

I would like to have more Steps commands for better integration with other platforms.

Better and easy-to-use integration with Docker would be an improvement.

We use this solution for continuous integration and deployment, using Groovy Script for pipeline node configuration.

This solution has helped us in automating the build and test process, reducing time.

The most valuable features are plugins that make my server highly available.

The upgrades need improvement.

Jenkins is part of our test infrastructure. We organize the test execution mainly of our performance tests, based on JMeter.

Second, the deployment of release candidates in our test infrastructure is managed using Jenkins.

In the future, we want to use Jenkins more in the field of continuous integration and continuous deployment.

For test automation, Jenkins seems to be our main and central solution at the moment. We want to extend this in the future towards Jenkins pipelines, which can be very useful for having a more dynamic test infrastructure.

Currently, using Jenkins for automatic testing is the most valuable feature for us.

It is very useful for us to be able to collect and manage automatic processing pipelines.

We have issues with the following points:

• The usability and user interface could be improved.
• Clearer feedback for problems and errors would be useful.
  
• The learning curve is quite steep at the moment.
• Our security policy does not allow normal users to introduce additional modules. A simpler way of extending the basic functionality would be nice.

When there is enough disk space and RAM, the solution is stable.

Scalability is not an issue for us.

There is a large open source community where you can find a lot of workarounds and solutions when you have a problem.

We did not use another solution previously.

The setup is straightforward.

Our in-house SysOps team managed to install Jenkins.

Jenkins is open source and free.

We also evaluated Bamboo but decided to go with Jenkins because it is open source and free.

We recommend having the proper infrastructure, and to ensure the maintenance of the server is performed.

This is our CD solution for Java APIs and Microsites.

This solution automates the deployment process and therefore increases productivity.

The most valuable feature is its ability to connect with different tools and technologies.

This solution would be improved with the inclusion of an Artifactory (Universal artifact repository manager).

This solution is the primary component for our automatic release process, including code smell, integration, and deployment.

This solution has provided us with better quality and less time to market for our software products. We can also automate many procedures like code review, testing, and deployment.

There are a large number of plugins available for integration with third party systems.

The user interface could be updated a little. I think that a REST API is needed to expand the integration capabilities.