Overview

Travis CI

Stacks28.0K

Followers6.7K

Votes1.7K

Visual Studio App Center

Stacks113

Followers232

Votes4

Travis CI vs Visual Studio App Center: What are the differences?

Key Differences between Travis CI and Visual Studio App Center

Travis CI and Visual Studio App Center are both popular tools used in software development for continuous integration and delivery. However, they have some key differences that set them apart.

Integration with Different Platforms: Travis CI primarily focuses on providing continuous integration for GitHub hosted projects. On the other hand, Visual Studio App Center supports a wide range of platforms including iOS, Android, Windows, macOS, and more. This makes App Center a more versatile tool for developers working on various platforms.
Testing and Monitoring Capabilities: Visual Studio App Center offers advanced testing and monitoring capabilities compared to Travis CI. App Center provides features such as automated UI testing, beta distribution, crash reporting, and analytics. These features enable developers to thoroughly test and monitor their applications across multiple platforms, helping them to deliver high-quality software.
Build Configurations: Travis CI uses a declarative YAML-based configuration file to define the build and deployment process. On the other hand, Visual Studio App Center provides a user-friendly interface that allows developers to configure and manage builds without writing complex YAML files. This makes App Center a more beginner-friendly tool for developers who are not familiar with YAML configurations.
Community Support and Integrations: Travis CI has a strong community presence and offers hundreds of third-party integrations, allowing developers to customize their workflows. Visual Studio App Center, being a part of the Microsoft ecosystem, offers seamless integration with various Microsoft tools and services such as Azure DevOps, HockeyApp, and more. This integration provides developers with a comprehensive suite of tools to streamline their development and deployment process.
Pricing: Travis CI offers a free tier for open-source projects, giving developers a cost-effective solution. However, for private repositories and larger scale projects, paid plans are required. On the other hand, Visual Studio App Center offers a free tier with limited features, but for more advanced features and larger teams, paid plans are required. The pricing structure of these tools may influence the choice of developers based on their project requirements and budget.
Market Share and Popularity: Travis CI is a widely used and established continuous integration tool with a large user base. It has been around since 2011 and is considered one of the pioneers in the CI/CD space. Visual Studio App Center, being a relatively newer tool, is gaining traction in the market due to its integration with the Microsoft ecosystem and advanced features.

In summary, Travis CI is primarily focused on continuous integration for GitHub projects, while Visual Studio App Center offers a wider platform support, advanced testing capabilities, user-friendly build configurations, integration with Microsoft tools, and a growing market presence.

🔥 Trending in Continuous Integration on StackShare

Everdone Continuous Integration

Everdone

Try it View Docs Alternatives

Try

0

1

Advice on Travis CI, Visual Studio App Center

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	Visual Studio App Center
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 the lifecycle of your iOS, Android, Windows, and macOS apps. Connect your repo and within minutes build in the cloud, test on thousands of real devices, distribute to beta testers and app stores, and monitor real-world usage with crash and analytics data. All in one place.
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.	Build; Test; Distribute; Crashes; Diagnostics; Analytics; Push; CD/CI;
Statistics
Stacks 28.0K	Stacks 113
Followers 6.7K	Followers 232
Votes 1.7K	Votes 4
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 1 Show error issues for mobile devices 1 Slack integration 1 For Mobile apps diagnostics and tracking 1 Bug tracking integration
Integrations
Amazon S3 Heroku AWS CodeDeploy MySQL Red Hat OpenShift Nodejitsu npm GitHub Engine Yard Cloud cloudControl	GitHub Bitbucket Azure DevOps Slack

What are some alternatives to Travis CI, Visual Studio App Center?

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.

Ionic

Free and open source, Ionic offers a library of mobile and desktop-optimized HTML, CSS and JS components for building highly interactive apps. Use with Angular, React, Vue, or plain JavaScript.

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.

Flutter

Flutter is a mobile app SDK to help developers and designers build modern mobile apps for iOS and Android.

React Native

React Native enables you to build world-class application experiences on native platforms using a consistent developer experience based on JavaScript and React. The focus of React Native is on developer efficiency across all the platforms you care about - learn once, write anywhere. Facebook uses React Native in multiple production apps and will continue investing in React Native.

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.

Xamarin

Xamarin’s Mono-based products enable .NET developers to use their existing code, libraries and tools (including Visual Studio*), as well as skills in .NET and the C# programming language, to create mobile applications for the industry’s most widely-used mobile devices, including Android-based smartphones and tablets, iPhone, iPad and iPod Touch.

NativeScript

NativeScript enables developers to build native apps for iOS, Android and Windows Universal while sharing the application code across the platforms. When building the application UI, developers use our libraries, which abstract the differences between the native platforms.

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.