Jenkins Reviews & Insights

Score8.3 out of 10

510 Reviews and Ratings

Community insights

TrustRadius Insights for Jenkins are summaries of user sentiment data from TrustRadius reviews and, when necessary, third party data sources.

Pros

Automated Build Process: Many users have found the automated build process in Jenkins to be great, emphasizing its efficiency and reliability. They appreciate the seamless automation of tasks, from compiling code to deploying applications, without human intervention. The ability to run code against any testing suite and automatically rollback faulty programs has been particularly valued by reviewers.

Supportive Community: Jenkins has garnered praise for its extremely supportive community that readily offers assistance and troubleshooting guidance. Reviewers have specifically mentioned how valuable it is to have a strong network of experienced users who are willing to share their knowledge and help others overcome challenges.

Connectivity with Multiple Clouds: Users highly value Jenkins' support for connectivity with multiple clouds, including Azure, AWS, GCP, OCI, and more. This feature enables them to deploy applications across different platforms seamlessly. Several reviewers have expressed their satisfaction with this flexibility as it allows them to leverage various cloud services based on their specific needs.

Reviews

74 Reviews

Jenkins Powerful CICD Tool with Flexibility at the Cost of Usability

Rating: 6 out of 10

Incentivized

May 7, 2025

Use Cases and Deployment Scope

Jenkins is used for triggering builds in our company. We have more than 20+ apps which needs to be deployed , and we take help of jenkins to do so. From frontend, to backend to ML team, all uses jenkins for their deployment.
Jenkins helps us speed up our delivery by allowing parallel builds and testing, significantly improving deployment times. Jenkins integrates seamlessly with Git (GitHub/GitLab), Docker, Kubernetes, and other DevOps tools we use, enabling end-to-end automation.

Pros

Monitors source code repositories pretty well
Automatically triggers the deployment when new code is pushed
Advanced logic like conditional steps, parallel execution, or environment-specific stages
Reusability across projects using shared libraries

Cons

Complex UI
Less user friendly
Should not go down
Plugin Dependency and Maintenance Overhead
Limited Native Support for Modern Cloud-Native Workflows

Likelihood to Recommend

1. Suited well for a company which has more than 10 apps to deploy. 2. Not suited for a place where Serverless or Event-Driven CI/CD with Minimal Setup is required.
3. If project requires fine-tuned control over build steps, conditional deployment flows, and script-heavy automation, Jenkins provides unmatched flexibility using Jenkins file and Groovy scripting.

Verified User

Engineer in Engineering (1001-5000 employees)

Vetted Review

7 years of experience

The Power of Flexibility and Scalability for CICD Automation.

Rating: 7 out of 10

Incentivized

April 24, 2025

Use Cases and Deployment Scope

Jenkins integrates well with tools like Ansible, Terraform, Docker, and Kubernetes. Used to automate the build, test, and deployment processes across multiple teams, projects, and environments.

Pros

Lots of plugins.
Highly Configurable.

Cons

UI/UX Feels Outdated.
Steep learning curve.

Likelihood to Recommend

Centralized pipeline management using shared libraries and templates. Multi-branch pipelines for handling parallel feature development. Send notifications to Slack, Teams, email, or enterprise dashboards. Integrate with SonarQube, JIRA, Prometheus, and others for metrics and tracking. Produce detailed test and deployment reports—Ross's large dev teams.

Verified User

Engineer in Information Technology (1001-5000 employees)

Vetted Review

1 year of experience

Jenkins : An opensource tool for automating software development and deployment

Rating: 7 out of 10

Incentivized

October 30, 2024

Use Cases and Deployment Scope

We are using Jenkins for continuous integration and continuous deployment in our organization. It has helped in moving towards automation and currently major applications created using TIBCO BPM Enterprise, React UI and Node JS are being deployed using Jenkins. Jenkins has helped a great deal to not just developers but system administrators as well. Any additional tasks which need to be completed along with deployment are added in the scripts which gets executed during deployment.

Pros

Automated deployment
It is open source and user friendly
Customize deployment pipeline as per the requirements
Supports good documentation

Cons

There can be performance issues due to single server architecture.
Implementation is not relatively easy
User interface has room for improvement
Redundant pluggins

Likelihood to Recommend

Jenkins is suitable to implement for small organizations as it uses single server architecture. It can be used to automate deployments and script execution which helps users automate manual tasks. Jenkins is opensource and has a strong community which helps in resolving errors. Jenkins might not be suitable for large organizations or complex architectures. There are other competitors which might have an edge like Atlassian Bamboo/Octopus.

Verified User

Employee in Information Technology (5001-10,000 employees)

Vetted Review

3 years of experience

Powerful CICD tool for handling all stages in pipeline with versatile programs.

Rating: 8 out of 10

