Concourse vs Travis CI: What are the differences?
Concourse: Pipeline-based CI system written in Go. Concourse's principles reduce the risk of switching to and from Concourse, by encouraging practices that decouple your project from your CI's little details, and keeping all configuration in declarative files that can be checked into version control; 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.
Concourse and Travis CI belong to "Continuous Integration" category of the tech stack.
"Real pipelines" is the top reason why over 8 developers like Concourse, while over 505 developers mention "Github integration" as the leading cause for choosing Travis CI.
Concourse is an open source tool with 3.99K GitHub stars and 482 GitHub forks. Here's a link to Concourse's open source repository on GitHub.
According to the StackShare community, Travis CI has a broader approval, being mentioned in 670 company stacks & 624 developers stacks; compared to Concourse, which is listed in 18 company stacks and 17 developer stacks.
Sign up to add or upvote prosMake informed product decisions
Sign up to add or upvote consMake informed product decisions
What is Concourse?
What is Travis CI?
Need advice about which tool to choose?Ask the StackShare community!
Sign up to get full access to all the companiesMake informed product decisions
Sign up to get full access to all the tool integrationsMake informed product decisions