Overview

Travis CI

Stacks26.5K

Followers6.7K

Votes1.7K

GitHub Actions

Stacks24.2K

Followers3.1K

Votes27

Github Actions vs Travis CI: What are the differences?

Key differences between Github Actions and Travis CI

1. Pricing model: Github Actions offers a more flexible pricing model compared to Travis CI. While Travis CI has a tiered pricing structure based on the number of concurrent jobs and build minutes, Github Actions provides a certain number of free minutes and allows users to pay for additional minutes as per their usage.

2. Native integration with Github: Github Actions has native integration with Github repositories, making it easier to set up and manage CI/CD pipelines. It eliminates the need for extra configuration and provides a seamless experience for developers. In contrast, Travis CI requires additional setup and configuration to integrate with Github repositories.

3. Customizable execution environments: Github Actions allows users to define custom execution environments for their workflows. Users can specify the operating system, runtime version, and other dependencies specific to their project requirements. On the other hand, Travis CI provides a more limited set of pre-configured environments to choose from.

4. Supports Windows, macOS, and Linux: Github Actions supports Windows, macOS, and Linux operating systems, providing a versatile platform for building and testing applications. Travis CI initially focused on supporting Linux environments but has since added limited support for macOS.

5. Community support and third-party integrations: Github Actions benefits from a large community of users who contribute to the platform by creating and sharing reusable workflows. It also has a wide range of third-party integrations available, including popular tools like Slack, Jira, and Docker. While Travis CI also has a supportive community, the ecosystem is not as extensive as Github Actions.

6. Workflow visualization and logs: Github Actions provides a visual representation of workflows and their execution status, making it easier to understand and debug the CI/CD process. It also offers detailed logs for each step of the workflow, allowing developers to analyze and troubleshoot issues effectively. Travis CI, although having a similar feature, does not provide the same level of visual representation and detailed logs as Github Actions.

In summary, Github Actions offers a more flexible pricing model, native integration with Github repositories, customizable execution environments, support for multiple operating systems, extensive community support and third-party integrations, as well as better workflow visualization and logging capabilities compared to Travis CI.

🔥 Trending in Continuous Integration on StackShare

Everdone Continuous Integration

Everdone

Try it View Docs Alternatives

Try

0

1

Advice on Travis CI, GitHub Actions

Somnath

Engineering Leader at Altimetrik Corp.

Jun 25, 2020

Needs adviceon

CircleCI

Drone.io

GitHub Actions

I am in the process of evaluating CircleCI, Drone.io, and GitHub Actions to cover my #CI/ #CD needs. I would appreciate your advice on comparative study w.r.t. attributes like language-Inclusive support, code-base integration, performance, cost, maintenance, support, ease of use, ability to deal with big projects, etc. based on actual industry experience.

Thanks in advance!

1.82M views1.82M

Comments

Felipe

May 24, 2020

Needs advice

My website is brand new and one of the few requirements of testings I had to implement was code coverage. Never though it was so hard to implement using a #docker container.
Given my lack of experience, every attempt I tried on making a simple code coverage test using the 4 combinations of #TravisCI, #CircleCi with #Coveralls, #Codecov I failed. The main problem was I was generating the .coverage file within the docker container and couldn't access it with #TravisCi or #CircleCi, every attempt to solve this problem seems to be very hacky and this was not the kind of complexity I want to introduce to my newborn website.
This problem was solved using a specific action for #GitHubActions, it was a 3 line solution I had to put in my github workflow file and I was able to access the .coverage file from my docker container and get the coverage report with #Codecov.

198k views198k

Comments

StackShare

Apr 17, 2019

Needs advice

From a StackShare Community member: "Currently we use Travis CI and have optimized it as much as we can so our builds are fairly quick. Our boss is all about redundancy so we are looking for another solution to fall back on in case Travis goes down and/or jacks prices way up (they were recently acquired). Could someone recommend which CI we should go with and if they have time, an explanation of how they're different?"

529k views529k

Comments

Detailed Comparison

Travis CI	GitHub Actions
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.	It makes it easy to automate all your software workflows, now with world-class CI/CD. Build, test, and deploy your code right from GitHub. Make code reviews, branch management, and issue triaging work the way you want.
Easy Setup- Getting started with Travis CI is as easy as enabling a project, adding basic build instructions to your project and committing code.;Supports Your Platform- Lots of databases and services are pre-installed and can simply be enabled in your build configuration, we'll launch them for you automatically. MySQL, PostgreSQL, ElasticSearch, Redis, Riak, RabbitMQ, Memcached are available by default.;Deploy With Confidence- Deploying to production after a successful build is as easy as setting up a bit of configuration, and we'll deploy your code to Heroku, Engine Yard Cloud, Nodejitsu, cloudControl, OpenShift, and CloudFoundry.	Multiple workflow files support; Free and open source; Workflow run interface; Search for actions in GitHub Marketplace; Integrated with Github's Checks API; Logs and artifacts downloading support
Statistics
Stacks 26.5K	Stacks 24.2K
Followers 6.7K	Followers 3.1K
Votes 1.7K	Votes 27
Pros & Cons
Pros 506 Github integration 388 Free for open source 271 Easy to get started 191 Nice interface 162 Automatic deployment Cons 8 Can't be hosted insternally 3 Unstable 3 Feature lacking 2 Incomplete documentation for all platforms	Pros 8 Integration with GitHub 5 Free 3 Easy to duplicate a workflow 3 Ready actions in Marketplace 2 Docker Support Cons 5 Lacking [skip ci] 4 Lacking allow failure 3 Lacking job specific badges 2 No ssh login to servers 1 No manual launch
Integrations
Amazon S3 Heroku AWS CodeDeploy MySQL Red Hat OpenShift Nodejitsu npm GitHub Engine Yard Cloud cloudControl	GitHub

What are some alternatives to Travis CI, GitHub Actions?

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.

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.

Airflow

Use Airflow to author workflows as directed acyclic graphs (DAGs) of tasks. The Airflow scheduler executes your tasks on an array of workers while following the specified dependencies. Rich command lines utilities makes performing complex surgeries on DAGs a snap. The rich user interface makes it easy to visualize pipelines running in production, monitor progress and troubleshoot issues when needed.

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.