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."
"We significantly reduced build times of large projects (more than 80k lines of Scala code) using build time on Jenkins as a time sample. It reduced the developer write-test-commit cycle time, and increased productivity."
"Continuous Integration. Jenkins can integrate with almost any systems used for application development and testing, with its plugins."
"The deployment of traditional Jenkins is easy."
"We use Jenkins to automatically build Python binaries into several OS's i.e. OS X, Ubuntu, Windows 32-bit and Windows 64-bit."
"Jenkins is a CI/CD tool and is the most robust tool."
"Jenkins is a very mature product."
"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."
"Jenkins's open-based framework is very valuable."
 

Cons

"The documentation should be better. It should be very easy to call REST APIs, and the documentation has to be perfect for that."
"Jenkins can be improved, but it's difficult for me to explain. The initial setup could be more straightforward. If you connect Jenkins with bookings and lockouts, it can be challenging."
"Jenkins is an old product, and we encounter performance issues and slow response. Also, some of the plugins are not stable."
"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."
"I would like to have an integrated dashboard on top of it and a better UX to look at. The dashboard could be better in terms of integration with other tools. We should be able to have a single pane of glass across all the tools that we use where Jenkins is the pipeline. This can be a very good upgrade to it."
"Sometimes, random errors of metadata are not there, which causes delays. These are essentially gaps in the information being passed to the job."
"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."
"The documentation is not helpful, as it is not user-friendly."
"I would like to see even more integrations included in the next release."
 

Pricing and Cost Advice

Information not available
"The open-source version is free, but small companies would not be able to afford the cloud-based version."
"We are using the free version of Jenkins. There are no costs or licensing."
"We are using the free version of Jenkins. There is not a license required to use the solution because it is open-source."
"Jenkins is open-source, so it is free."
"It's free software with a big community behind it, which is very good."
"I used the free OSS version all the time. It was enough for all my needs."
"It could be cheaper because there are many solutions available in the market. We are paying yearly."
"We use the tool's open-source version which is free. There is an enterprise version which is expensive but comes with better support."
report
Use our free recommendation engine to learn which Build Automation solutions are best for your needs.
845,564 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,564 professionals have used our research since 2012.