When comparing Buddy vs Travis, the Slant community recommends Travis for most people. In the question“What are the best continuous integration tools?” Travis is ranked 7th while Buddy is ranked 15th. The most important reason people chose Travis is:
Travis is free for all public repositories on Github.
Specs
Ranked in these QuestionsQuestion Ranking
Pros
Pro Easy Pipeline Setups
The ease to setup custom pipelines are amazing, can easily various settings quickly and then be ready to deploy.
Pro Multitude of Actions
Almost any action you can need and think of is already here, making it easy for you to setup your pipeline.
Pro Nice material design
The design is minimalistic and based on today's standarts on material design. It uses colors which are pleasing to the eye and displays the information in an ordered way. The main view shows the latest activity sorted in a chronological order, displaying commits and pushes.
Every repo has it's own view, on the top there's the repo's name and a dropdown which displays the current branch with the ability to change to another branch or to create a new one.
On the right there's a vertical menu with links to add a new file, show the history or to download the current repository.
Pro Free private repositories
Private repositories are free. Although they are free for up to 3 repos and each repository must be less than 100MB in size.
Pro Lots of integrations, for example discord, slack
Pro Free for open source projects
Travis is free for all public repositories on Github.
Pro Easy to set up and configure
All that is needed to set up Travis is a configuration file (travis.yml) in the root of the repository where it will be installed and Travis takes care of the rest.
Pro Github integration
Travis registers every push to GitHub and automatically builds the branch by default.
Pro Supports most technological stacks
Supports the most widely used technological stacks (Node, Ruby, PHP, Python etc...) for free.
Pro OSX & Ubuntu support
Travis' VM are built on Ubuntu 12.04 64 bit Server Edition, with the exception of Objective-C builds, which are based on Mac OS X Mavericks.
Pro Multiple test environments for different runtime versions
Travis supports testing for different versions of the same runtime. All it takes is some lines in the travis.yml
file.
Pro Supports more than a dozen languages
Support for C, C++, Clojure, Erlang, Go, Groovy, Haskell, Java, JavaScript, Perl, PHP, Python, Ruby and Scala.
Pro Great community
Travis CI has a large and helpful community which is quite accepting to new users and provides a great number of tutorials.
Pro Private repositories and personal support w/ TravisPro
Starting at $129 you can use TravisPro, that adds the option of closed-source, private, repositories and personal support.
Pro Excellent website user experience
Cons
Con Unlimited private repositories are not free
To have more than three repositories and to bypass the limit of 100MB per repository it's not free. It costs $3/month.
Con Only partial .NET support
.NET support is limited to .NET Core and Mono.
Con Only GitHub support
It does not support BitBucket. So it's not in list for companies using BitBucket private or public repositories.
Con Relatively expensive
Commercial plans for Travis are relatively expensive compared to other tools. They start at $129/month.
Con Non-free for private repos
Travis CI was first built to serve and help Open Source Projects, but now they also have added support for Closed Source which unfortunately is not free.
Con No Windows support
Travis can only run tests on Linux and OS X operating systems; running tests on Windows is not currently supported.