Inedo BuildMaster vs Jenkins comparison

Cancel
You must select at least 2 products to compare!
Inedo Logo
98 views|60 comparisons
0% willing to recommend
Jenkins Logo
6,896 views|5,921 comparisons
88% willing to recommend
Comparison Buyer's Guide
Executive Summary

We performed a comparison between Inedo BuildMaster and Jenkins based on real PeerSpot user reviews.

Find out what your peers are saying about GitLab, Jenkins, Google and others in Build Automation.
To learn more, read our detailed Build Automation Report (Updated: April 2024).
768,740 professionals have used our research since 2012.
Featured Review
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."

More Inedo BuildMaster Pros →

"Jenkins has built good plugins and has a good security platform.""It's very useful when you want to automate different processes from beginning to end.""The deployment of traditional Jenkins is easy.""Jenkins optimizes the CI/CD process, enhances automation, and ensures efficiency and management of our build and deployment pipeline.""When we have manual tasks, we have to depend on multiple technical teams. With Jenkins, we can bring all the technologies together by the click of a button. We can see results without having to depend on different teams. Jenkins makes life easy for the database and DevOps teams.""Jenkins has excellent task planning features.""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.""It has a lot of community posts and support."

More Jenkins Pros →

Cons
"The documentation should be better. It should be very easy to call REST APIs, and the documentation has to be perfect for that."

More Inedo BuildMaster Cons →

"The documentation is not helpful, as it is not user-friendly.""We need more licensed product integrations.""I would like them to provide space for people to have a central node that stores all the logs of workspace information in a distributed fashion to facilitate backup and restoration. Currently, everything is stored on one node, so you need to set up distributed storage or an endpoint that you can use for backing up your information.""It would be helpful if they had a bit more interactive UI.""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.""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.""For this solution to be a 10, it has to be a lot more stable. Maybe the public version of Jenkins is stable, but in our case it's not stable.""Sometimes you have Jenkins restarting because of OOM errors."

More Jenkins Cons →

Pricing and Cost Advice
Information Not Available
  • "It is a free product."
  • "Jenkins is open source."
  • "​It is free.​"
  • "Some of the add-ons are too expensive."
  • "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."
  • "Jenkins is open source and free."
  • "There is no cost. It is open source."
  • More Jenkins Pricing and Cost Advice →

    report
    Use our free recommendation engine to learn which Build Automation solutions are best for your needs.
    768,740 professionals have used our research since 2012.
    Comparison Review
    Anonymous User
    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 nowadays. The biggest difference upon initial inspection is that TeamCity is far more focused on validating individual commits rather than certain types of tests. Jenkins’ front page presents information that is simply not useful in a non-linear development environment, where people are often working in vastly different directions. How many of the previous tests passed/failed is not really salient information in this kind of situation. Running specific tests for individual commits on TeamCity is far more trivial in terms of interface complexity than Jenkins. TeamCity just involves clicking the ”…” button in the corner on any test type (although I wish it wasn’t so easy to click “Run” by accident). I generally find TeamCity a lot more intuitive than Jenkins out of the box. There’s a point at which you feel that if you have to scour the documentation to do anything remotely complex in an application, you’re dealing with a bad interface. One disappointing thing in both is that inter-branch merges improperly trigger e-mails to unrelated committers. I suppose it is fairly difficult to determine who to notify about failure in situations like these, though. It seems like TeamCity pulls up the… Read more →
    Questions from the Community
    Top Answer:Technical support is quick to respond. I haven't had any issues with them.
    Top Answer:The documentation should be better. It should be very easy to call REST APIs, and the documentation has to be perfect for that. The embedded tasks and approval process looks very basic in the older… more »
    Top Answer:We use this solution as a deployment agent to deploy out to various other servers. We're using version 6.1. We host the solution on our own server. There are about 100 people using this solution in my… more »
    Top Answer: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 easy… more »
    Top Answer:Jenkins has been instrumental in automating our build and deployment processes.
    Ranking
    21st
    out of 41 in Build Automation
    Views
    98
    Comparisons
    60
    Reviews
    1
    Average Words per Review
    399
    Rating
    6.0
    2nd
    out of 41 in Build Automation
    Views
    6,896
    Comparisons
    5,921
    Reviews
    39
    Average Words per Review
    386
    Rating
    7.8
    Comparisons
    Also Known As
    BuildMaster
    Learn More
    Inedo
    Video Not Available
    Overview

    BuildMaster lets you release your software reliably, to any environment, at whatever pace the business demands. Build a self-service release management platform by allowing different teams to manage their own applications and deploy to their own environments. BuildMaster allows you to start simple and then scale to thousands of servers and the cloud.

    Jenkins is an award-winning application that monitors executions of repeated jobs, such as building a software project or jobs run by cron.

    Sample Customers
    Rate Setter, Axian
    Airial, Clarus Financial Technology, cubetutor, Metawidget, mysocio, namma, silverpeas, Sokkva, So Rave, tagzbox
    Top Industries
    No Data Available
    REVIEWERS
    Financial Services Firm33%
    Computer Software Company23%
    Media Company9%
    Comms Service Provider9%
    VISITORS READING REVIEWS
    Financial Services Firm20%
    Computer Software Company17%
    Manufacturing Company11%
    Government6%
    Company Size
    No Data Available
    REVIEWERS
    Small Business27%
    Midsize Enterprise16%
    Large Enterprise58%
    VISITORS READING REVIEWS
    Small Business17%
    Midsize Enterprise11%
    Large Enterprise72%
    Buyer's Guide
    Build Automation
    April 2024
    Find out what your peers are saying about GitLab, Jenkins, Google and others in Build Automation. Updated: April 2024.
    768,740 professionals have used our research since 2012.

    Inedo BuildMaster is ranked 21st in Build Automation with 1 review while Jenkins is ranked 2nd in Build Automation with 83 reviews. Inedo BuildMaster is rated 6.0, while Jenkins is rated 8.0. The top reviewer of Inedo BuildMaster writes "Deployment agent that allows us to deploy out to various other servers but doesn't provide build automation". On the other hand, the top reviewer of Jenkins writes "A highly-scalable and stable solution that reduces deployment time and produces a significant return on investment". Inedo BuildMaster is most compared with , whereas Jenkins is most compared with GitLab, Bamboo, AWS CodePipeline, IBM Rational Build Forge and Tekton.

    See our list of best Build Automation vendors.

    We monitor all Build Automation reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. We validate each review for authenticity via cross-reference with LinkedIn, and personal follow-up with the reviewer when necessary.