Jenkins Reviews

<a href='https://www.trustradius.com/static/about-trustradius-scoring#question3' target='_blank' rel='nofollow noopener noreferrer'>Customer Verified: Read more.</a>
251 Ratings
<a href='https://www.trustradius.com/static/about-trustradius-scoring' target='_blank' rel='nofollow noopener noreferrer'>trScore algorithm: Learn more.</a>
Score 8.2 out of 100

Do you work for this company? Manage this listing

TrustRadius Top Rated for 2019

Overall Rating

Reviewer's Company Size

Last Updated

By Topic

Industry

Department

Experience

Job Type

Role

Filtered By:

Reviews (1-25 of 51)

Dodd Weisenberger profile photo
Score 8 out of 10
Vetted Review
Verified User
Review Source

Use Cases and Deployment Scope

We use Jenkins as our build management software, and it is mostly used between the development and QA teams. We use it both in manual and automated builds. It allows the developers to work together and send a combined solution to the QA team. It also controls our versioning with minor builds and patches.
Read Dodd Weisenberger's full review
Richard Rout profile photo
Score 2 out of 10
Vetted Review
Verified User
Review Source

Use Cases and Deployment Scope

We used Jenkins as our build server to execute build jobs and automated tests. The whole of engineering used it to build jobs and checking build status. Ensuring their branches would successfully run tests before merging to the master branch. It was a cheaper alternative to non-open-source competitors since it was free.
Read Richard Rout's full review
Erlon Sousa Pinheiro profile photo
Score 7 out of 10
Vetted Review
Verified User
Review Source

Use Cases and Deployment Scope

We're using Jenkins to perform part of our deployment pipeline. For our Development team, all the code tests are performed through Jenkins and on the DevOps side, all configuration management is performed by Jenkins integrated to Git, Puppet and Terraform. Also, their role on our day by day activities is quite important since we also use test routines on our configuration management pipeline and these tests are executed by Jenkins.
Read Erlon Sousa Pinheiro's full review
trang nguyen profile photo
Score 9 out of 10
Vetted Review
Verified User
Review Source

Use Cases and Deployment Scope

We use Jenkins as our main CICD server for multiple projects in our department and integrate Jenkins with our Gitlab source code repository and other tools such as SonarQube, Artifactory, Tomcat, Jboss, and Coverity. Our development team uses Jenkins jobs on every check-in code to run unit tests, scan code quality and run automation tests on every merge request before actually merging. Jenkins helps to increase our quality of product and eliminate most manual steps on deployment and integration.
Read trang nguyen's full review
No photo available
October 17, 2019

Jenkins CI/CD

Score 8 out of 10
Vetted Review
Verified User
Review Source

Use Cases and Deployment Scope

Jenkins is the main workhorse supporting our build and deploy pipeline and is used by both developers and dev-ops alike. Jenkins provides a sort of single source of truth by running tests and verification steps to ensure that code going out to production is functional and safe. It also allows our team of over 100 developers to safely deploy production changes many times per day.
Read this authenticated review
No photo available
Score 9 out of 10
Vetted Review
Verified User
Review Source

Use Cases and Deployment Scope

Jenkins is used across various teams in our organization. It is an integration tool where we use the CI/CD pipeline for continuous deployments of our microservices. This tool makes life easy to automate the process of deploying services into all environments ( staging, production, and development environments). It uses in all development life-cycle processes including build, document, test, package, stage, deploys, static analysis, and publishing.
Read this authenticated review
No photo available
October 16, 2019

Excellent CI/CD tool

Score 10 out of 10
Vetted Review
Verified User
Review Source

Use Cases and Deployment Scope

We are using Jenkins for our CI/CD solution. It is used across all the departments in our org. we use Jenkins for various purposes. We use it deploying applications to various environments and taking the backups of the servers and restore them. We integrated Jenkins with various tools across the whole organization.
Read this authenticated review
Dylan Cauwels profile photo
Score 9 out of 10
Vetted Review
Verified User
Review Source

Use Cases and Deployment Scope