Incentivized

October 30, 2024

Use Cases and Deployment Scope

We use Jenkins as a main CICD in our project, we organize jobs with similar function into Group, we create jobs for the build, compile, and unit test each time a developer check-in their code to a specified branch and build a new version of artifact when having master branch commit. We add some additional plugin and create Jenkins jobs for run system test, automation test, and integration test automatically when having new commit to master and have jobs for deploy our new code to destination VMs on demand.

Pros

continuous deployment
continuous integration
continuous delivery also it's the best integration tools in the market

Cons

Jenkins UI looks bit classic, and it is hard for manage when we have a large number of jobs and pipeline
It does not have features for tracking job history, sometimes accident deletes or changes to a job and we unable to recover it.
User and roles management needs some improvement

Likelihood to Recommend

Its' a good for continuous deployment, continuous integration, and continuous delivery also it's the best integration tools in the market. It also supports many plugins and it is targeting users are developers and teams looking to automate parts of their software development
process. If number of jobs are more this won't be that great application.

Shivanand Labbi

Senior software engineer in Information Technology at Manhattan (501-1000 employees)

Vetted Review

6 years of experience

Jenkins - Hard to use but can be set up to do anything

Rating: 7 out of 10

Incentivized

July 2, 2024

Use Cases and Deployment Scope

We use Jenkins to build and deploy all our applications. This range from web services, APIs, docker images, automated tests to small helper scripts. It automates all our build flows and make sure we always build using the same environment like most CI. As we have many applications depending on one API that have to be rebuilt every time, Jenkins provide us a cheaper alternative that is not dependent on build minutes.

Pros

Build java applications
Plugins for any use case
Able to adapt to your needs
Supports Active Directory integration

Cons

UI can feel quite clunky and slow
More functionality built in instead of having to rely on third party plugins
Project of type Maven is most of the time buggy, we need to use free-style project to avoid this bugs losing out of the box functionality

Likelihood to Recommend

I think Jenkins is well suited if you are using a lot of build minutes and have to use your own hardware. It is also well suited if you need to customize your build and deploy process quite much, which is very possible with Jenkins. If your build and deploy needs are rather straight forward, it might be easier to just get a cloud service that provide you with easier to use interface and processes.

Verified User

Professional in Information Technology (1001-5000 employees)

Vetted Review

12 years of experience

My choice is Jenkins, for pipeline deployment!

Rating: 10 out of 10

Incentivized

June 16, 2023

Use Cases and Deployment Scope

We used Jenkins to implement deployment automation through CI/CD pipeline. Deployment has been easy now. We were building and deploying our applications manually into DEV, test and PRD environments. It was time consuming and it involved repetitive tasks, we used the jenkins to remove all these manual tasks.

Pros

Automated build package
Automated deployment
Automated job run

Cons

Performance improvement
Handling plugins is difficult
UI is outdated

Likelihood to Recommend

Its easy to configure for simple pipeline deployment. Saves lot of time and manual efforts fir build and deployment.

Verified User

Engineer in Information Technology (10,001+ employees)

Vetted Review

5 years of experience

Drive your Continuous Integration Pipelines via Scripting with Jenkins

Rating: 10 out of 10

June 6, 2023

Use Cases and Deployment Scope

We use Jenkins in our continuous integration pipelines. With Jenkins, we build and test our microservices. We also make extensible use of the plugin capability (we also develop and maintain internal plugins) to cover complex build/testing scenarios.

Pros

Extensive documentation
Big community and popularity
Easy to extend and customize

Cons

Improve configuration portability
Improve scalability
Increase interoperability with containers
Introduce ways to update common dependencies automatically (eg Docker)

Likelihood to Recommend

Jenkins' strengths are:

Scripting: Using Groovy we can extend the plugins' behavior and customize the way we build our projects. If you have complex pipelines and tricky build scenarios, please consider the use of Jenkins.
Maturity: Nowadays we have powerful CI alternatives, but Jenkins is a tool used for many companies and has an active community so it's easy to find documentation related to almost any setup, also there are plenty of people with knowledge about it.

Some areas where Jenkins needs improvement are:

Updating: Jenkins needs to introduce/facilitate ways to update external dependencies.
Scalability: For some workloads, Jenkins still has issues with performance.

Verified User

Technician in Engineering (501-1000 employees)

Vetted Review

3 years of experience

Jenkins - review.

Rating: 9 out of 10

Incentivized

May 22, 2023

Use Cases and Deployment Scope

We utilized Jenkins to enable Continuous Integration and Deployment on 100s of our microservices. Deployed the Modular Pipelines architecture on Jenkins to enable seamless CI/CD between services utilizing different frameworks. So the thing is our pipelines facilitate the CI process from checking out code to building the artifact and then deploying it on Kubernetes.

