Incredibuild vs Jenkins comparison

Cancel
You must select at least 2 products to compare!
IncrediBuild Logo
677 views|322 comparisons
100% 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 Incredibuild 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).
767,667 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
"It is saving time for developers, which is saving money for the company."

More Incredibuild Pros →

"The most valuable aspect of this solution is that there are multiple features. We can abstract certain variables and then build our deployment routine while being able to do some abstraction onto the SSH connections.""It is easy to use.""Jenkins is a very mature product.""For business needs, Jenkins is the most relevant choice because it can be self-hosted, the price is good, it’s robust, and requires almost no effort for maintenance.""There are a large number of plugins available for integration with third party systems.""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.""Configuration management: It is so easy to configure a Jenkins instance. Migrate configuration to a new environment just by copying XML files and setting up new nodes.""Having builds and test tasks triggered on commit helps not to break the product."

More Jenkins Pros →

Cons
"Stability could be improved. I don't know the reason for the instability because there are no logs that help me to understand the problem."

More Incredibuild Cons →

"Partition security for the workflow of projects is not yet an option.""The disadvantage of Jenkins is writing Groovy scripts. There are other CI tools where you do not need to write this many scripts to manage and deploy.""The product should provide more visualization as to how many pipelines are performing and how many builds are happening. It should also integrate with Kubernetes and OpenShift.""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.""I would like to see even more integrations included in the next release.""Jenkins could simplify the user interface a little bit because it sometimes creates too many features cramped in the UI.""The bug fix speed is very slow.""Jenkins is an open-source solution, and people tend to stay on the same version for a long time. When you look for an answer on Google, you often find something that doesn't relate to your implementation. The plugins are both the aspect of Jenkins and also one of the worst because the plugins can have different versions, so it's hard to figure out how to solve the problems."

More Jenkins Cons →

Pricing and Cost Advice
  • "Its pricing and licensing are annoying. Every year, I need to renew. If I miss the deadline date, all my processes will stop working. So, I would prefer that I wouldn't need to renew every year, instead have another solution for it. Or, if we could have an enterprise license agreement with the company, then the development team wouldn't need to spend time renewing licenses."
  • More Incredibuild Pricing and Cost Advice →

  • "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.
    767,667 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
    Ask a question

    Earn 20 points

    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
    20th
    out of 41 in Build Automation
    Views
    677
    Comparisons
    322
    Reviews
    0
    Average Words per Review
    0
    Rating
    N/A
    2nd
    out of 41 in Build Automation
    Views
    6,896
    Comparisons
    5,921
    Reviews
    39
    Average Words per Review
    386
    Rating
    7.8
    Comparisons
    Bazel logo
    Compared 55% of the time.
    TeamCity logo
    Compared 19% of the time.
    GitLab logo
    Compared 12% of the time.
    GitLab logo
    Compared 16% of the time.
    Bamboo logo
    Compared 14% of the time.
    AWS CodePipeline logo
    Compared 9% of the time.
    IBM Rational Build Forge logo
    Compared 7% of the time.
    Tekton logo
    Compared 7% of the time.
    Learn More
    Overview

    Incredibuild, the world’s leading platform for development acceleration, lets you deliver faster developer cycles and shorten your time-top market with more compute power and lower costs on prem and the cloud.

    Incredibuild enables every machine to use hundreds of cores to accelerate time-consuming software development by using idle CPUs in network or bursting to the cloud. Use the full potential of your network to raise product quality, iterate more frequently, and increase dev productivity.

    Most importantly, Incredibuild works out of the box, no need to change any of your existing toolchain, processes, or code.

    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
    Over 2,000 companies worldwide across industries inluding Epic Games, Microsoft, Playstation, Nintendo, Samsung, GM, Intel, CitiGroup, Qualcomm, Boeing, Motorola, Qt, and more accelerate their development and enhance their devs’ productivity with Incredibuild.
    Airial, Clarus Financial Technology, cubetutor, Metawidget, mysocio, namma, silverpeas, Sokkva, So Rave, tagzbox
    Top Industries
    VISITORS READING REVIEWS
    Manufacturing Company19%
    Computer Software Company15%
    Legal Firm10%
    Non Profit7%
    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
    VISITORS READING REVIEWS
    Small Business21%
    Midsize Enterprise18%
    Large Enterprise61%
    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.
    767,667 professionals have used our research since 2012.

    Incredibuild is ranked 20th in Build Automation while Jenkins is ranked 2nd in Build Automation with 83 reviews. Incredibuild is rated 8.0, while Jenkins is rated 8.0. The top reviewer of Incredibuild writes "Saves time for developers, which saves money for the company". 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". Incredibuild is most compared with Bazel, TeamCity and GitLab, 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.