# 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:** 565 ## 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 use** , facilitating seamless integration and comprehensive DevOps support. (23 reviews) - Users value Jenkins for its **seamless integrations** with various tools, enhancing automation and workflow flexibility across projects. (18 reviews) - Users appreciate the **extensive plugins** in Jenkins, enabling seamless integration with various tools and platforms. (16 reviews) - Users appreciate the **extensive plugin support** of Jenkins, enabling seamless integration with various tools and platforms. (15 reviews) - Users value the **flexibility of automation** provided by Jenkins, enhancing their CI/CD processes across diverse environments. (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 experience **plugin issues** with compatibility and memory consumption, impacting their overall Jenkins experience. (14 reviews) - Users find the **confusing interface** of Jenkins to be outdated and challenging, complicating their workflow and setup. (11 reviews) - Users often find **Jenkins' setup challenging** , requiring significant time and effort for proper configuration and maintenance. (8 reviews) - Users find Jenkins' **user interface outdated** , leading to challenges in usability and overall experience. (8 reviews) - Users find the **poor UI** of Jenkins outdated and complex, making setup and management challenging 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' setup and management processes to be **complex** , particularly with its outdated UI and plugin 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. Jenkins Makes Automation Reliable with Flexible Integrations and Strong Community Support **Rating:** 4.5/5.0 stars **Reviewed by:** VINAY P. | Mechanical Design Engineer, Design, Enterprise (> 1000 emp.) **Reviewed Date:** June 02, 2026 **What do you like best about Jenkins?** What I like most about Jenkins is its ability to automate repetitive processes and keep workflows consistent. In my work, having automated tasks reduces the need for manual monitoring and helps ensure that routine activities are completed reliably. The platform is highly flexible and integrates well with different tools, which makes it easier to connect various stages of a workflow. I also appreciate the scheduling and notification capabilities, as they help keep teams informed about task status and completion without constant manual follow-up. Another advantage is the large community and documentation available. Whenever configuration changes or new requirements arise, it is usually possible to find helpful resources and examples, which simplifies implementation and ongoing maintenance. **What do you dislike about Jenkins?** One area that could be improved is the user interface, which can feel dated compared to newer platforms. As the number of jobs and workflows increases, navigation and administration can become more complex. **What problems is Jenkins solving and how is that benefiting you?** Before using Jenkins, many routine processes required manual execution and monitoring, which increased the possibility of delays and inconsistencies. Tracking the status of recurring tasks also required additional effort. Jenkins helps by automating scheduled and repeatable workflows, providing visibility into task execution and reducing manual intervention. This makes processes more consistent and allows teams to focus on higher-value work instead of repetitive administrative activities. As a result, less time is spent on manual coordination, workflows are more reliable, and task tracking becomes much easier. This improves efficiency, reduces errors, and helps maintain a more organized working environment. ### 2. 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. ### 3. 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. ### 4. 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. ### 5. 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. ### 6. 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. ### 7. 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. ### 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. 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. ### 10. Efficient Automation with Jenkins Despite Plugin Challenges **Rating:** 4.0/5.0 stars **Reviewed by:** Swaroop K. | DevOps Engineer, Pharmaceuticals, Small-Business (50 or fewer emp.) **Reviewed Date:** April 09, 2026 **What do you like best about Jenkins?** I use Jenkins to automate CI/CD pipelines for build and deployment workflows, which were previously manual. It integrates well with Git-based repositories and supports pipeline-as-code using Jenkinsfiles, making version control and changes easier to manage. The UI is simple for basic navigation like viewing job status, build history, and logs, which helps in quick troubleshooting. It also supports a wide range of plugins for integrating tools like Docker and Kubernetes, making it flexible for different environments. Examples: Automated build and deployment pipelines triggered on every code commit, reducing manual effort. Used Jenkins pipelines to deploy applications to Kubernetes clusters, improving release consistency. **What do you dislike about Jenkins?** Plugin management in Jenkins can be difficult, especially with version conflicts and outdated plugins causing instability. The UI also feels outdated for complex pipeline configurations, and debugging multi-stage pipelines is not always straightforward. Managing Jenkins at scale (like handling multiple jobs and agents) requires additional effort and maintenance. Examples: Plugin updates sometimes break existing pipelines due to compatibility issues. Debugging failed pipeline stages requires navigating multiple logs and views, which slows down troubleshooting. **What problems is Jenkins solving and how is that benefiting you?** Jenkins solves the problem of manual build and deployment processes by automating CI/CD workflows. This reduces human errors and speeds up the release cycle. It also provides visibility into build status and failures, which helps in identifying issues early in the development lifecycle. Overall, it improves deployment consistency and reduces downtime during releases. Examples: Earlier deployments were manual and error-prone; now pipelines handle builds, tests, and deployments automatically. Build failures are immediately visible with logs, reducing debugging time for the team. ### 11. Easy Setup, Powerful Plugins, and Time-Saving CI with Jenkins **Rating:** 4.5/5.0 stars **Reviewed by:** Ravi R. | DevOps Engineer, Mid-Market (51-1000 emp.) **Reviewed Date:** April 23, 2026 **What do you like best about Jenkins?** Easy setup, lots of plugins, simple UI, easy integrate with 3rd party tools with the help of plugins. It saves lots of time and easy to manage. Also for any support, online and official documents available. **What do you dislike about Jenkins?** As i.am using Jenkins from last 5 years, i noticed there are some features need to be added. Like plugins which are available, should be officially reinstall with Jenkins. As it is open source tool, it must be integrate with AI also. **What problems is Jenkins solving and how is that benefiting you?** Building, integrating and deployments of code. Plugins are very good, easy to install and play with your code whatever you want, Jenkins will do. ### 12. Jenkins Makes Automation Simple with Powerful, Flexible Pipelines **Rating:** 4.0/5.0 stars **Reviewed by:** Rahul K. | Associate Specialist, Insurance, Enterprise (> 1000 emp.) **Reviewed Date:** March 20, 2026 **What do you like best about Jenkins?** What I like best about Jenkins is that it makes automation really simple. You can set up pipelines to build, test, and deploy code without doing things manually every time. It saves a lot of effort, keeps everything consistent, and helps catch problems early. I also like that it has tons of plugins, so you can connect it with almost any tool you’re already using. In simple words: Jenkins makes life easier by automating repetitive tasks and keeping the whole development process smooth. **What do you dislike about Jenkins?** What I dislike about Jenkins is that it can feel old‑fashioned and heavy at times. The interface isn’t very user‑friendly, and setting up pipelines can get complicated if you’re not careful. It also needs a lot of plugins to do advanced things, which sometimes makes it harder to maintain. In simple words: Jenkins works well, but it’s not always easy to use, can get messy with plugins, and takes effort to manage **What problems is Jenkins solving and how is that benefiting you?** Jenkins is solving the problem of manual builds, testing, and deployments. Without it, developers would have to repeat the same steps again and again, which wastes time and can cause mistakes. Jenkins automates all of this with pipelines, so the whole process becomes faster, more reliable, and consistent. The benefit for me is that I don’t have to worry about doing things manually—code gets built, tested, and deployed automatically. In simple words: Jenkins saves time, reduces errors, and makes the development process smooth. ### 13. Highly Configurable for CI/CD, But Steep Learning Curve **Rating:** 3.5/5.0 stars **Reviewed by:** Saroj P. | Senior Software Engineer, Mid-Market (51-1000 emp.) **Reviewed Date:** March 10, 2026 **What do you like best about Jenkins?** I like how Jenkins allows us to self-host, which saves us from paying for a third-party provider. I appreciate being able to configure very specific details on Jenkins, unlike other cloud CI providers. Jenkins offers a lot of customization, enabling us to set things up in-depth. The observability with Jenkins is great because it lets us know exactly what's happening, giving us more confidence in our systems. Additionally, Jenkins picks up changes from our GitHub and automatically runs the CI/CD pipeline, making deployment much easier. The initial setup was very straightforward and intuitive, which was helpful. **What do you dislike about Jenkins?** The UI is a little less intuitive. That's, like, we could definitely improve the UI portion of Jenkins. And the learning curve is certainly a bit steep because of, you know, how complex the UI can get. **What problems is Jenkins solving and how is that benefiting you?** I use Jenkins to automate deployments, so I don't manually handle everything. It pulls from GitHub and deploys to our cloud provider. We don't have to pay third-party fees, and we can configure specifics with deep insights for better observability. ### 14. Highly Flexible with Complex Setup **Rating:** 4.5/5.0 stars **Reviewed by:** Atharva P. | Cloud BI Engineer, Enterprise (> 1000 emp.) **Reviewed Date:** May 01, 2026 **What do you like best about Jenkins?** I like that Jenkins is highly flexible and extensive. It is an extensible CI/CD tool with a large plugin ecosystem, which is really helpful. I can customize it to fit almost any build and deployment workflow. The integrations with other tools like Docker, Kubernetes, SonarQube, Artifactory, and Terraform are really good and incredibly flexible. This level of integration allows me to automate infrastructure provisioning, store build artifacts, enable code quality checks, and manage workloads efficiently without needing to switch between multiple tools. **What do you dislike about Jenkins?** Setup and maintenance can be complex. The UI also feels outdated, and managing plugins or upgrades can sometimes cause stability issues. **What problems is Jenkins solving and how is that benefiting you?** Jenkins automates builds, tests, and deployment pipelines, reducing manual effort, ensuring consistent deployments, and speeding up release cycles. ### 15. Jenkins’ Flexibility and Plugin Ecosystem Make CI/CD Workflows Easy **Rating:** 5.0/5.0 stars **Reviewed by:** Chetan P. | System engineer, Mid-Market (51-1000 emp.) **Reviewed Date:** April 29, 2026 **What do you like best about Jenkins?** What stands out most about Jenkins is its flexibility and extensibility. With its huge plugin ecosystem, you can tailor it to almost any CI/CD workflow—build, test, deploy, and integrate with countless tools. **What do you dislike about Jenkins?** It can be hard to maintain—plugins break, dependencies conflict, and upgrades aren’t always smooth. The UI feels outdated and not very intuitive compared to newer CI/CD tools. **What problems is Jenkins solving and how is that benefiting you?** Jenkins solves the problem of manual, inconsistent software delivery by automating build, test, and deployment pipelines (CI/CD). ### 16. Unified Builds with Jenkins: Easy Navigation, Extensions, and Solid Support **Rating:** 4.5/5.0 stars **Reviewed by:** Moses L. | Director, Small-Business (50 or fewer emp.) **Reviewed Date:** April 24, 2026 **What do you like best about Jenkins?** Jenkins provides a unified way to build our code while providing access control, history and support for lots of extensions. The user interface is easy enough to navigate and there is plenty of online support. **What do you dislike about Jenkins?** It can be a bit resource intensive since it runs on Java **What problems is Jenkins solving and how is that benefiting you?** It allows us to build in a centralized location with the press of a button. Anyone on the team can create a build, or access built assets as needed. ### 17. On-Prem CI Standard: Huge Community, Easy to Setup and Maintain, Solid Docs, and Proven Pipelines **Rating:** 4.5/5.0 stars **Reviewed by:** Verified User in Information Technology and Services | Enterprise (> 1000 emp.) **Reviewed Date:** May 09, 2026 **What do you like best about Jenkins?** It's practically industry standard for an On-Prem installation. If you can run pipelines in the cloud, Jenkins might not be needed, but for those who need it on-prem or local - it's still th best with the biggest community and documentation. **What do you dislike about Jenkins?** Nothing that I really dislike, since I'm so used to it. However, the UI is a bit wonky in some scenarios, but nothing what experience will not overcome. **What problems is Jenkins solving and how is that benefiting you?** It allows my to automate my application build, test and deploy steps. Specifically for my requirements to build my apps with application security testing tool steps in between, it shows the workflow really nicely. ### 18. Flexible Hosting, Plugin-Friendly GUI, and Outstanding Community Support **Rating:** 4.5/5.0 stars **Reviewed by:** Sanket O. | SDET, Computer Software, Mid-Market (51-1000 emp.) **Reviewed Date:** March 23, 2026 **What do you like best about Jenkins?** I like its GUI, the flexibility to host it on our local servers or somewhere in the cloud, the strong support for plugins, and the crazy level of community support. **What do you dislike about Jenkins?** There are other options, such as Harness, which I think are better because the UI feels more advanced and modern, and it offers good integration with AWS, Azure, and other services. **What problems is Jenkins solving and how is that benefiting you?** Jenkins helps us orchestrate the different stages of our deployment process, including compiling, building, testing, and deploying. ### 19. Easy Setup with Versatile Job Management **Rating:** 4.0/5.0 stars **Reviewed by:** Verified User in Media Production | Small-Business (50 or fewer emp.) **Reviewed Date:** February 04, 2026 **What do you like best about Jenkins?** I find Jenkins very easy to use. I can manage a lot of jobs and categorize them into folders, which is super helpful. It supports a lot of languages and parameters, making it really versatile. Additionally, the initial setup was very easy, and there's a lot of online documentation available, which makes it very convenient to get started. **What do you dislike about Jenkins?** I feel that if I have a few jobs that are connected to each other and if I want to trigger one job from another, I can't do it from Jenkins. So it can be improved in terms of managing ETL processes and pipelines. **What problems is Jenkins solving and how is that benefiting you?** I use Jenkins to manage pipeline and jobs for my ETL product. It handles job scheduling, which Pentaho lacks. Jenkins is easy to use, supports multiple languages and parameters, and lets me organize jobs into categories. ### 20. Extensible and Flexible CI/CD Powerhouse with a Huge Plugin Ecosystem **Rating:** 4.0/5.0 stars **Reviewed by:** Manish K. | Managerial, Mid-Market (51-1000 emp.) **Reviewed Date:** April 29, 2026 **What do you like best about Jenkins?** What I like best about Jenkins is its extensibility and flexibility. With a vast plugin ecosystem, it integrates seamlessly into any CI/CD pipeline and supports virtually any toolchain or workflow. **What do you dislike about Jenkins?** What I dislike about Jenkins is its dated UI and steep learning curve. Managing plugins and maintaining stability can become complex, especially in large-scale or poorly governed environments. **What problems is Jenkins solving and how is that benefiting you?** Jenkins solves the problem of manual, error-prone build and deployment processes by automating CI/CD pipelines. This enables faster releases, consistent builds, early bug detection, and improved developer productivity. ### 21. Reliable CI Automation with a Huge Plugin Ecosystem **Rating:** 4.5/5.0 stars **Reviewed by:** Sandeep R. | Linux Administrator, Mid-Market (51-1000 emp.) **Reviewed Date:** January 14, 2026 **What do you like best about Jenkins?** Jenkins is very reliable for continuous integration and build automation. It has a huge plugin ecosystem and integrates easily with Git, cloud service, and DevOps tools. Once set up, it saves a lot of time by automating repetitive tasks. **What do you dislike about Jenkins?** Initial setup and configuration can be complex, especially for beginners. Managing plugins and upgrades some causes compatibility issues, and the UI feels outdated compared to modern CI/CD tools. **What problems is Jenkins solving and how is that benefiting you?** Jenkins automates builds, tests, and deployments, reducing manual effort and error. It helps catch issues early in the development cycle and speeds up delivery with consistent and repeatable pipelines. ### 22. Reliable automation tool that simplifies CI/CD **Rating:** 5.0/5.0 stars **Reviewed by:** Kirti T. | Assosciate Engineer, Small-Business (50 or fewer emp.) **Reviewed Date:** September 19, 2025 **What do you like best about Jenkins?** Jenkins has been a game changer for me in automating builds and deploments. I no longer have to manually trigger jobs or keep track of different stages-- the pipelines handle everything. What I like the most is how customizable it is with pluginsm and the fact that it workds well with almost any tool i use. it has helped me save a lot of time and reduced mistakes in the release process because i could test in different environments before giving it for release. it is easy to use and implement the desired deployments. it is a tool that i use very frequently in my daily work. i recommend it to anyone with similar needs to mine. **What do you dislike about Jenkins?** nothing really. it has been reliable and does exactly what i need. **What problems is Jenkins solving and how is that benefiting you?** Jenkins is helping me automate the entire CI/CD process, from code integration to deployment. Earlier i used to spend a lot of time manually running building in my local and deployments, which often led to delays and errors. With jenkins, everything is streamlines, run automatically, tests are triggered instantly and deployments are much faster. This has saved me a lot of time, reduced manual and integration errors, and made releases more consistant and reliable. ### 23. Seamless Integration, Outdated UI **Rating:** 4.5/5.0 stars **Reviewed by:** Srikar V. | DevOps Engineer, Enterprise (> 1000 emp.) **Reviewed Date:** November 27, 2025 **What do you like best about Jenkins?** I love how Jenkins allows me to build automated pipelines for triggering build-test-deploy cycles effortlessly, significantly reducing the need for manual deployments and the triggering of automation suites. I appreciate Jenkins for its seamless integration with most available languages, ensuring I don't encounter compatibility issues regardless of whether my projects use Java, Python, or any other language — it fits smoothly into my workflow. The simplicity of Jenkins' code for building pipelines and utilizing cron expressions to trigger time-based pipelines enhances efficiency and flexibility in my operations, making Jenkins incredibly valuable. Additionally, Jenkins works exceptionally well in conjunction with Git and Bitbucket for source code management, Maven for building projects, and Selenium for conducting automated test cases, combining to create a streamlined and cohesive development environment. **What do you dislike about Jenkins?** I find that the user interface of Jenkins is outdated and navigating through job configurations or plugin settings can be confusing, especially when dealing with large pipelines or multiple jobs. Additionally, Jenkins' reliance on plugins, while powerful, can be risky as it poses dependency issues and lacks built-in native support. **What problems is Jenkins solving and how is that benefiting you?** I use Jenkins to automate build, test, and deploy cycles, eliminating the need for manual deployment and ensuring seamless integration across multiple languages. ### 24. Jenkins Shines with Extensive Plugins, Flexible Pipelines, and Horizontal Scaling **Rating:** 4.5/5.0 stars **Reviewed by:** Subrajit B. | Deputy Manager, Information Technology and Services, Enterprise (> 1000 emp.) **Reviewed Date:** January 21, 2026 **What do you like best about Jenkins?** Some points I do like About Jenkins. 1.Extensive Plugins it provides. 2.Support of Declarative and scripted pipelines . 3.It's Horizontal scaling mechanism . **What do you dislike about Jenkins?** Some pain points of Jenkins is . 1. Setup and maintenance as frequent plugin update required . 2.It's User Interface is outdated . 3.There might be chances of vulnerabilities due to it's plugin model and open source in nature **What problems is Jenkins solving and how is that benefiting you?** Automates builds, tests, and deployments through CI/CD pipelines. Faster release cycles, fewer human errors, and consistent delivery across environments. Seamless workflows across version control, testing, monitoring, and deployment platforms. velopers fix issues early, reducing rework and improving overall code quality. ### 25. One-Click CI/CD Pipelines That Make Deployments Easy **Rating:** 5.0/5.0 stars **Reviewed by:** Vishnu P. | Cloud Engineer, Computer Software, Enterprise (> 1000 emp.) **Reviewed Date:** January 14, 2026 **What do you like best about Jenkins?** What I like about the jenkins is its pipeline workflow, like with a single click, completed CICD flow work for deployments. **What do you dislike about Jenkins?** As of now i dont find any issue in jenkins juts only its timeout issue for nodes. **What problems is Jenkins solving and how is that benefiting you?** My biggest problem was that I needed to do the deployment manually for my environment. Now I created the job which does it with one click ### 26. Flexible CI/CD Pipelines with Strong Plugin Support **Rating:** 4.5/5.0 stars **Reviewed by:** Adarsh K. | Software Engineer, Small-Business (50 or fewer emp.) **Reviewed Date:** February 18, 2026 **What do you like best about Jenkins?** it is very flexible for building CI/CD pipeline and support a large number of plugins different tools and environment pipeline as code support makes east to maintain version controlled workflow **What do you dislike about Jenkins?** It's feel outdated and initial configuration may be complex for new users. sometimes plugins and dependency require manual maintenance **What problems is Jenkins solving and how is that benefiting you?** it automates our build and deployment process which leads to reduce manually effort and minimising human error during releases. it also help maintain consistent CI/CD workflow across environment and improve release reliability ### 27. Grandfather of CI/CD **Rating:** 4.0/5.0 stars **Reviewed by:** Mitul C. | Software Engineer, Enterprise (> 1000 emp.) **Reviewed Date:** January 19, 2026 **What do you like best about Jenkins?** plug in system, since it is one of the founding instances of ci/cd the plugin ecosystem is very vast and helpful. this makes the platform highly flexible as well. **What do you dislike about Jenkins?** the user interface is very very old, UI needs massive re-work. it required more maintenance than its competitors like gitlab **What problems is Jenkins solving and how is that benefiting you?** removed the problem of manual builds/tests/ deployments ### 28. Jenkins: Reliable CI/CD Automation with Broad Tool Integration **Rating:** 4.5/5.0 stars **Reviewed by:** Verified User in Information Technology and Services | Enterprise (> 1000 emp.) **Reviewed Date:** January 14, 2026 **What do you like best about Jenkins?** Jenkins is the most popular and most widely used tool automating builds and deployments in CI / CD pipelines. Offers extensive customisation via plugins and proivdes seamless. integration. Jenkins works really well by integrating with various source code management system like Git, Bitbucket, Gerrit, Maven for building projects, and Selenium for running automated test cases. Jenkins helps to build a reliable continuous integration and continuous deployment pipeline. **What do you dislike about Jenkins?** Jenkins UI is seems out to date. With adding several plugins, Jenkins consume lot of memory. **What problems is Jenkins solving and how is that benefiting you?** Jenkins is helping us for build automation ### 29. Jenkins Customization and Plugin Ecosystem Make Integration Easy **Rating:** 4.5/5.0 stars **Reviewed by:** Dipika U. | Software Developer, Enterprise (> 1000 emp.) **Reviewed Date:** March 31, 2026 **What do you like best about Jenkins?** Customization and plugins that Jenkins provide for integration. **What do you dislike about Jenkins?** Maintainence and sometimes there's a compatibilty issues and works slows due touse of too many plugins. **What problems is Jenkins solving and how is that benefiting you?** Solves a huge problem of scheduler and build issues where we get timely installation and execution of pipelines regardless of time and person's availibility. ### 30. Automation Made Easy with Powerful Integrations and Monitoring **Rating:** 5.0/5.0 stars **Reviewed by:** Rinu L. | DevOps Engineer, Mid-Market (51-1000 emp.) **Reviewed Date:** December 19, 2025 **What do you like best about Jenkins?** Automation & CI/CD Extensibility with Plugins Easy Integration Visualization & Monitoring **What do you dislike about Jenkins?** Jenkins can consume a lot of memory, especially when start adding multiple plugins or scaling with many jobs **What problems is Jenkins solving and how is that benefiting you?** Jenkins solves the problem of manual and repetitive tasks in software development by automating builds, tests, and deployment. It provides faster feedback and ensures consistent quality and collaboration across teams. ### 31. Infinitely Customisable Test Orchestration **Rating:** 4.5/5.0 stars **Reviewed by:** Verified User in Information Technology and Services | Enterprise (> 1000 emp.) **Reviewed Date:** August 24, 2025 **What do you like best about Jenkins?** Jenkins Pipeline scripts let me define our entire Android test flow as code - from building APKs to running Espresso tests across multiple devices. The Blue Ocean UI actually makes sense compared to the old interface. Parallel execution cuts our regression suite from 3 hours to 45 minutes. Slack notifications immediately alert us when builds fail, and the build history helps track down which commit broke things. **What do you dislike about Jenkins?** Plugin compatibility is a nightmare - updating one breaks three others. The workspace gets corrupted randomly and needs manual cleanup. Configuration through UI is tedious. **What problems is Jenkins solving and how is that benefiting you?** We push code multiple times daily, and Jenkins automates our entire mobile testing pipeline. It runs our unit tests, UI automation suite, and generates APKs for different environments automatically. The real win is catching bugs before they hit staging - last week it flagged a crasher in our cart module at 2 AM. My team doesn't have to manually trigger builds anymore, which freed up hours for actual test development. ### 32. Great Pipeline Visualization and Control, but Limited IaC Automation and Testing **Rating:** 3.5/5.0 stars **Reviewed by:** Verified User in Computer Software | Mid-Market (51-1000 emp.) **Reviewed Date:** February 17, 2026 **What do you like best about Jenkins?** The visualization of the pipelines and ability to control the script; the additional plugins **What do you dislike about Jenkins?** The JCASC and support of IaC management is limited. That is in terms of upgrading or installing plugins or versions it is not easily automated via Terraform, JSCASC, kubernetes. Support for playgrounds and testing is also limited. Nodes can cause bottlenecks **What problems is Jenkins solving and how is that benefiting you?** Pipeline orchestration for multibranch projects ### 33. Unmatched Flexibility and Plugin Power for CI/CD **Rating:** 4.0/5.0 stars **Reviewed by:** chetan V. | System Analyst, Enterprise (> 1000 emp.) **Reviewed Date:** December 16, 2025 **What do you like best about Jenkins?** What I appreciate most about Jenkins is its flexibility and the vast plugin ecosystem it offers. With Jenkins, I can create custom CI/CD pipelines that are compatible with nearly any environment. **What do you dislike about Jenkins?** I find Jenkins frustrating due to its high maintenance requirements and the complexity involved in its configuration. Handling plugins, performing upgrades, and scaling the system often turn into time-consuming tasks. **What problems is Jenkins solving and how is that benefiting you?** Jenkins solves automated build, test, and deployment problems. It benefits me by catching issues early, speeding up releases, and reducing manual work. ### 34. Great Open-Source CI Tool That Simplifies Automation **Rating:** 5.0/5.0 stars **Reviewed by:** Lokesh T. | Sr. Security Engineer, Small-Business (50 or fewer emp.) **Reviewed Date:** October 17, 2025 **What do you like best about Jenkins?** This is open-source CI platform where every one can make us of it. And its a popular CI tool, where it made my Automation easy **What do you dislike about Jenkins?** Since it is a Open source, we need to open source community if we are facing any challenges **What problems is Jenkins solving and how is that benefiting you?** It is a Platform to where every stage in SDLC will be aligned as a pipeline. This is more to build DevOps platform ### 35. Making CI/CD Effortless: Jenkins Streamlines Delivery 🫡 **Rating:** 4.5/5.0 stars **Reviewed by:** Aman Kumar M. | Senior Software Engineer (Data) , Information Technology and Services, Enterprise (> 1000 emp.) **Reviewed Date:** August 07, 2025 **What do you like best about Jenkins?** Jenkins offers unmatched flexibility and extensibility, allowing us to automate builds, tests, and deployments across all environments. Its vast ecosystem of plugins lets us integrate with countless tools, while pipelines as code deliver transparency and control for CI/CD processes & The ability to scale with distributed agents means Jenkins meets the needs of single projects and enterprise setups alike. **What do you dislike about Jenkins?** It can be complex to set up and manage, especially for newcomers. Customizing pipelines and plugins may require deep technical expertise. The web UI is functional but dated, and administration sometimes proves time-consuming. However, its robust community often makes up for these hurdles.. **What problems is Jenkins solving and how is that benefiting you?** Jenkins automates the entire software delivery cycle—building, testing, and deploying—reducing manual tasks and errors. It enables quick feedback, faster releases, and increased code quality, making our DevOps processes reliable and scalable ### 36. Jenkins: My Go-To for Practicing CI/CD Integration **Rating:** 3.5/5.0 stars **Reviewed by:** Prabhakar D. | Sr. Associate, Computer Software, Mid-Market (51-1000 emp.) **Reviewed Date:** January 20, 2026 **What do you like best about Jenkins?** Jenkins is my first choice when I want to practice CI/CD integration for an application. **What do you dislike about Jenkins?** There are a lot of plug-ins, which makes it confusing to understand its exact purpose. **What problems is Jenkins solving and how is that benefiting you?** It helps with automated application delivery by streamlining the build, test, and deploy process. ### 37. probably the best Devops automation tool **Rating:** 4.5/5.0 stars **Reviewed by:** Nashit H. | Mentor/Faculty cum Developer, Education Management, Small-Business (50 or fewer emp.) **Reviewed Date:** October 09, 2025 **What do you like best about Jenkins?** Seamless integration with most of the tools like Git,Docker, Maven builds, and all. Plugins are great. Implementation is easy and user centric. **What do you dislike about Jenkins?** Scalability is a challenge, besides the not so-friendly dashboard (unlike GitLab CI/CD) is another challenge. **What problems is Jenkins solving and how is that benefiting you?** The complete CI-CD pipeline. Continuous builds, tests and deployment, helped me launch multiple versions of my application. ### 38. Easy CI/CD Setup, But UI Needs Improvement **Rating:** 3.5/5.0 stars **Reviewed by:** Verified User in Computer Software | Mid-Market (51-1000 emp.) **Reviewed Date:** December 15, 2025 **What do you like best about Jenkins?** Jenkins is free to use and simple to deploy. Its capability to define the CI/CD process within a Jenkinsfile, along with version control for application code, makes creating builds straightforward and facilitates easy deployment. **What do you dislike about Jenkins?** The default Jenkins UI feels rather confusing and outdated. At times, working with Jenkins files in Groovy script can also become quite complex. **What problems is Jenkins solving and how is that benefiting you?** By automating the delivery pipeline from code commit through to deployment, the release process has become much more predictable, consistent, and efficient. This automation ensures that each release follows the same steps, resulting in faster and more reliable deployments. ### 39. Flexible CI/CD Automation with Seamless Integrations **Rating:** 5.0/5.0 stars **Reviewed by:** Shreya Z. | Quality Assurance Analyst, Small-Business (50 or fewer emp.) **Reviewed Date:** December 13, 2025 **What do you like best about Jenkins?** Flexible to set th automation for CICD pipeline in the way we want.east to integrate the other tools like GitHub, docker and koobernets. **What do you dislike about Jenkins?** As per my self there is nothing to dislike **What problems is Jenkins solving and how is that benefiting you?** Automatic the deployment process of the software after commit by developer including the creating build ,running automation test cases, deployment of staging/production ### 40. Best open source integration tool **Rating:** 3.5/5.0 stars **Reviewed by:** Jaideep S. | ITDP Intern - Technical Product Manager, Enterprise (> 1000 emp.) **Reviewed Date:** April 23, 2025 **What do you like best about Jenkins?** Jenkins is open source and implementing it in our ecosystem does not cost much. It supports multiple plugins as per our requirements and it very customizable. **What do you dislike about Jenkins?** The initial setup takes up a lot of time and effort. There will be cases when we would have to manually debug pipelines and resolve issues. This can slow down the speed of deployment cycles. Hence, a dedicated team is necessary for this. **What problems is Jenkins solving and how is that benefiting you?** Jenkins is open source so it does not cost a lot to the organization. It integrates with many applications such as GitHub, BitBucket, Jira, Bamboo and others. These integrations are very helpful for a developer. It also integrates with Sonar, SonarQube which helps in testing. Jenkins has a clean and easy to use UI with a dedicated section to download plugins as per our own requirements. ### 41. Powerful automation for continuous integration **Rating:** 4.0/5.0 stars **Reviewed by:** Verified User in Retail | Enterprise (> 1000 emp.) **Reviewed Date:** September 30, 2025 **What do you like best about Jenkins?** Jenkins is flexible and has extensive plugin ecosystem, which allow seamless integration with almost any tool in the development pipeline. **What do you dislike about Jenkins?** Learning curve for jenkins is steep. Managing plugins can sometimes lead to compatibility issues. **What problems is Jenkins solving and how is that benefiting you?** Jenkins solves the challenge of automating build, test and deployment process, which reduces manual effort and human error. ### 42. Bulk removal of listings **Rating:** 5.0/5.0 stars **Reviewed by:** Sushmitha A. | Marketplace trust associate, Mid-Market (51-1000 emp.) **Reviewed Date:** December 25, 2024 **What do you like best about Jenkins?** Jenkins gives hand for searching the missing listings when the user reaches out; bulk removal of the lists; helps to integrate the data in an ease manner. They also have colour indications to signify us whether the takedown is done or it's somewhere in the middle. It has only very few datas to fill before runing it which eats a very low time. Thus it is a very good application. **What do you dislike about Jenkins?** It takes a bit more time while taking down the listings but still that is fine and it got stuck 2 times while running the jenkins and I have to add the details again to run it. Apart from that it is a good application. **What problems is Jenkins solving and how is that benefiting you?** It helps to takedown the counterfeit listings in bulk with the essential information. When the luxury brand reach out to us, we use jenkins to takedown the products. We handle the client's queries on hidden listings which we cannot see in the admin page. It will not eat up the time like other apps asking for much data. It has many filterations which could be very useful in drawing the data. It also has seperate hypes for whole listing removal and also for a particular picture removal of a whole listing. Friendly to navigate and and very much supporting. ### 43. Light but out-of-date **Rating:** 4.0/5.0 stars **Reviewed by:** Matias A. | Quality Senior Engineer., Mid-Market (51-1000 emp.) **Reviewed Date:** September 16, 2025 **What do you like best about Jenkins?** Lot of Plugins available Lightness of the tool **What do you dislike about Jenkins?** User interface could be more attractive and user friendly. The configuration could be more simple and visual. **What problems is Jenkins solving and how is that benefiting you?** We have integrated the schedule for test automation executions. It also trigger notifications where it is set (slack, email, etc) and is available to be integrated with reporting tools like Allure report. ### 44. Jenkins review **Rating:** 4.5/5.0 stars **Reviewed by:** Grant W. | Senior Cloud Engineer, Mid-Market (51-1000 emp.) **Reviewed Date:** March 22, 2017 **What do you like best about Jenkins?** I like the way that jenkins integrates with a lot of external systems. we also like It is a server-based system running in a servlet container like the Apache Tomcat. It offers support for SCM platforms and solutions like AccuRev, CVS, Subversion, Git, Mercurial, Perforce, Clearcase and RTC, and can implement Apache Ant and Apache Maven-based projects. Jenkins can also execute arbitrary shell scripts and Windows batch commands. **What do you dislike about Jenkins?** I do not like how it is configurable, seems to be about 20 years out of date. **Recommendations to others considering Jenkins:** I would recommend Jenkins to anyone who is looking for a continuous integration tool that delivers continuous integration services for software development. **What problems is Jenkins solving and how is that benefiting you?** We use jenkins as a continuous integration tool that delivers continuous integration services for software development. ### 45. Fetarue of Jenkins **Rating:** 4.5/5.0 stars **Reviewed by:** rahul l. | software devloper, Small-Business (50 or fewer emp.) **Reviewed Date:** September 17, 2025 **What do you like best about Jenkins?** Full control and change the settings according to your requirements **What do you dislike about Jenkins?** Need more extra tools for the best action. **What problems is Jenkins solving and how is that benefiting you?** this use for CICD. when code commit it will check and deplyed in the server ### 46. Best tool for setting up CI/CD pipeline **Rating:** 4.0/5.0 stars **Reviewed by:** Verified User in Information Technology and Services | Enterprise (> 1000 emp.) **Reviewed Date:** January 29, 2025 **What do you like best about Jenkins?** The best thing about it is that it gives a test report that gets generated after the test execution on jenkins server which can be shared to anyone via link. The other best thing I like is that you can paramerize the jenkins job accordingly to make it more dynamic which gets overidden during run time. **What do you dislike about Jenkins?** The UI interface can be improved more and it's been long since the UI interface is not changed so it needs to get improved. **What problems is Jenkins solving and how is that benefiting you?** This tool is helping me to build automation reports. I am using cucumber plugin which helps me to generate the cucumber report after every test job execution and also it is helping to set the new machine agent into jenkins server to setup the automation of desktop automation, frontend and backend automation. ### 47. Best for Automation **Rating:** 5.0/5.0 stars **Reviewed by:** Verified User in Information Technology and Services | Enterprise (> 1000 emp.) **Reviewed Date:** March 01, 2025 **What do you like best about Jenkins?** 1. We can automate mostly all workflows through it. Be it programming or shell script. 2. We have been using it for creating our builds (artefacts) and production deployment. 3. It's master/slave feature for makes it easy to scale as we trigger more jobs. **What do you dislike about Jenkins?** A lot of plugins needs to be updated at regular intervals. **What problems is Jenkins solving and how is that benefiting you?** 1. With Jenkins our Ops team is able to deploy the new build with fewer pipelines. 2. As our product deployment has downtime window so we need to deploy it within that window so with Jenkins we are making sure to complete job within the timeframe. ### 48. Best CICD tool **Rating:** 5.0/5.0 stars **Reviewed by:** Subrat M. | Senior DevOps Engineer, Enterprise (> 1000 emp.) **Reviewed Date:** May 16, 2025 **What do you like best about Jenkins?** It is mostly used worldwide CICD tool. It give many features and compatibility with other platforms just by adding a plugin for the same plat form available in marketplace. **What do you dislike about Jenkins?** It needs restart after a small change related to jenkins. **What problems is Jenkins solving and how is that benefiting you?** It is open source and it is faster than any other CI tool in the market. ### 49. Jenkins Review: Simplifying Automation and Integration **Rating:** 5.0/5.0 stars **Reviewed by:** Dr habeeb M. | Data scientist, Mid-Market (51-1000 emp.) **Reviewed Date:** August 11, 2024 **What do you like best about Jenkins?** Jenkins is a great tool in the discipline of continuous integration and continuous delivery. It is flexible and scalable. What I like the most about Jenkins is its huge plugin ecosystem, which allows for seamless integration with various tools and platforms. This makes it very adjustable to different development environments and workflows. **What do you dislike about Jenkins?** Though Jenkins is definitely a useful and adaptable tool, there are some parts that I find problematic. Its high level of complexity in installation and configuration is the most significant disadvantage. The newbies might be confused by numerous options and plug-ins that are available in Jenkins. **What problems is Jenkins solving and how is that benefiting you?** Jenkins has played a very important role in solving several crucial challenges that are present in our SDLC mainly in the aspects of CI/CD. All of it was manual before Jenkins and we used to have many times human errors because the build and deployment was done manually, hence the release delay and an irregular build quality. Jenkins has changed this a lot by actually automating the chain and code integration and deployment. ### 50. Unleash the power of automation with Jenkins CICD **Rating:** 4.5/5.0 stars **Reviewed by:** Akhil G. | DevOps Engineer, Enterprise (> 1000 emp.) **Reviewed Date:** December 23, 2024 **What do you like best about Jenkins?** Jenkins supports large number of plugins, that is helpful in performing various automation and easy integration **What do you dislike about Jenkins?** I am using Jenkins frim long back, overall application is perfect for the use cases. UI can be improved little bit. **What problems is Jenkins solving and how is that benefiting you?** We have integrated our git repository with the Jenkins. Whenever our developers do make any changes in the application code, a new docker image of that application gets created. Additionally it get pushed to docker repository. Which can be used later for the deployment purpose. ## 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?section=pricing&secure%5Bexpires_at%5D=2026-06-03+21%3A26%3A09+-0500&secure%5Bsession_id%5D=3a352eb1-625c-42da-8c22-1bad9c52d2a0&secure%5Btoken%5D=614960ca174c00d03de2867668a8d5fc1987b0b431ec54737a092f62cece22c1&format=llm_user) ## Jenkins Integrations - [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) - [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,293 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)