Get Advice Icon

Need advice about which tool to choose?Ask the StackShare community!

Heroku CI
Heroku CI

66
68
+ 1
4
Travis CI
Travis CI

4.2K
2.9K
+ 1
1.7K
Add tool

Heroku CI vs Travis CI: What are the differences?

What is 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.

What is Travis CI? A hosted continuous integration service for open source and private projects. 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.

Heroku CI and Travis CI belong to "Continuous Integration" category of the tech stack.

According to the StackShare community, Travis CI has a broader approval, being mentioned in 670 company stacks & 624 developers stacks; compared to Heroku CI, which is listed in 10 company stacks and 12 developer stacks.

- No public GitHub repository available -
- No public GitHub repository available -

What is Heroku CI?

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.

What is 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.
Get Advice Icon

Need advice about which tool to choose?Ask the StackShare community!

Why do developers choose Heroku CI?
Why do developers choose Travis CI?

Sign up to add, upvote and see more prosMake informed product decisions

What are the cons of using Heroku CI?
What are the cons of using Travis CI?
    Be the first to leave a con
    What companies use Heroku CI?
    What companies use Travis CI?

    Sign up to get full access to all the companiesMake informed product decisions

    What tools integrate with Heroku CI?
    What tools integrate with Travis CI?

    Sign up to get full access to all the tool integrationsMake informed product decisions

    What are some alternatives to Heroku CI and Travis CI?
    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.
    Heroku
    Heroku is a cloud application platform – a new way of building and deploying web apps. Heroku lets app developers spend 100% of their time on their application code, not managing servers, deployment, ongoing operations, or scaling.
    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.
    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.
    GitLab CI
    GitLab offers a continuous integration service. If you add a .gitlab-ci.yml file to the root directory of your repository, and configure your GitLab project to use a Runner, then each merge request or push triggers your CI pipeline.
    See all alternatives
    Decisions about Heroku CI and Travis CI
    No stack decisions found
    Interest over time
    Reviews of Heroku CI and Travis CI
    Avatar of tschellenbach
    CEO at Stream
    Review ofTravis CITravis CI

    In the past we used to run Jenkins. The build server always had weird issues and was a pain to maintain. Travis is a great solution for CI. Their Debug build features makes it trivial to figure out why your build broke. The integration with Github is also very slick. One thing they could improve is the documentation on the .travis.yaml format. All in all, great company and very responsive supports. Over here at getstream.io we're a fan. Keep up the good work guys!

    How developers use Heroku CI and Travis CI
    Avatar of datapile
    datapile uses Travis CITravis CI

    Travis CI is our pillar for automated deployment, pull request testing, auto-merging (for non-mission-critical projects), and build testing per commit / release.

    It is highly configurable, super cheap, and extremely robust (supports every language and configuration we've thrown at it).

    Avatar of Pēteris Caune
    Pēteris Caune uses Travis CITravis CI

    While we usually run tests before commits, Travis goes further and tests with different Python versions and different database backends. It works great, and, best of all, it is free for open source projects.

    Avatar of Dieter Adriaenssens
    Dieter Adriaenssens uses Travis CITravis CI

    Travis CI builds and tests every commit. It's also used to deploy Buildtime Trend as a Service to Heroku and the Buildtime Trend Python library to the PyPi repository.

    Avatar of Nate Ferrell
    Nate Ferrell uses Travis CITravis CI

    Travis CI is critical for Linux and macOS CI tests for the Powershell module. Travis runs the same tests we run in AppVeyor in parallel.

    Avatar of Andrew Williams
    Andrew Williams uses Travis CITravis CI

    To ensure that what works locally will also work for someone else. Also used to send code coverage to codeintel

    How much does Heroku CI cost?
    How much does Travis CI cost?
    Pricing unavailable
    News about Heroku CI
    More news