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
3rd
Average Rating
8.0
Reviews Sentiment
7.0
Number of Reviews
93
Ranking in other categories
No ranking in other categories
 

Mindshare comparison

As of April 2025, in the Build Automation category, the mindshare of Inedo BuildMaster is 0.1%, down from 0.1% compared to the previous year. The mindshare of Jenkins is 10.4%, down from 13.8% compared to the previous year. It is calculated based on PeerSpot user engagement data.
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.
Dinesh-Patil - PeerSpot reviewer
A highly-scalable and stable solution that reduces deployment time and produces a significant return on investment
The dashboard needs to be improved. Though the access management and authentication functionalities are present, the dashboard and UI could be more user-friendly. The product has many plug-ins. Users have to go through the documentation to be able to use the product. The UI must be more user-friendly. The information should be available in the dashboard itself. The users shouldn’t have to refer to the documentation. When a user hovers over the elements on the dashboard, it should reveal information about them.

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 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 most valuable features of Jenkins are the ease of use and the information about how to use the features is readily available on the internet. Additionally, with the solution, I can use other reporting tools, such as Flow."
"Jenkins is very stable."
"I am not aware of the available options in the market right now compared to Jenkins, but I am pretty much happy with the service that Jenkins is providing our company."
"We benefit from Kubernetes' ability to autoscale pods and use horizontal pod autoscalers to adjust the number of pods based on metrics like CPU or memory usage, ensuring efficient resource allocation and stability under load."
"Jenkins is a very mature product."
"I can install Jenkins for integration from multiple developers and automate application delivery, staging, and production environments."
"The solution is scalable and concurrent users have access to the platform."
 

Cons

"The documentation should be better. It should be very easy to call REST APIs, and the documentation has to be perfect for that."
"The onboarding of Jenkins should be smoother, and it should have more pipelines available as it's deployed on many different servers."
"Its schedule builds need improvement. It should have scheduling features in the platform rather than using external plug-ins."
"UI is quite outdated."
"The support for the latest Java Runtime Environment should be improved."
"This solution could be improved by removing the storage of unnecessary data such as the history of test deployments that were unsuccessful."
"Support should be provided at no cost, as there is no free support available for any of the free versions."
"Jenkins could improve by allowing more scripting languages. We need to use Groovy scripting and it is difficult to debug and it is not ideal for creating file scripts. We tried to search for assistance but we did not find much help."
"Centralized user management would be helpful."
 

Pricing and Cost Advice

Information not available
"The solution is one of the lowest costs compared to competitors."
"The open-source version is free, but small companies would not be able to afford the cloud-based version."
"​It is free.​"
"The pricing for Jenkins is free."
"It is an open source."
"Jenkins is open-source, so it is free."
"In our company, we do pay for the licensing of the solution."
"Jenkins is an open-source platform."
report
Use our free recommendation engine to learn which Build Automation solutions are best for your needs.
845,877 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
22%
Computer Software Company
17%
Manufacturing Company
11%
Government
6%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
No data available
 

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, Jenkins and others in Build Automation. Updated: April 2025.
845,877 professionals have used our research since 2012.