Jenkins Reviews

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.

I use Jenkins for Continous Integration or Continous Deployment to run test case execution in Nightly build atmosphere. Integrating test scripts to Jenkins is easier and it can run based on the frequency mentioned in settings.

Jenkins has helped us in executing our test scripts without the Dev team during night time.  It automatically fetches the latest build or codes and execute all your test scripts and share the report with the respective team and stakeholders.

I have found the following features extremely helpful.

• It is open source & user-friendly.
• It can deploy code instantly & generate test reports. The requirements for continuous integration and continuous deployment can be configured manually.
  
• Integration work is automated.
  
• It can be integrated with other major tools.

They should improve the Version Control tracking system in Jenkins.

We use it for build.

It improves our process because it's incorporated with the code. We don't need a UI to design the build process. It's like code for building.

Pipeline.

I think we have everything we need in Jenkins, really we're content with what we have in it. If I had to name something, I'd like to see more on the cloud, cloud integration, like to Amazon and  Google. I'd like to see more plugins for those.