Codefresh vs Travis CI

Overview

Travis CI

Stacks28.0K

Followers6.7K

Votes1.7K

Codefresh

Stacks64

Followers111

Votes47

Codefresh vs Travis CI: What are the differences?

Developers describe Codefresh as "CI/CD Tailor-Made For Docker". Automate and parallelize testing. Codefresh allows teams to spin up on-demand compositions to run unit and integration tests as part of the continuous integration process. Jenkins integration allows more complex pipelines. On the other hand, Travis CI is detailed as "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.

Codefresh and Travis CI are primarily classified as "Container" and "Continuous Integration" tools respectively.

Some of the features offered by Codefresh are:

Instant Dev, test and feature preview environments: Enables all team members to run any image as a standalone or composition for feature preview, manual testing, bug reproduction and more. Collaborate on features before pushing them into staging and production.
Testing with every step: Configure your pipeline to run integration and unit tests with every step
Instantly test all code changes in the Codefresh build system before pushing to staging & production. Run integration, unit tests in parallel.

On the other hand, Travis CI provides the following key features:

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.

"Fastest and easiest way to work with Docker" is the primary reason why developers consider Codefresh over the competitors, whereas "Github integration" was stated as the key factor in picking Travis CI.

Share your Stack

Help developers discover the tools you use. Get visibility for your team's tech choices and contribute to the community's knowledge.

View Docs

CLI (Node.js)

Manual

Advice on Travis CI, Codefresh

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

Tatiana

Nov 16, 2019

Decided

Jenkins is a pretty flexible, complete tool. Especially I love the possibility to configure jobs as a code with Jenkins pipelines.

CircleCI is well suited for small projects where the main task is to run continuous integration as quickly as possible. Travis CI is recommended primarily for open-source projects that need to be tested in different environments.

And for something a bit larger I prefer to use Jenkins because it is possible to make serious system configuration thereby different plugins. In Jenkins, I can change almost anything. But if you want to start the CI chain as soon as possible, Jenkins may not be the right choice.

734k views734k

Comments

Detailed Comparison

Travis CI	Codefresh
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.	Automate and parallelize testing. Codefresh allows teams to spin up on-demand compositions to run unit and integration tests as part of the continuous integration process. Jenkins integration allows more complex pipelines.
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.	Instant Dev, test and feature preview environments: Enables all team members to run any image as a standalone or composition for feature preview, manual testing, bug reproduction and more. Collaborate on features before pushing them into staging and production.; Testing with every step: Configure your pipeline to run integration and unit tests with every step; Instantly test all code changes in the Codefresh build system before pushing to staging & production. Run integration, unit tests in parallel.; 360° view of Docker images: View commit info, test results and build logs for all images; Manage Docker image labels and status, comment and see new feature branches; search and filter based on any attribute.; Out-of-the-box Docker buildpack for all technologies: Seamlessly package your code in a Docker image. Quickly associate a Dockerfile with your repo by selecting the repository technology stack (Java, Node, PHP, etc.). Codefresh then adds a template for Dockerizing apps.; View and Access Running Container Logs: Access each container log directly from within the Codefresh platform. This lets you easily perform root-cause analysis on failed services and allows you to see logs in high debug model level.; Support for Docker Compose 1 & 2: Manage your Docker Compose file natively in one place, with support for both Docker Compose versions 1 and 2. Use a built-in wizard to write Docker Compose files quickly.; YAML file support: Customize and easily define your pipeline steps using a codefresh.yml file.
Statistics
Stacks 28.0K	Stacks 64
Followers 6.7K	Followers 111
Votes 1.7K	Votes 47
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 Feature lacking 3 Unstable 2 Incomplete documentation for all platforms	Pros 11 Fastest and easiest way to work with Docker 7 Great support/fast builds/awesome ui 6 Great onboarding 5 Freestyle build steps to support custom CI/CD scripting 4 Robust feature-preview/qa environments on-demand Cons 1 Expensive compared to alternatives 1 Questionable product quality and stability
Integrations
Amazon S3 Heroku AWS CodeDeploy MySQL Red Hat OpenShift Nodejitsu npm GitHub Engine Yard Cloud cloudControl	Quay.io Docker Compose Docker Swarm BinTray Docker Cloud Amazon EC2 GitHub Bitbucket HipChat BlazeMeter

What are some alternatives to Travis CI, Codefresh?

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.

Kubernetes

Kubernetes is an open source orchestration system for Docker containers. It handles scheduling onto nodes in a compute cluster and actively manages workloads to ensure that their state matches the users declared intentions.

Rancher

Rancher is an open source container management platform that includes full distributions of Kubernetes, Apache Mesos and Docker Swarm, and makes it simple to operate container clusters on any cloud or infrastructure platform.

Docker Compose

With Compose, you define a multi-container application in a single file, then spin your application up in a single command which does everything that needs to be done to get it running.

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.

Docker Swarm

Swarm serves the standard Docker API, so any tool which already communicates with a Docker daemon can use Swarm to transparently scale to multiple hosts: Dokku, Compose, Krane, Deis, DockerUI, Shipyard, Drone, Jenkins... and, of course, the Docker client itself.

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.

Related Comparisons

Some of the features offered by Codefresh are:

Instant Dev, test and feature preview environments: Enables all team members to run any image as a standalone or composition for feature preview, manual testing, bug reproduction and more. Collaborate on features before pushing them into staging and production.
Testing with every step: Configure your pipeline to run integration and unit tests with every step
Instantly test all code changes in the Codefresh build system before pushing to staging & production. Run integration, unit tests in parallel.

On the other hand, Travis CI provides the following key features:

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.

Codefresh vs Travis CI