--- title: Jenkins Reviews meta_title: 'Jenkins Reviews 2026: Details, Pricing, & Features | G2' meta_description: Filter 568 reviews by the users' company size, role or industry to find out how Jenkins works for a business like yours. aggregate_rating: rating_value: 4.4 review_count: 568 scale: '5' date_modified: '2026-07-13' parent_category: name: CI/CD Tools url: https://www.g2.com/categories/ci-cd-tools --- # Jenkins Reviews **Vendor:** The Continuous Delivery Foundation (CDF) **Category:** [Continuous Integration Tools](https://www.g2.com/categories/continuous-integration) **Average Rating:** 4.4/5.0 **Total Reviews:** 568 ## About Jenkins The leading open source automation server, Jenkins provides hundreds of plugins to support building, deploying and automating any project. ## Jenkins Pros & Cons **What users like:** - Users find Jenkins to be **very easy to learn and use** , making it accessible for a wide range of users. (23 reviews) - Users value the **seamless integrations** of Jenkins with various tools, enhancing their build and deployment processes. (18 reviews) - Users appreciate the **extensive plugins** offered by Jenkins, enhancing customization and flexibility in their workflows. (16 reviews) - Users value the **extensive plugin support** in Jenkins, enhancing its integration and customization for CI/CD pipelines. (15 reviews) - Users appreciate the **automation capabilities** of Jenkins, enjoying easy integration and extensive plugin support for CI/CD pipelines. (12 reviews) - Flexibility (12 reviews) - Users value Jenkins for its **automation efficiency** , ensuring smooth continuous integration and delivery processes with extensive support. (11 reviews) - CD Integration (10 reviews) - Easy Integrations (10 reviews) - Pipeline Management (9 reviews) **What users dislike:** - Users find Jenkins' reliance on plugins to be **confusing and troublesome** , leading to maintenance challenges and complexity. (14 reviews) - Users find Jenkins' **confusing interface** and outdated UI complicate navigation and management of jobs and plugins. (11 reviews) - Users find the **difficult setup** of Jenkins challenging, requiring significant time and technical expertise, especially for newcomers. (8 reviews) - Users find the **outdated interface** of Jenkins challenging, leading to difficulties in setup and management. (8 reviews) - Users find the **UI outdated** and complex, making setup and management challenging, especially for newcomers. (8 reviews) - Users experience **complex setup** challenges with Jenkins, particularly due to the intricate configuration and plugin management. (7 reviews) - Performance Issues (7 reviews) - Update Issues (7 reviews) - Users find Jenkins **complex to set up and manage** , struggling with its outdated UI and plugin compatibility issues. (6 reviews) - Users face a **steep learning curve** with Jenkins, making initial set up and navigation challenging for beginners. (5 reviews) ## Jenkins Reviews ### 1. Easy Integrations, Solid Docs, and Highly Customizable Jenkins Pipelines **Rating:** 4.5/5.0 stars **Reviewed by:** Anish M. | Member Of Technical Staff - Software Development (AI), Enterprise (> 1000 emp.) **Reviewed Date:** May 27, 2026 **What do you like best about Jenkins?** It is able to integrate easily with tools like Bitbucket, Kubernetes, Docker, SonarQube and similar tools. It has pretty good documentation making life easier to connect and work in production environment and Dev environment. Jenkins can automate builds, testing, deployments, rollback workflows, notifications, and infrastructure tasks reliably across multiple environments. Also we are able to tailor pipelines as per our needs effectively. **What do you dislike about Jenkins?** When we have hundreds of pipelines running across dynamic agents, Kubernetes workers, or hybrid infra, diagnosing intermittent failures becomes painful. Problems are often non-deterministic, agent drift, workspace contamination, plugin thread deadlocks, credential injection timing, or executor starvation. With teams building the pipelines based on the knowledge they have. Some are tightly coupled and needs the respective owners to find issues. **What problems is Jenkins solving and how is that benefiting you?** With Jenkins solving the CI/CD workflow, having code stored in a repo and you manually validate the tests and then copy the code and paste into the server is a lot of burden with Jenkins one time setup and the process of shipping code with tests get very optimal. It acts as the automation backbone connecting source control system. ### 2. Simply the best CI/CD tool **Rating:** 5.0/5.0 stars **Reviewed by:** Ankit S. | Back End Developer, Small-Business (50 or fewer emp.) **Reviewed Date:** January 20, 2022 **What do you like best about Jenkins?** Jenkins is a powerful CI/CD tool for organizations that want to automate work such as building, deploying, administration, testing, and more. You can create separate jobs for each stage—like build, deploy, and test—and then organize them together in a group for better structure. It’s also straightforward to install and configure. On top of that, there are many plugins available that make it easy to integrate Jenkins with other tools. **What do you dislike about Jenkins?** Sometimes it becomes very difficult to manage when there are many jobs. We can’t recover deleted jobs or pipelines, which is frustrating. Maintenance and updates depend on the user, so you need to know how everything works in order to use all of its functionality. **Recommendations to others considering Jenkins:** From a developer's point of view, if you want to save your time and resource, then you should go for it. It has a high developer community, is highly customizable, and has a lot of plugins. **What problems is Jenkins solving and how is that benefiting you?** With the help of continuous integration and continuous delivery tool, we save a lot of resources in our organization. We deploy, build and test in one go. With Jenkins, we save a lot of money and time. ### 3. A One-Stop Shop for Integrations, CI/CD Scaling, and Easier Version Control **Rating:** 5.0/5.0 stars **Reviewed by:** Chirag A. | Software Automation Developer, Transportation/Trucking/Railroad, Enterprise (> 1000 emp.) **Reviewed Date:** April 29, 2026 **What do you like best about Jenkins?** It's a one stop shop for integrating with any tools be it a custom aplication too. I use Worksoft Certify and it integerates well with it. Also it scales from simple automation to highly complex CI/CD systems, while giving teams full control over how they build and deliver software. The version control becomes too much easier with it. Also since it's open source on local host and doesn't have any price associated with it. **What do you dislike about Jenkins?** It often requires a dedicated owner to keep it healthy and effective. Also most of the plugins become obsolete and I have to update them manually to keep it healthy. Plugins can become unmaintained, break after updates, or clash with one another, sometimes causing pipelines to fail unexpectedly. Also the Jenkins UI still feels dated compared to modern CI/CD platforms. Navigating jobs, logs, and configuration can be clunky, especially for new users. **What problems is Jenkins solving and how is that benefiting you?** It’s the only CI/CD tool for me that has the CTM plugin, and it integrates easily with the Worksoft Continuous Testing Manager, which in turn runs the Worksoft Test Suite. Overall, it has made my life easier: the builds run smoothly, and the reporting is accurate and does what I need. ### 4. Automating Development for Faster and Reliable Workflows **Rating:** 4.5/5.0 stars **Reviewed by:** Kushal K. | MERN developer, Mid-Market (51-1000 emp.) **Reviewed Date:** April 21, 2026 **What do you like best about Jenkins?** What I like most about Jenkins is its flexibility and how easily it supports continuous integration and delivery. It automates tasks like building, testing, and deployment, which saves time and helps catch issues early in the development process. Another strong point is its large plugin ecosystem. You can integrate it with almost any tool or technology, making it suitable for different types of projects. On top of that, since it’s open-source and widely used, there’s plenty of community support and resources available. Overall, it makes development workflows more efficient, organized, and reliable. **What do you dislike about Jenkins?** One downside of Jenkins is that it can be difficult to set up and maintain, especially for beginners. Managing plugins and keeping them updated can sometimes cause compatibility issues. Its user interface also feels outdated, and configuring complex pipelines can become messy without proper experience. **What problems is Jenkins solving and how is that benefiting you?** Jenkins solves the problem of manual and repetitive tasks in software development, like building, testing, and deploying code. Instead of doing these steps by hand, it automates everything through a pipeline. This benefits me by saving time, reducing human errors, and giving faster feedback on code changes. It also helps keep the development process more consistent and organized, which improves overall productivity. ### 5. Reliable Automation for Faster Builds and Deployments **Rating:** 5.0/5.0 stars **Reviewed by:** Priyanka B. | Senior QA Automation Engineer, Mid-Market (51-1000 emp.) **Reviewed Date:** May 05, 2026 **What do you like best about Jenkins?** I like Jenkins best because it makes build, test, and deployment automation reliable and repeatable. Its huge plugin ecosystem and flexible pipeline support make it easy to integrate with different tools and adapt to different project needs. It also helps save time by reducing manual steps and making CI/CD workflows more consistent. **What do you dislike about Jenkins?** Jenkins is very powerful, but I dislike the complexity of setting it up and maintaining it. The UI feels dated, plugin management can be messy, and pipelines sometimes require more manual effort than I’d like. For larger projects, it can also take time to keep everything running smoothly and consistently. **What problems is Jenkins solving and how is that benefiting you?** Jenkins solves the problem of manual and inconsistent build, test, and deployment processes. It benefits me by automating repetitive work, reducing errors, providing faster feedback on changes, and making our release process more reliable and efficient. ### 6. Best-in-Class Open-Source CI/CD, But Integration Requires Patience with Docs **Rating:** 3.5/5.0 stars **Reviewed by:** arpit a. | Senior Software Engineer, Enterprise (> 1000 emp.) **Reviewed Date:** May 21, 2026 **What do you like best about Jenkins?** In my opinion, this is the best open-source tool for creating and running CI/CD pipelines. **What do you dislike about Jenkins?** Not everyone can go through, or is used to going through, lengthy documentation just to get something integrated or to complete a deployment with an open-source tool. In many cases, people would rather use Azure Devops or Atlassian products for the same kind of work, pay someone to set it up, and then customize everything through a UI. **What problems is Jenkins solving and how is that benefiting you?** It helps me create continuous integration and continuous deployment pipelines at no cost. Any tech-savvy person can install it and have a CI/CD pipeline set up and ready to use without paying anything. ### 7. Extensive Plugin Library Makes Jenkins Highly Integrable **Rating:** 4.0/5.0 stars **Reviewed by:** Harsh V. | Co-Founder, Small-Business (50 or fewer emp.) **Reviewed Date:** June 09, 2026 **What do you like best about Jenkins?** The single biggest advantage of Jenkins is its extensive library of plugins. Whether you need to integrate with version control systems (Git, SVN), cloud providers (AWS, Azure, Google Cloud), containerization tools (Docker, Kubernetes), or notification services (Slack, Email), there is almost certainly a Jenkins plugin available for it. **What do you dislike about Jenkins?** The core Jenkins UI feels like a relic from the 2000s. Navigating logs, configuring complex jobs manually in the GUI, and troubleshooting failed builds can be frustrating and unintuitive compared to modern, streamlined interfaces. **What problems is Jenkins solving and how is that benefiting you?** Jenkins pipelines natively support parallel execution. You can configure a Jenkinsfile to split a massive test suite into chunks and run them simultaneously across multiple worker nodes. A build that takes 2 hours sequentially can be reduced to 15 minutes by fanning it out across parallel agents, drastically improving the performance of the feedback loop. ### 8. JENKINS - Flexible Automation That Streamlines CI/CD Workflows **Rating:** 4.5/5.0 stars **Reviewed by:** Subhashree S. | System Engineer, Enterprise (> 1000 emp.) **Reviewed Date:** May 25, 2026 **What do you like best about Jenkins?** What I like best about Jenkins is its flexibility and strong automation capabilities. It makes CI/CD workflows much easier by automating builds, testing, and deployments, which saves time and helps maintain a smoother development process. **What do you dislike about Jenkins?** One thing I dislike about Jenkins is that the initial setup and plugin management can be a bit complex, maintaining pipelines sometimes requires extra effort and troubleshooting. **What problems is Jenkins solving and how is that benefiting you?** Jenkins helps automate the build, testing, and deployment process, reducing manual effort and minimizing human errors. This speeds up development cycles, improves release reliability, and allows the team to deliver updates more efficiently. ### 9. Reliable CI/CD Automation for Development Teams **Rating:** 4.0/5.0 stars **Reviewed by:** Hrithik V. | Software Engineer - Trading Systems, Mid-Market (51-1000 emp.) **Reviewed Date:** June 05, 2026 **What do you like best about Jenkins?** Jenkins provides a flexible and reliable CI/CD platform with strong automation capabilities. It integrates well with our build, testing, and deployment workflows and supports a wide range of plugins and customizations. **What do you dislike about Jenkins?** The user interface feels dated, and managing plugins and pipeline configurations can become complex over time. Initial setup and maintenance often requires significant time and effort. **What problems is Jenkins solving and how is that benefiting you?** Jenkins automates CI/CD workflows for our services, including application builds, container image creation, testing, and deployments. By standardizing these processes, it reduces manual operational overhead and enhances performance by shortening release cycles. ### 10. Rock-Solid Jenkins CI for UI Automation with Seamless Selenium Grid Integration **Rating:** 4.0/5.0 stars **Reviewed by:** Sree K. | Software Engineer II in Test, Information Technology and Services, Mid-Market (51-1000 emp.) **Reviewed Date:** January 26, 2026 **What do you like best about Jenkins?** Jenkins mostly just keeps the CI lights on for our UI automation, which is honestly what I need most days. We host it on a Linux server and it’s rock-solid: pipelines fire when they should, and the connection to our Selenium Grid on remote Windows 11 machines is seamless enough that I barely think about it. I kick off a job, agents spin up, tests run, reports land—done, no drama. The plugin ecosystem is a big win too: test reporters, HTML publisher, Slack and email notifications, credentials bindings, all the usual suspects. That makes it easy to wire up a pipeline that matches our workflow without bolting on a bunch of custom glue. Once the Jenkinsfile is in place, everything feels predictable run after run; the logs are clear enough, and failures usually point to the right stage so I can fix things and move on. Day-to-day usage is pretty straightforward. We schedule weekly runs across different environments, pass parameters for browser or env, and the matrix job handles it cleanly without me babysitting every combo. Branch builds are easy, artifacts get archived, and test results show up in the job with trends so we can spot regressions fast instead of guessing. Git integration is simple enough too: webhooks trigger CI, the job picks up the latest commit, and there are no manual steps or copy-paste. Labels help isolate jobs so Windows grid work stays separate from other tasks, and the Linux master stays calm even when the queue gets busy. Folders and role-based access provide decent guardrails, secrets live in the credentials store so people don’t stash tokens in scripts, and shared library functions keep our pipeline steps consistent across repos, which cuts down the chaos a lot. Support and docs are decent, and the community answers usually get me unstuck when I hit an odd edge case—often after a plugin update. It’s not perfect: plugins can be picky, a node will go offline now and then, and sometimes a flaky test makes a stage look worse than it is. Still, the feedback loop is fast and reliable. The net result is simple: faster iteration, fewer setup headaches, and cleaner commits that flow right into our ADO repo and CI without me babysitting a bunch of steps. It keeps the work organized and predictable, which is exactly what I need for UI automation, and it saves me a lot of little minutes across the week so I can focus on fixing issues instead of wrangling the pipeline. **What do you dislike about Jenkins?** The initial setup was the only part that felt genuinely tricky. We spent quite a bit of time going back and forth with DevOps to land on the right configurations, plugins, agent permissions, and service accounts. Once that was sorted out, everything has been smooth sailing. Every so often, the Selenium Grid goes down, but that’s tied to our remote machines rather than Jenkins itself—usually a restart on the Windows side brings it right back. Plugin updates can also be a little touchy at times: dependencies get bumped and then a job starts complaining, but a quick rollback or a small reconfiguration typically resolves it. None of this is a dealbreaker; they’re just minor bumps you notice more when deadlines are tight. **What problems is Jenkins solving and how is that benefiting you?** Jenkins solves the repeatable testing problem for us. Rather than running test suites by hand, we rely on pipelines that run on a schedule, target the right environment, publish reports, and notify the team. The result is faster feedback, fewer manual errors, and a clear trail showing what ran, when it ran, and why it passed or failed. It also keeps coordination straightforward: there’s one place to check status, logs, artifacts, and history, which makes handoffs and audits much easier. Overall, we spend less time babysitting runs, more time fixing real issues, and the whole automation workflow feels calmer and more manageable. ## Jenkins Discussions - [What is Jenkins used for?](https://www.g2.com/discussions/what-is-jenkins-used-for) - 2 comments, 1 upvote - [Is there any plan to change jenkins UX/UI](https://www.g2.com/discussions/is-there-any-plan-to-change-jenkins-ux-ui) - 1 comment, 1 upvote - [Does it integrate with Microsoft Project?](https://www.g2.com/discussions/13687-does-it-integrate-with-microsoft-project) - 1 comment, 1 upvote - [View Jenkins pricing details and edition comparison](https://www.g2.com/products/jenkins/reviews/jenkins-review-2940468?section=pricing&secure%5Bexpires_at%5D=2026-07-14+16%3A41%3A23+-0500&secure%5Bsession_id%5D=e0ae60d1-5270-446c-9708-a46942a9a995&secure%5Btoken%5D=03a7194174fb8fd757c974e30b95019deaed35425216722df43d5c9b8c07cd98&format=llm_user) ## Jenkins Integrations - [Amazon EC2](https://www.g2.com/products/amazon-ec2/reviews) - [Amazon EC2 Auto Scaling](https://www.g2.com/products/amazon-ec2-auto-scaling/reviews) - [Amazon Elastic Container Registry (ECR)](https://www.g2.com/products/amazon-elastic-container-registry-ecr/reviews) - [Amazon Elastic Kubernetes Service (Amazon EKS)](https://www.g2.com/products/amazon-elastic-kubernetes-service-amazon-eks/reviews) - [Amazon S3 Glacier](https://www.g2.com/products/amazon-s3-glacier/reviews) - [Apache Maven](https://www.g2.com/products/apache-maven/reviews) - [AWS Cloud Development Kit (AWS CDK)](https://www.g2.com/products/aws-cloud-development-kit-aws-cdk/reviews) - [AWS CodePipeline for CI/CD Automation](https://www.g2.com/products/aws-codepipeline-for-ci-cd-automation/reviews) - [Azure DevOps Server](https://www.g2.com/products/azure-devops-server/reviews) - [Azure Portal](https://www.g2.com/products/azure-portal/reviews) - [Barracuda Cloud-to-Cloud Backup](https://www.g2.com/products/barracuda-cloud-to-cloud-backup/reviews) - [Bitbucket](https://www.g2.com/products/bitbucket/reviews) - [BlueOceanAI (Formally BlueOcean Brand Navigator)](https://www.g2.com/products/blueoceanai-formally-blueocean-brand-navigator/reviews) - [BrowserStack](https://www.g2.com/products/browserstack/reviews) - [Codex](https://www.g2.com/products/openai-codex/reviews) - [Discord](https://www.g2.com/products/textaify-discord/reviews) - [Docker](https://www.g2.com/products/docker-inc-docker/reviews) - [Git](https://www.g2.com/products/git/reviews) - [GitHub](https://www.g2.com/products/github/reviews) - [GitLab](https://www.g2.com/products/gitlab/reviews) - [Gradle Build Tool](https://www.g2.com/products/gradle-build-tool/reviews) - [Grafana Labs](https://www.g2.com/products/grafana-labs/reviews) - [IBM Vault (formerly HashiCorp Vault)](https://www.g2.com/products/ibm-vault-formerly-hashicorp-vault/reviews) - [Jira](https://www.g2.com/products/jira/reviews) - [Jira Service Management](https://www.g2.com/products/jira-service-management/reviews) - [JUnit](https://www.g2.com/products/junit/reviews) - [Kubernetes](https://www.g2.com/products/kubernetes/reviews) - [Microsoft Teams](https://www.g2.com/products/microsoft-teams/reviews) - [npm](https://www.g2.com/products/npm/reviews) - [Selenium Grid on Windows](https://www.g2.com/products/selenium-grid-on-windows/reviews) - [ServiceNow IT Service Management](https://www.g2.com/products/servicenow-it-service-management/reviews) - [Slack Connector for Jira](https://www.g2.com/products/slack-connector-for-jira/reviews) - [SonarQube](https://www.g2.com/products/sonarqube/reviews) - [Worksoft Certify](https://www.g2.com/products/worksoft-certify/reviews) ## Jenkins Features **Functionality** - Deployment-Ready Staging - Integration - Extensible **Management** - Configuration Management - Access Control - Orchestration **Functionality** - Integrations - Extensibility - Test Customization **Agentic AI - AWS Marketplace** - Autonomous Task Execution - Multi-step Planning - Cross-system Integration **Management** - Processes and Workflow - Reporting - Automation **Functionality** - Automation - Integrations - Extensibility **Management** - Automation - Processes and Workflow - Reporting **Processes** - Pipeline Control - Workflow Visualization - Continuous Deployment **Agentic AI - Continuous Integration** - Autonomous Task Execution - Cross-system Integration - Adaptive Learning - Natural Language Interaction - Proactive Assistance **Agentic AI - Continuous Delivery** - Autonomous Task Execution - Cross-system Integration - Adaptive Learning - Natural Language Interaction - Proactive Assistance ## Top Jenkins Alternatives - [GitHub](https://www.g2.com/products/github/reviews) - 4.7/5.0 (2,312 reviews) - [CloudBees](https://www.g2.com/products/cloudbees/reviews) - 4.4/5.0 (591 reviews) - [CircleCI](https://www.g2.com/products/circleci/reviews) - 4.4/5.0 (499 reviews)