Jenkins has been a reliable CI/CD tool since I first learned it while studying programming and microservices seven years ago, and returning to it across several projects since has reinforced how flexible and extensible it is. Being open-source with a massive plugin ecosystem has made it adaptable to nearly any tech stack or workflow, whether that's simple build automation or more complex multi-stage deployment pipelines. Pipeline-as-code through Jenkinsfiles has made version-controlling the entire CI/CD process straightforward, keeping build logic alongside the actual codebase rather than living in a separate system. The community support and documentation, built up over years of widespread adoption, means troubleshooting rarely takes long since most issues have already been discussed somewhere. Review collected by and hosted on G2.com.

The interface feels dated compared to more modern CI/CD tools, and navigating plugin configurations can get cluttered as a project's pipeline complexity grows. Managing and updating plugins over time requires ongoing maintenance, since compatibility issues between plugins occasionally surface after updates. Setting up more advanced pipelines still requires a fair amount of Groovy scripting knowledge, which adds a learning curve for team members newer to Jenkins specifically. Self-hosting means taking on infrastructure maintenance responsibility that some newer, managed CI/CD platforms have abstracted away entirely. Review collected by and hosted on G2.com.

I like Jenkins because it helps automate our CI/CD pipeline. It builds the code automatically, runs tests, and integrates with tools like Git and SonarQube to give fast feedback. As a result, it cuts down on manual work, improves consistency across our process, and helps us deliver reliable software more efficiently. Review collected by and hosted on G2.com.

One thing I don’t like is that Jenkins requires ongoing maintenance, especially when it comes to managing plugins and handling upgrades. Setting up and maintaining complex pipeline configurations can also be time-consuming. Still, overall, its flexibility and automation capabilities make it a very valuable CI/CD tool. Review collected by and hosted on G2.com.

I like Jenkins because it automates the CI/CD process, reduces manual deployment work, and helps make builds and deployments more consistent. It also integrates well with GitHub and supports flexible pipelines for different environments. Review collected by and hosted on G2.com.

Jenkins can be difficult to configure and maintain, especially when managing plugins, credentials, and complex pipelines. The UI also feels outdated, and troubleshooting failed builds can sometimes take a lot of time. Review collected by and hosted on G2.com.

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. Review collected by and hosted on G2.com.

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. Review collected by and hosted on G2.com.

Jenkins stands out for its flexibility, extensive plugin ecosystem, and open-source nature. It can be deployed on a dedicated server or as containerized microservices, making it suitable for organizations of different sizes. We use it to automate CI/CD pipelines and integrate seamlessly with Git repositories, Docker, Kubernetes, AWS services, and notification tools like Slack. The large plugin library allows us to customize pipelines based on project requirements, reducing manual effort and accelerating software delivery. Although the UI feels dated compared to newer CI/CD platforms, its stability, scalability, and strong community support make it a highly cost-effective solution with excellent ROI for automating development and deployment workflows. Review collected by and hosted on G2.com.

User management has always felt a bit messy in Jenkins, and access management isn’t much better. When I’m setting up a pipeline and choosing those mini boxes, it becomes really hard to manage who can do what, and the whole process ends up feeling confusing. Review collected by and hosted on G2.com.

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. Review collected by and hosted on G2.com.

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. Review collected by and hosted on G2.com.

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. Review collected by and hosted on G2.com.

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. Review collected by and hosted on G2.com.

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. Review collected by and hosted on G2.com.

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. Review collected by and hosted on G2.com.

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. Review collected by and hosted on G2.com.

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. Review collected by and hosted on G2.com.

I really like the latest code-based pipeline management. It’s genuinely easy to maintain, and it makes tracking everything much simpler. Review collected by and hosted on G2.com.

One thing I’ve noticed is that I don’t think Jenkins supports copying artifacts when a job is aborted. I tried multiple approaches, but it still didn’t work for me. Review collected by and hosted on G2.com.