Try our new research platform with insights from 80,000+ expert users

Incredibuild vs Jenkins comparison

 

Comparison Buyer's Guide

Executive Summary

Review summaries and opinions

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Categories and Ranking

Incredibuild
Ranking in Build Automation
25th
Average Rating
8.0
Reviews Sentiment
5.1
Number of Reviews
1
Ranking in other categories
No ranking in other categories
Jenkins
Ranking in Build Automation
4th
Average Rating
8.0
Reviews Sentiment
7.0
Number of Reviews
92
Ranking in other categories
No ranking in other categories
 

Mindshare comparison

As of September 2025, in the Build Automation category, the mindshare of Incredibuild is 1.0%, up from 0.7% compared to the previous year. The mindshare of Jenkins is 9.1%, down from 11.8% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Build Automation Market Share Distribution
ProductMarket Share (%)
Jenkins9.1%
Incredibuild1.0%
Other89.9%
Build Automation
 

Featured Reviews

ZM
Saves time for developers, which saves money for the company
We are using the Incredibuild agent to run multiple processes on all available cores. This is the improvement that we did. Instead of the machine's core doing task after task, it is now running on multiple machines. In my working environment, it is saving time for all our developers in regards to the time consumption of the builds. My team has four people who manage and interact with Incredibuild as a product.
Annamalai Pts - PeerSpot reviewer
Streamlined CI/CD pipelines with powerful integration and an easy setup
I use Jenkins as a CI/CD tool. We create pipelines using Jenkins, with stages for Maven builds, Docker image builds, SonarQube integration, and deploying the image to a Kubernetes cluster, AWS EKS Jenkins has made the developers' work very easy. They commit to the remote repository, and…

Quotes from Members

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Pros

"It is saving time for developers, which is saving money for the company."
"The most valuable feature of Jenkins is its open source."
"Jenkins is the most widely used development tool, so there are many plugins and it's easy to integrate. There is a large user base to provide community support, which I find very valuable. If I need to find a better way to do something, I can always get help from the community. Automation is about thinking outside of the box, and other users are constantly adding new plugins."
"The auto-schedule feature is valuable. Another valuable feature is that Jenkins does not trigger a build when there is no change in any of the systems. Jenkins also supports most of the open-source plug-ins."
"Jenkins's automation and orchestration features have significantly improved workflows by automating various processes. Initially, it did not support YAML manifesting or GitOps, but recent versions have introduced these capabilities. Now, the tool supports importing manifest files from Git repositories, enabling the implementation of GitOps pipelines. Compared to other tools like GitLab, it has become a mature tool for running CI/CD pipelines."
"Jenkins is very customizable."
"Also, the ability to customize these plugins is valuable. Its user-friendliness stands out, especially in its user interface which allows easy installation and configuration."
"This solution has helped us in automating the build and test process, reducing time."
"Automation of chores like deployment, frequent manual tasks (like running scripts on test and production systems) reduced the time used and the number of errors made by engineers, freeing them to do meaningful work instead."
 

Cons

"Stability could be improved. I don't know the reason for the instability because there are no logs that help me to understand the problem."
"It would be better if there were an option to remove its Java dependency. This would make it more compatible with other software, and it could be much better. At present, we have to depend on Java whenever we want to deploy agents."
"Creating a new SonarQube project requires a separate job, and we've encountered some integration issues with Docker and the need for better vulnerability checks."
"Jenkins could improve the integration with other platforms."
"UI is quite outdated."
"Sometimes you have Jenkins restarting because of OOM errors."
"Some kind of SaaS product would be helpful in providing organizational structure."
"The bug fix speed is very slow."
"Centralized user management would be helpful."
 

Pricing and Cost Advice

"Its pricing and licensing are annoying. Every year, I need to renew. If I miss the deadline date, all my processes will stop working. So, I would prefer that I wouldn't need to renew every year, instead have another solution for it. Or, if we could have an enterprise license agreement with the company, then the development team wouldn't need to spend time renewing licenses."
"Jenkins is open source and free."
"We are using the free version of Jenkins. There is not a license required to use the solution because it is open-source."
"In our company, we do pay for the licensing of the solution."
"We use the tool's open-source version which is free. There is an enterprise version which is expensive but comes with better support."
"It could be cheaper because there are many solutions available in the market. We are paying yearly."
"Jenkins is a free solution, it is open source."
"The solution is one of the lowest costs compared to competitors."
"This is an open-source solution for the basic features. However, if an organization wishes to include specific functionality, outside of the basic package, there are extra costs involved."
report
Use our free recommendation engine to learn which Build Automation solutions are best for your needs.
867,445 professionals have used our research since 2012.
 

Comparison Review

it_user184734 - PeerSpot reviewer
Jan 22, 2015
I generally find TeamCity a lot more intuitive than Jenkins.
Moving to TeamCity from Jenkins At work, we’re slowly migrating from Jenkins to TeamCity in the hope of ending some of our recurring problems with continuous integration. My use of Jenkins prior to this job has been almost strictly on a personal basis, although I pretty much only use Travis…
 

Top Industries

By visitors reading reviews
Financial Services Firm
18%
Computer Software Company
16%
Manufacturing Company
11%
Retailer
7%
Financial Services Firm
21%
Computer Software Company
13%
Manufacturing Company
13%
Government
7%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
No data available
By reviewers
Company SizeCount
Small Business28
Midsize Enterprise15
Large Enterprise56
 

Questions from the Community

Ask a question
Earn 20 points
How does Tekton compare with Jenkins?
When you are evaluating tools for automating your own GitOps-based CI/CD workflow, it is important to keep your requirements and use cases in mind. Tekton deployment is complex and it is not very e...
What do you like most about Jenkins?
Jenkins has been instrumental in automating our build and deployment processes.
What is your experience regarding pricing and costs for Jenkins?
Jenkins is used in many companies to save money, especially within R&D divisions, by avoiding the expenses of proprietary tools.
 

Comparisons

 

Overview

 

Sample Customers

Over 2,000 companies worldwide across industries inluding Epic Games, Microsoft, Playstation, Nintendo, Samsung, GM, Intel, CitiGroup, Qualcomm, Boeing, Motorola, Qt, and more accelerate their development and enhance their devs’ productivity with Incredibuild.
Airial, Clarus Financial Technology, cubetutor, Metawidget, mysocio, namma, silverpeas, Sokkva, So Rave, tagzbox
Find out what your peers are saying about GitLab, Google, GitHub and others in Build Automation. Updated: August 2025.
867,445 professionals have used our research since 2012.