Pros

Used Jenkins as CI/CD tool.
Extremely supportive community.
Support connectivity with multiple clouds so the deployments over Azure, AWS, GCP, OCI and etc are supported.
Trigger builds and deployments on Linux or Windows agents without issue.
Support multiple version control tools.

Cons

High memory utilization.
Troubleshooting at times is hard as some plugins have bad error handling.
Master/Agent connection must be more robust.

Likelihood to Recommend

Jenkins is a highly customizable CI/CD tool with excellent community support. One can use Jenkins to build and deploy monolith services to microservices with ease. It can handle multiple "builds" per agent simultaneously, but the process can be resource hungry, and you need some impressive specs server for that. With Jenkins, you can automate almost any task. Also, as it is an open source, we can save a load of money by not spending on enterprise CI/CD tools.

Muhammad Arsalan Niazi

Sr. Lead Devops Engineer in Information Technology at Nisum (1001-5000 employees)

Vetted Review

6 years of experience

View profile

Jenkins-making deployments easy.

Rating: 9 out of 10

Incentivized

May 22, 2023

Use Cases and Deployment Scope

My company uses Jenkins for building, testing, and deploying our projects. Since you can have all these plugins and works with GitHub, Jenkins seems to be the obvious choice. Jenkins also offers code quality as it has plugins to check the code. This helps us as we know if the Jenkins run fails or goes below the score quality, then we can catch major problems before they are deployed.

Pros

Building
Code quality.
Deployments
Testing

Cons

Documentation
Logging

Likelihood to Recommend

Since I have worked with Jenkins, it has been reliable 9 out of 10 times. Considering you can build a docker file, test your code, have a sonar plugin for quality control, and then deploy the docker image all in one, this makes Jenkins very convenient to use. There have been times when Jenkins does not run. I am unsure if it is due to how many people are using the instance. It doesn't give a great description of why, which is the only time I have had negative issues with Jenkins.

Verified User

Employee in Information Technology (10,001+ employees)

Vetted Review

4 years of experience

Streamlining Development Workflows.

Rating: 9 out of 10

Incentivized

May 22, 2023

Use Cases and Deployment Scope

The workflow begins with developers submitting pull requests containing their code changes and documentation. Jenkins automatically triggers builds, running unit tests to verify functionality and code analysis tools to assess quality and adherence to standards. Integration testing follows, ensuring seamless component interaction. User acceptance testing occurs in a dedicated environment, allowing stakeholders and users to provide feedback. Jenkins generates reports and notifications throughout the process, keeping stakeholders informed. Finally, upon review and approval, Jenkins handles the deployment to the production environment. This streamlined approach improves efficiency, consistency, and visibility, ensuring high-quality software releases.

Pros

Automated Builds: Jenkins is configured to monitor the version control system for new pull requests. Once a pull request is created, Jenkins automatically triggers a build process. It checks out the code, compiles it, and performs any necessary build steps specified in the configuration.
Unit Testing: Jenkins runs the suite of unit tests defined for the project. These tests verify the functionality of individual components and catch any regressions or errors. If any unit tests fail, Jenkins marks the build as unsuccessful, and the developer is notified to fix the issues.
Code Analysis: Jenkins integrates with code analysis tools like SonarQube or Checkstyle. It analyzes the code for quality, adherence to coding standards, and potential bugs or vulnerabilities. The results are reported back to the developer and the product review team for further inspection.

Cons

User Interface: The Jenkins user interface can be complex and overwhelming for new users. Improving the user experience and making it more intuitive would help streamline the onboarding process and enhance usability for both beginners and experienced users.
Configuration Management: Managing and configuring Jenkins can be challenging, especially when dealing with large and complex projects. Simplifying the configuration process and providing more user-friendly options for managing pipelines and jobs would be beneficial.
Scalability: As projects grow and the number of builds and jobs increases, Jenkins can experience performance issues and scalability challenges. Optimizing Jenkins for larger-scale deployments and providing better support for distributed builds and parallelization would help address these limitations.

Likelihood to Recommend

In a scenario where a small software development team is working on a simple project with minimal codebase and a straightforward deployment process, Jenkins may not be well suited. The overhead and complexity of setting up and maintaining Jenkins could outweigh the benefits of such a small-scale project. Additionally, the learning curve associated with Jenkins, along with its resource-intensive nature, might not be justifiable for a team with limited resources and a shared infrastructure. Alternative lightweight CI/CD solutions that offer streamlined workflows and require minimal configuration may provide a more suitable and efficient choice for small projects with straightforward requirements, focusing on simplicity, speed, and ease of use.

Damon Darling

Engineering Manager in Engineering at Sigma Connectivity (501-1000 employees)

Vetted Review

12 years of experience

View profile