Travis CI
Travis CI

4.2K
2.9K
1.7K
wercker
wercker

164
135
242
Add tool

Travis CI vs wercker: What are the differences?

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; wercker: Build, test, and deploy container-native applications. Wercker is a CI/CD developer automation platform designed for Microservices & Container Architecture.

Travis CI and wercker belong to "Continuous Integration" category of the tech stack.

Some of the features offered by Travis CI are:

  • 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.

On the other hand, wercker provides the following key features:

  • Pipelines - Wercker's Pipelines enable developers to fully automate builds, tests and deployments with Docker as a first class citizen.
  • Workflows - With Workflows: a collection of pipelines can be chained and triggered to achieve complex automation goals.
  • Steps Store - A step is a self contained best practice for accomplishing a specific automation task. Build your own or help yourself to our community based store.

"Github integration" is the primary reason why developers consider Travis CI over the competitors, whereas "Automatic Deployments" was stated as the key factor in picking wercker.

According to the StackShare community, Travis CI has a broader approval, being mentioned in 670 company stacks & 624 developers stacks; compared to wercker, which is listed in 40 company stacks and 23 developer stacks.

- No public GitHub repository available -
- No public GitHub repository available -

What is Travis CI?

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

Wercker is a CI/CD developer automation platform designed for Microservices & Container Architecture.

Want advice about which of these to choose?Ask the StackShare community!

Why do developers choose Travis CI?
Why do developers choose wercker?

Sign up to add, upvote and see more prosMake informed product decisions

What are the cons of using Travis CI?
What are the cons of using wercker?
    Be the first to leave a con
    What companies use Travis CI?
    What companies use wercker?

    Sign up to get full access to all the companiesMake informed product decisions

    What tools integrate with Travis CI?
    What tools integrate with wercker?

    Sign up to get full access to all the tool integrationsMake informed product decisions

    What are some alternatives to Travis CI and wercker?
    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.
    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.
    GitLab CI
    GitLab offers a continuous integration service. If you add a .gitlab-ci.yml file to the root directory of your repository, and configure your GitLab project to use a Runner, then each merge request or push triggers your CI pipeline.
    GitLab
    GitLab offers git repository management, code reviews, issue tracking, activity feeds and wikis. Enterprises install GitLab on-premise and connect it with LDAP and Active Directory servers for secure authentication and authorization. A single GitLab server can handle more than 25,000 users but it is also possible to create a high availability setup with multiple active servers.
    Bamboo
    Focus on coding and count on Bamboo as your CI and build server! Create multi-stage build plans, set up triggers to start builds upon commits, and assign agents to your critical builds and deployments.
    See all alternatives
    Decisions about Travis CI and wercker
    No stack decisions found
    Interest over time
    Reviews of Travis CI and wercker
    Avatar of tschellenbach
    CEO at Stream
    Review ofTravis CITravis CI

    In the past we used to run Jenkins. The build server always had weird issues and was a pain to maintain. Travis is a great solution for CI. Their Debug build features makes it trivial to figure out why your build broke. The integration with Github is also very slick. One thing they could improve is the documentation on the .travis.yaml format. All in all, great company and very responsive supports. Over here at getstream.io we're a fan. Keep up the good work guys!

    How developers use Travis CI and wercker
    Avatar of datapile
    datapile uses Travis CITravis CI

    Travis CI is our pillar for automated deployment, pull request testing, auto-merging (for non-mission-critical projects), and build testing per commit / release.

    It is highly configurable, super cheap, and extremely robust (supports every language and configuration we've thrown at it).

    Avatar of Pēteris Caune
    Pēteris Caune uses Travis CITravis CI

    While we usually run tests before commits, Travis goes further and tests with different Python versions and different database backends. It works great, and, best of all, it is free for open source projects.

    Avatar of Dieter Adriaenssens
    Dieter Adriaenssens uses Travis CITravis CI

    Travis CI builds and tests every commit. It's also used to deploy Buildtime Trend as a Service to Heroku and the Buildtime Trend Python library to the PyPi repository.

    Avatar of Nate Ferrell
    Nate Ferrell uses Travis CITravis CI

    Travis CI is critical for Linux and macOS CI tests for the Powershell module. Travis runs the same tests we run in AppVeyor in parallel.

    Avatar of Andrew Williams
    Andrew Williams uses Travis CITravis CI

    To ensure that what works locally will also work for someone else. Also used to send code coverage to codeintel

    Avatar of James Bowman
    James Bowman uses werckerwercker

    Automatic generation and deployment of site

    Avatar of Ruben Timmerman
    Ruben Timmerman uses werckerwercker

    For automated testing and deployment

    How much does Travis CI cost?
    How much does wercker cost?
    Pricing unavailable
    News about wercker
    More news