Blue Ocean vs Travis CI

Overview

Travis CI

Stacks28.0K

Followers6.7K

Votes1.7K

Blue Ocean

Stacks92

Followers167

Votes7

GitHub Stars2.9K

Forks537

Blue Ocean vs Travis CI: What are the differences?

Blue Ocean: A reboot of the Jenkins CI/CD User Experience. Designed from the ground up for Jenkins Pipeline and compatible with Freestyle jobs, Blue Ocean reduces clutter and increases clarity for every member of your team; 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.

Blue Ocean and Travis CI can be primarily classified as "Continuous Integration" tools.

Some of the features offered by Blue Ocean are:

Sophisticated visualizations of CD pipelines, allowing for fast and intuitive comprehension of software pipeline status.
Pipeline editor (In Development) that makes automating CD pipelines approachable by guiding the user through an intuitive and visual process to create a pipeline.
Personalization of the Jenkins UI to suit the role-based needs of each member of the DevOps team.

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.

"Beautiful interface" is the primary reason why developers consider Blue Ocean over the competitors, whereas "Github integration" was stated as the key factor in picking Travis CI.

Blue Ocean is an open source tool with 2.49K GitHub stars and 435 GitHub forks. Here's a link to Blue Ocean'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 Blue Ocean, which is listed in 4 company stacks and 10 developer stacks.

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, Blue Ocean

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	Blue Ocean
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.	Designed from the ground up for Jenkins Pipeline and compatible with Freestyle jobs, Blue Ocean reduces clutter and increases clarity for every member of your team.
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.	Sophisticated visualizations of CD pipelines, allowing for fast and intuitive comprehension of software pipeline status.;Pipeline editor (In Development) that makes automating CD pipelines approachable by guiding the user through an intuitive and visual process to create a pipeline.;Personalization of the Jenkins UI to suit the role-based needs of each member of the DevOps team.;Pinpoint precision when intervention is needed and/or issues arise. The Blue Ocean UI shows where in the pipeline attention is needed, facilitating exception handling and increasing productivity.;Native integration for branch and pull requests enables maximum developer productivity when collaborating on code with others in GitHub and Bitbucket.
Statistics
GitHub Stars -	GitHub Stars 2.9K
GitHub Forks -	GitHub Forks 537
Stacks 28.0K	Stacks 92
Followers 6.7K	Followers 167
Votes 1.7K	Votes 7
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 7 Beautiful interface
Integrations
Amazon S3 Heroku AWS CodeDeploy MySQL Red Hat OpenShift Nodejitsu npm GitHub Engine Yard Cloud cloudControl	Jenkins

What are some alternatives to Travis CI, Blue Ocean?

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.

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.

Snap CI

Snap CI is a cloud-based continuous integration & continuous deployment tool with powerful deployment pipelines. Integrates seamlessly with GitHub and provides fast feedback so you can deploy with ease.

Related Comparisons

Bitbucket vs GitHub vs GitLab

AWS CodeCommit vs Bitbucket vs GitHub

Docker Swarm vs Kubernetes vs Rancher

Grunt vs Webpack vs gulp

Grafana vs Graphite vs Kibana

Blue Ocean vs Travis CI: What are the differences?

Blue Ocean and Travis CI can be primarily classified as "Continuous Integration" tools.

Some of the features offered by Blue Ocean are:

Sophisticated visualizations of CD pipelines, allowing for fast and intuitive comprehension of software pipeline status.
Pipeline editor (In Development) that makes automating CD pipelines approachable by guiding the user through an intuitive and visual process to create a pipeline.
Personalization of the Jenkins UI to suit the role-based needs of each member of the DevOps team.

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.

"Beautiful interface" is the primary reason why developers consider Blue Ocean over the competitors, whereas "Github integration" was stated as the key factor in picking Travis CI.

Blue Ocean is an open source tool with 2.49K GitHub stars and 435 GitHub forks. Here's a link to Blue Ocean's open source repository on GitHub.