Jenkins is a powerful tool, but it can be challenging to set up and maintain, especially as the plugin ecosystem grows. As you add more plugins, compatibility problems can come up, and upgrades along with pipeline management often take significant effort. The user interface also feels dated compared to newer CI/CD platforms. A more modern UI and easier, more streamlined maintenance would greatly improve the overall experience. Review collected by and hosted on G2.com.

Jenkins is highly capable, but maintaining it can become more challenging over time. Managing plugins, dealing with version compatibility, and keeping pipelines up to date often require continuous administrative effort. The interface also feels less modern than many newer CI/CD platforms, and the initial setup can come with a steep learning curve for new users. 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.

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.

I particularly like the recent Jenkins AI-assisted pipeline features and ecosystem improvements, which make creating and troubleshooting pipeline configurations much easier. The enhanced pipeline visualization provides better insight into complex CI/CD workflows, helping identify bottlenecks and failed stages more quickly. I've also found the improved Kubernetes and cloud-native integrations valuable, as they make it easier to spin up ephemeral build agents, improve scalability, and optimize resource usage for large automation workloads. Review collected by and hosted on G2.com.

Plugin compatibility is a nightmare - updating one breaks three others. The workspace gets corrupted randomly and needs manual cleanup. Configuration through UI is tedious. 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.

In my opinion, this is the best open-source tool for creating and running CI/CD pipelines. Review collected by and hosted on G2.com.

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

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

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