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 August 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.3%, down from 12.2% 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.
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 can be used for elastic management, if you have any sensitive data or credentials you can use them across the environment. Additionally, the solution is easy to use and can be used across multiple use cases."
"The most valuable features of Jenkins are its ease of use and good plugins available. You are able to connect to a lot of solutions."
"Jenkins is very easy to use."
"With Jenkins, the pipeline will take your code from any versioning system like GitHub or Bitbucket. All the security scans can happen in one go and then all the tests also get run. You can just build one container in it and deploy it."
"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."
"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."
"The most valuable feature of Jenkins is its continuous deployment. We can deploy to multi-cluster and multi-regions in the cloud."
 

Cons

"The documentation should be better. It should be very easy to call REST APIs, and the documentation has to be perfect for that."
"Its schedule builds need improvement. It should have scheduling features in the platform rather than using external plug-ins."
"A more user-friendly UI for creating pipelines would be helpful."
"The enterprise version is less stable than the open-source version."
"They need to improve their documentation."
"We sometimes face challenges during version upgrades, such as failures when migrating Kubernetes versions."
"The user interface could be updated a little."
"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."
"It could be cheaper."
 

Pricing and Cost Advice

Information not available
"We are using the free version of Jenkins. There are no costs or licensing."
"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."
"In our company, we do pay for the licensing of the solution."
"Jenkins is not expensive and reasonably priced."
"I used the free OSS version all the time. It was enough for all my needs."
"It's free software with a big community behind it, which is very good."
"​It is free.​"
"It is an open source."
report
Use our free recommendation engine to learn which Build Automation solutions are best for your needs.
865,384 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
21%
Computer Software Company
14%
Manufacturing Company
13%
Government
7%
 

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, GitHub and others in Build Automation. Updated: July 2025.
865,384 professionals have used our research since 2012.