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

Inedo BuildMaster 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

Inedo BuildMaster
Ranking in Build Automation
31st
Average Rating
6.0
Reviews Sentiment
7.0
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 October 2025, in the Build Automation category, the mindshare of Inedo BuildMaster is 0.6%, up from 0.1% compared to the previous year. The mindshare of Jenkins is 9.1%, down from 11.4% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Build Automation Market Share Distribution
ProductMarket Share (%)
Jenkins9.1%
Inedo BuildMaster0.6%
Other90.3%
Build Automation
 

Featured Reviews

Rajat Rawat - PeerSpot reviewer
Deployment agent that allows us to deploy out to various other servers but doesn't provide build automation
I would rate this solution as six out of ten. There isn't a big learning curve. It's a very straightforward and simple tool. It can be used anywhere to deploy your code or to configure files. I would recommend it, but there are already better tools in the market. We feel that it's probably not the best tool available, even though we have used it for quite some time. The automation with the REST APIs and other types of APIs isn't that great. There are some things you need to do manually to set up the tool. Other tools provide things you can do automatically through APIs. Inedo BuildMaster is a good tool if you want to have some deployments in your company. The problem is that it's a very limited tool and needs some additional features, like an approval based process for REST APIs. It only works for deployment-related things. These days, tools like Jenkins and DevOps are coming up with build automation. Because Inedo BuildMaster is a deployment-centered tool, you'll need to use a different tool for build automation, which makes it less likely to be used. If they work on that aspect, the solution would be better.
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

"Technical support is quick to respond. I haven't had any issues with them."
"Jenkins is a CI/CD tool and is the most robust tool."
"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."
"We can schedule anything with Jenkins, which is useful for deployment or anything that requires scheduling. It also has multiple plugins we can use for Maven, JUnit, etc."
"We are using the open-source version and there is a lot of plugins and features that are available and it works on agents for free. In other solutions, it will cost extra to use them with the agent."
"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."
"Configuration management: It is so easy to configure a Jenkins instance. Migrate configuration to a new environment just by copying XML files and setting up new nodes."
"A lot of support material exists via a single web search of exactly what you're looking for."
"Jenkins' most valuable feature is Pipeline."
 

Cons

"The documentation should be better. It should be very easy to call REST APIs, and the documentation has to be perfect for that."
"Centralized user management would be helpful."
"Jenkins relies on the old version of interface for configuration management. This needs improvement."
"Sometimes you have Jenkins restarting because of OOM errors."
"Upgrading and maintaining plugins can be painful, as sometimes upgrading a plugin can break functionality of another plugin that a job is dependent on."
"Developer documentation for plugins, plugin development, integrations: Sometimes it’s tricky to do pretty obvious things."
"Jenkins could improve in areas related to Kubernetes and Docker container integration, like machine allocation of nodes and Marshaling integration improvements."
"The disadvantage of Jenkins is writing Groovy scripts. There are other CI tools where you do not need to write this many scripts to manage and deploy."
"And I don't care too much for the Jenkins user interface. It's not that user-friendly compared to other solutions available right now. It's not a great user experience. You can do just fine if you are a techie, but it would take a novice some time to learn it and get things done."
 

Pricing and Cost Advice

Information not available
"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."
"Jenkins is not expensive and reasonably priced."
"It could be cheaper because there are many solutions available in the market. We are paying yearly."
"Jenkins is an open-source tool."
"The open-source version is free, but small companies would not be able to afford the cloud-based version."
"​It is free.​"
"We use the tool's open-source version which is free. There is an enterprise version which is expensive but comes with better support."
"The solution is open source."
report
Use our free recommendation engine to learn which Build Automation solutions are best for your needs.
868,787 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
No data available
Financial Services Firm
20%
Manufacturing Company
13%
Computer Software 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

No data available
 

Also Known As

BuildMaster
No data available
 

Overview

 

Sample Customers

Rate Setter, Axian
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: September 2025.
868,787 professionals have used our research since 2012.