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
32nd
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 June 2025, in the Build Automation category, the mindshare of Inedo BuildMaster is 0.2%, up from 0.1% compared to the previous year. The mindshare of Jenkins is 10.5%, down from 13.0% 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.
Mahdi Mallaki - PeerSpot reviewer
Has a community of plugin providers but needs improvement in Kubernetes integration
Integrating Jenkins with other tools or solutions has presented some challenges. For instance, when attempting to integrate Jenkins with Kubernetes, I encountered numerous errors, which took several days to resolve. In Jenkins, adding a feature typically involves incorporating the repository feature separately. Jenkins lacks built-in Git repository functionality, necessitating an external Git repository to store Jenkins manifests. In contrast, GitLab offers an integrated Git repository and pipeline runner, streamlining the process. One improvement for Jenkins could be integrating a Git server, simplifying the management of CI/CD pipelines. Currently, with Jenkins, modifying pipeline manifests requires navigating to a separate Git repository. In GitLab, however, manifest changes can be made directly within the repository.

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."
"The most valuable feature of Jenkins is its open source."
"I love Jenkins. I like that you work on anything, and you make anything. Jenkins is very important for my team. I am satisfied with the product."
"It is easy to use."
"It can scale easily."
"Jenkins is very user-friendly."
"The simplicity of Jenkins and the evolving ecosystem of Jenkins are most valuable. Today, you do not have to write a pipeline from scratch. The library functionality of Jenkins helps you to bring all those in ready-made, and you also get the best practices for them. That is a great feature of Jenkins, and that is why it is being used significantly."
"I can install Jenkins for integration from multiple developers and automate application delivery, staging, and production environments."
"I like the business logs. It's a very useful tool. Client-server communication is also very fast."
 

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 could simplify the user interface a little bit because it sometimes creates too many features cramped in the UI."
"The solution could improve by having more advanced integrations."
"Partition security for the workflow of projects is not yet an option."
"Developer documentation for plugins, plugin development, integrations: Sometimes it’s tricky to do pretty obvious things."
"I would like to see even more integrations included in the next release."
"Integrating Jenkins with other tools or solutions has presented some challenges. For instance, when attempting to integrate Jenkins with Kubernetes, I encountered numerous errors, which took several days to resolve. In Jenkins, adding a feature typically involves incorporating the repository feature separately. Jenkins lacks built-in Git repository functionality, necessitating an external Git repository to store Jenkins manifests."
"The major drawback with Jenkins is the lack of support."
"Adding support for OIDC and internal user databases simultaneously would improve Jenkins."
 

Pricing and Cost Advice

Information not available
"Some of the add-ons are too expensive."
"Jenkins is an open-source tool."
"We are using the free version of Jenkins. There are no costs or licensing."
"I used the free OSS version all the time. It was enough for all my needs."
"The open-source version is free, but small companies would not be able to afford the cloud-based version."
"The pricing for Jenkins is free."
"Jenkins is a free open-source server."
"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.
856,873 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
18%
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: June 2025.
856,873 professionals have used our research since 2012.