Buildbot vs Heroku CI

Overview

Buildbot

Stacks73

Followers128

Votes27

GitHub Stars5.4K

Forks1.7K

Heroku CI

Stacks90

Followers132

Votes5

Buildbot vs Heroku CI: What are the differences?

Buildbot: Python-based continuous integration testing framework. BuildBot is a system to automate the compile/test cycle required by most software projects to validate code changes. By automatically rebuilding and testing the tree each time something has changed, build problems are pinpointed quickly, before other developers are inconvenienced by the failure; Heroku CI: Fast, low-setup CI that’s easy to use. On every push to GitHub, Heroku CI runs your tests in a disposable Heroku app, so there’s never a wait time for a free CI worker. Tests run fast, on Performance dynos.

Buildbot and Heroku CI can be categorized as "Continuous Integration" tools.

Buildbot is an open source tool with 4K GitHub stars and 1.37K GitHub forks. Here's a link to Buildbot's open source repository on GitHub.

Pipefy, Landing.jobs, and Connected Bits are some of the popular companies that use Heroku CI, whereas Buildbot is used by Mozilla, Animoto, and Fetch Robotics. Heroku CI has a broader approval, being mentioned in 10 company stacks & 12 developers stacks; compared to Buildbot, which is listed in 7 company stacks and 6 developer stacks.

🔥 Trending in Continuous Integration on StackShare

GitHub Actions Continuous Integration

Automate your workflow from idea to production

Try it View Docs Alternatives

Try

4.23k

3.11k

Advice on Buildbot, Heroku CI

Sri Srinivas

Feb 11, 2020

Needs advice

I want to start automatic regressions for nightly builds and also continuous integration builds. The tests I ran are part of my regression suite. And I want to track the results of these tests.

I am able to do this with Jenkins using the Junit plugin. But, I am trying to do the same with Buildbot, and I am not able to get the report of the tests. So, I just want to know is it possible to get the reporting of tests through Buildbot. If yes, could anyone provide some examples

121k views121k

Comments

Detailed Comparison

Buildbot	Heroku CI
BuildBot is a system to automate the compile/test cycle required by most software projects to validate code changes. By automatically rebuilding and testing the tree each time something has changed, build problems are pinpointed quickly, before other developers are inconvenienced by the failure.	On every push to GitHub, Heroku CI runs your tests in a disposable Heroku app, so there’s never a wait time for a free CI worker. Tests run fast, on Performance dynos.
run builds on a variety of slave platforms;arbitrary build process: handles projects using C, Python, whatever;minimal host requirements: Python and Twisted;slaves can be behind a firewall if they can still do checkout;status delivery through web page, email, IRC, other protocols;track builds in progress, provide estimated completion time;flexible configuration by subclassing generic build process classes;debug tools to force a new build, submit fake Changes, query slave status;released under the GPL	-
Statistics
GitHub Stars 5.4K	GitHub Stars -
GitHub Forks 1.7K	GitHub Forks -
Stacks 73	Stacks 90
Followers 128	Followers 132
Votes 27	Votes 5
Pros & Cons
Pros 9 Highly configurable builds 5 Hosted internally 5 Beautiful waterfall 4 Free open source 3 Python	Pros 3 No waiting in the queue 1 Best in class pipeline integration 1 Consolidated Heroku billing
Integrations
No integrations available	Heroku GitHub

What are some alternatives to Buildbot, Heroku CI?

Jenkins

In a nutshell Jenkins CI is the leading open-source continuous integration server. Built with Java, it provides over 300 plugins to support building and testing virtually any project.

Travis CI

Free for open source projects, our CI environment provides multiple runtimes (e.g. Node.js or PHP versions), data stores and so on. Because of this, hosting your project on travis-ci.com means you can effortlessly test your library or applications against multiple runtimes and data stores without even having all of them installed locally.

Codeship

Codeship runs your automated tests and configured deployment when you push to your repository. It takes care of managing and scaling the infrastructure so that you are able to test and release more frequently and get faster feedback for building the product your users need.

CircleCI

Continuous integration and delivery platform helps software teams rapidly release code with confidence by automating the build, test, and deploy process. Offers a modern software development platform that lets teams ramp.

TeamCity

TeamCity is a user-friendly continuous integration (CI) server for professional developers, build engineers, and DevOps. It is trivial to setup and absolutely free for small teams and open source projects.

Drone.io

Drone is a hosted continuous integration service. It enables you to conveniently set up projects to automatically build, test, and deploy as you make changes to your code. Drone integrates seamlessly with Github, Bitbucket and Google Code as well as third party services such as Heroku, Dotcloud, Google AppEngine and more.

wercker

Wercker is a CI/CD developer automation platform designed for Microservices & Container Architecture.

GoCD

GoCD is an open source continuous delivery server created by ThoughtWorks. GoCD offers business a first-class build and deployment engine for complete control and visibility.

Shippable

Shippable is a SaaS platform that lets you easily add Continuous Integration/Deployment to your Github and BitBucket repositories. It is lightweight, super simple to setup, and runs your builds and tests faster than any other service.

Buildkite

CI and build automation tool that combines the power of your own build infrastructure with the convenience of a managed, centralized web UI. Used by Shopify, Basecamp, Digital Ocean, Venmo, Cochlear, Bugsnag and more.