We use Jenkins to automate our CD/CI jobs across a variety of applications. It is used by our QA teams to set up automatic testing for software deployments, and by our deployment team to deploy those applications in an automated fashion. This tool is crucial to any DevOps setup and will allow your teams to deploy as often as they would like with minimal effort or employee intervention.
Read Dylan Cauwels's full review
Hung Vu profile photo
Score 9 out of 10
Vetted Review
Verified User
Review Source

Use Cases and Deployment Scope

We use Jenkins as CICD server for our java application, We use both freestyle and pipeline project to have full lifecycle build from compile, unit test, code scan, build, deploy and run automation, performance test.
We use the freestyle and pipeline and they give us flexibility on what action we expect, we just compile and run unit test on every code checking, build a new snapshot artifact and deploy to test server then perform smoke automation test when merge to master, and run full automation test.
Read Hung Vu's full review
Mark Carpenter profile photo
Score 10 out of 10
Vetted Review
Verified User
Review Source

Use Cases and Deployment Scope

Jenkins is our standardized build tool for all our software teams. It has allowed us to move to a standardized continuous integration development cycle rather than the ad-hoc build and deploy structure that was used in the past. Having the ability to manage all our builds from a single web platform has been great for the management of our build process. We now have the ability to easily pull build logs and to determine where individual builds we're deployed. Jenkins has been highly beneficial for our company.
Read Mark Carpenter's full review
No photo available
Score 8 out of 10
Vetted Review
Verified User
Review Source

Use Cases and Deployment Scope

We use this technology throughout the company. Most of the time we integrate this with Git. Just by installing a Git plugin to the dashboard we are ready to rock and automate. We do the following process (this step by step guide will brief you more on our work): 1. Install and Integrate Git plugin with the dashboard of Jenkins (localhost:8080), 2. provide the URL/repository URL, 3. git pulls request so as to sync save all data to Jenkin workspace, 4. go to SCM, and select Git in freestyle project, 5. execute the operations and some batch commands, and 6. you are done! Now you are ready to automate your tests (Plugin wise) and debugging. We mostly use mailer application which triggers a mail to all the recipients when our production code builds successfully.



Read this authenticated review
Gabriel Samaroo profile photo
Score 10 out of 10
Vetted Review
Verified User
Review Source

Use Cases and Deployment Scope

The engineering team at several of my previous companies used Jenkins as a Continuous Integration and Automation tool. We used it for managing deployments of our applications across various environments, as well as a way to manually run various operations, such as running Tests or Invoking scripts. Jenkins has some good user permissions, that allow us to delegate specific responsibilities to various individuals without worry of someone doing something they shouldn't be allowed to. The setup is quite simple, and the software is very intuitive to use.
Read Gabriel Samaroo's full review
Ramendra Sahu profile photo
Score 7 out of 10
Vetted Review
Verified User
Review Source

Use Cases and Deployment Scope

This tool made the development flow fluid. Standout features are the continuous integration and a variety of support offered for creating packages for a number of technologies like, Java, C#, C++, etc and across multiple platforms that makes releases easier for faster roll out of business functionalities . It also has hundreds of plugins that can help you setup continuous integration and continuous delivery tool chain in quick time. You can easily scale out Jenkins across multiple machines, and support simultaneous large number of builds, tests and deployments across multiple platforms.
Read Ramendra Sahu's full review
Sagiv Frankel profile photo
Score 8 out of 10
Vetted Review
Verified User
Review Source

Use Cases and Deployment Scope

Jenkins is as our R&D build and deploy pipeline.
It allows us to:
1) Run end to end and unit tests every time we push new code.
2) Compile and bundle our code.
3) Deploy images and containers it to our Azure servers (Kubernetes).
4) Give us a nice dashboard to view that status of the tests, builds, and deployment.
Read Sagiv Frankel's full review
Kevin Van Heusen profile photo
Score 8 out of 10
Vetted Review
Verified User
Review Source

Use Cases and Deployment Scope

