Travis CI vs Webpack

Overview

Travis CI

Stacks28.0K

Followers6.7K

Votes1.7K

Webpack

Stacks45.0K

Followers28.1K

Votes752

GitHub Stars65.7K

Forks9.2K

Travis CI vs Webpack: What are the differences?

What is 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.

What is Webpack? A bundler for javascript and friends. A bundler for javascript and friends. Packs many modules into a few bundled assets. Code Splitting allows to load parts for the application on demand. Through "loaders" modules can be CommonJs, AMD, ES6 modules, CSS, Images, JSON, Coffeescript, LESS, ... and your custom stuff.

Travis CI and Webpack are primarily classified as "Continuous Integration" and "JS Build Tools / JS Task Runners" tools respectively.

"Github integration", "Free for open source" and "Easy to get started" are the key factors why developers consider Travis CI; whereas "Most powerful bundler", "Built-in dev server with livereload" and "Can handle all types of assets" are the primary reasons why Webpack is favored.

Webpack is an open source tool with 49.8K GitHub stars and 6.27K GitHub forks. Here's a link to Webpack's open source repository on GitHub.

Airbnb, Instagram, and Pinterest are some of the popular companies that use Webpack, whereas Travis CI is used by Lyft, Heroku, and Rainist. Webpack has a broader approval, being mentioned in 2206 company stacks & 1338 developers stacks; compared to Travis CI, which is listed in 670 company stacks and 624 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, Webpack

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

Aleksandr

Contract Software Engineer - Microsoft at Microsoft-365

Dec 23, 2019

Decided

Why migrated?

I could define the next points why we have to migrate:

Decrease build time of our application. (It was the main cause).
Also jspm install takes much more time than npm install.
Many config files for SystemJS and JSPM. For Webpack you can use just one main config file, and you can use some separate config files for specific builds using inheritance and merge them.

301k views301k

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?"

530k views530k

Comments

Detailed Comparison

Travis CI	Webpack
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.	A bundler for javascript and friends. Packs many modules into a few bundled assets. Code Splitting allows to load parts for the application on demand. Through "loaders" modules can be CommonJs, AMD, ES6 modules, CSS, Images, JSON, Coffeescript, LESS, ... and your custom stuff.
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.	Bundles ES Modules, CommonJS, and AMD modules (even combined); Can create a single bundle or multiple chunks that are asynchronously loaded at runtime (to reduce initial loading time); Dependencies are resolved during compilation, reducing the runtime size; Loaders can preprocess files while compiling, e.g. TypeScript to JavaScript, Handlebars strings to compiled functions, images to Base64, etc; Highly modular plugin system to do whatever else your application requires
Statistics
GitHub Stars -	GitHub Stars 65.7K
GitHub Forks -	GitHub Forks 9.2K
Stacks 28.0K	Stacks 45.0K
Followers 6.7K	Followers 28.1K
Votes 1.7K	Votes 752
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 309 Most powerful bundler 182 Built-in dev server with livereload 142 Can handle all types of assets 87 Easy configuration 22 Laravel-mix Cons 15 Hard to configure 5 No clear direction 2 Fire and Forget mentality of Core-Developers 2 Loader architecture is quite a mess (unreliable/buggy) 2 Spaghetti-Code out of the box
Integrations
Amazon S3 Heroku AWS CodeDeploy MySQL Red Hat OpenShift Nodejitsu npm GitHub Engine Yard Cloud cloudControl	JavaScript

What are some alternatives to Travis CI, Webpack?

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.

gulp

Build system automating tasks: minification and copying of all JavaScript files, static images. More capable of watching files to automatically rerun the task when a file changes.

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.

Grunt

The less work you have to do when performing repetitive tasks like minification, compilation, unit testing, linting, etc, the easier your job becomes. After you've configured it, a task runner can do most of that mundane work for you—and your team—with basically zero effort.

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.

Related Comparisons

Webpack is an open source tool with 49.8K GitHub stars and 6.27K GitHub forks. Here's a link to Webpack's open source repository on GitHub.

Travis CI vs Webpack