Jenkins is currently used to build and deploy our Amazon infrastructure. We practice the principles of infrastructure as code, meaning our infrastructure config and setup is checked into a revision control system and built via Chef and other scripts. Jenkins manages building that automatically or on demand and ensures that everything that is checked in is working properly.
Read Kevin Van Heusen's full review
Neale Foulds profile photo
April 02, 2018

Jenkins CI/CD

Score 10 out of 10
Vetted Review
Verified User
Review Source

Use Cases and Deployment Scope

We primarily use Jenkins as part of our build infrastructure for compile and build, typically executing mavens builds but also ant scripts for more complex tasks and workflows
Read Neale Foulds's full review
No photo available
Score 10 out of 10
Vetted Review
Verified User
Review Source

Use Cases and Deployment Scope

Jenkins is the tool we use for building our code, running our test cases and also for few of the inhouse datacenter deployments.

Apart from the regular CICD, we also use it for many of our other automation tasks, for example automating regular operational tasks like disk cleanup, log rotation etc.
Read this authenticated review
No photo available
Score 9 out of 10
Vetted Review
Verified User
Review Source

Use Cases and Deployment Scope

Jenkins is used across our entire organization. For our dev shop, it mains our build cycle by completing builds of code and handling deployment of code. In addition, we even utilize it to roll out database schema changes. If this wasn't enough, we also utilize Jenkins to generate content based off of markup. Jenkins has allowed us to meet the needs of our dev department of continuous integration while allowing customers to put out content in a timely manner.
Read this authenticated review
No photo available
Score 8 out of 10
Vetted Review
Verified User
Review Source

Use Cases and Deployment Scope

My organization has deployed Jenkins as the main continuous integration tool for their projects which is responsible for automating all the unit tests, integration tests, end-to-end tests and also the process of releasing the final products as configured.
Read this authenticated review
No photo available
Score 10 out of 10
Vetted Review
Verified User
Review Source

Use Cases and Deployment Scope

Currently Jenkins is being used across the IT team in our organization. It simply does the hard job of automating all the repetitive tasks, includes details in projects, inside builds, follows workflows, accesses operating systems, and alerts when it's done, or, based on decisions during tasks, what to do. This reduced a lot of work for our dev teams, but also now is helping the infrastructure team and other departments. The knowledge of Jenkins utilization replicates really fast inside our organization as at least one people inside every team learned about or knows how to use it to build a simple job to automate a task, workflow or a deploy. Jenkins also allows us to monitor what's being done, helping managers and the team have an overview of how a pipeline is running. Another problem that Jenkins solved is centralizing automation. As it's controlled by a web console, it's easy to check what is being done, access logs of old jobs, view the entire console output and know exactly who and when a job was last executed. Also, you may set permissions by project, by job, or what you or your organization needs.
Read this authenticated review
No photo available
July 05, 2018

Jenkins at a glance

Score 8 out of 10
Vetted Review
Verified User
Review Source

Use Cases and Deployment Scope

Jenkins is used for automating the build process of testing, deployment, and release. It makes continuous deployment faster and an automated process. It is used across the organization.
Read this authenticated review
No photo available
February 28, 2018

Jenkins Review

Score 8 out of 10
Vetted Review
Verified User
Review Source

Use Cases and Deployment Scope

It is being used by mostly the technology department. It allows us to run jobs between engineers and non-engineers. It increases productivity by automating processes.
Read this authenticated review
Jonathan Yu profile photo
Score 8 out of 10
Vetted Review
Verified User
Review Source

Use Cases and Deployment Scope

I used Jenkins to manage both development and release builds of software at my two previous roles (IBM and Red Hat.) In both cases, each department had its own instances, so that plugins could be customized and managed on a per-team, per-product basis. It enables teams to manage a fleet of build servers (slaves in Jenkins parlance) that can build source code and run tests in an automated fashion, across platforms - this enables cross-platform software to be tested against various versions of Windows and Linux, for example. It can also be used for simple automation tasks, though other tools like Ansible are better suited for those tasks.
Read Jonathan Yu's full review

About Jenkins

Jenkins is an open source continuous integration tool.
Categories:  Build Automation

Jenkins Integrations

Jenkins Technical Details

Operating Systems: Unspecified
Mobile Application:No