Strider vs Travis CI vs wercker

Need advice about which tool to choose?Ask the StackShare community!

Strider

21
38
+ 1
11
Travis CI

26K
6.6K
+ 1
1.7K
wercker

365
157
+ 1
242
Get Advice from developers at your company using StackShare Enterprise. Sign up for StackShare Enterprise.
Learn More
Pros of Strider
Pros of Travis CI
Pros of wercker
  • 6
    Free Open Source
  • 5
    Hosted Internally
  • 506
    Github integration
  • 388
    Free for open source
  • 271
    Easy to get started
  • 191
    Nice interface
  • 162
    Automatic deployment
  • 72
    Tutorials for each programming language
  • 40
    Friendly folks
  • 29
    Support for multiple ruby versions
  • 28
    Osx support
  • 24
    Easy handling of secret keys
  • 6
    Fast builds
  • 4
    Support for students
  • 3
    The best tool for Open Source CI
  • 3
    Hosted
  • 3
    Build Matrices
  • 2
    Github Pull Request build
  • 2
    Straightforward Github/Coveralls integration
  • 2
    Easy of Usage
  • 2
    Integrates with everything
  • 1
    Caching resolved artifacts
  • 1
    Docker support
  • 1
    Great Documentation
  • 1
    Build matrix
  • 1
    No-brainer for CI
  • 1
    Debug build workflow
  • 1
    Ubuntu trusty is not supported
  • 1
    Free for students
  • 1
    Configuration saved with project repository
  • 1
    Multi-threaded run
  • 1
    Hipchat Integration
  • 0
    Perfect
  • 35
    Automatic Deployments
  • 33
    Free
  • 25
    Easy config via yaml
  • 23
    Awesome UI
  • 23
    Github integration
  • 22
    Continuous Deployment
  • 16
    Supports both Github and Bitbucket
  • 14
    Easy to setup
  • 12
    Reliable
  • 11
    Bitbucket Integration
  • 4
    Community-driven components (boxes and steps)
  • 4
    Fast builds
  • 4
    Easy to get started
  • 4
    Docker based
  • 3
    Easy UI
  • 3
    Flexible configuration via YAML
  • 2
    Multi-target deploys
  • 1
    Trigger by branch name
  • 1
    Great UI, free and an active Slack channel :)
  • 1
    Docker support
  • 1
    Multiple configurable build steps

Sign up to add or upvote prosMake informed product decisions

Cons of Strider
Cons of Travis CI
Cons of wercker
    Be the first to leave a con
    • 8
      Can't be hosted insternally
    • 3
      Feature lacking
    • 3
      Unstable
    • 2
      Incomplete documentation for all platforms
      Be the first to leave a con

      Sign up to add or upvote consMake informed product decisions

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

      What is Strider?

      Strider is an Open Source Continuous Deployment / Continuous Integration platform. It is written in Node.JS / JavaScript and uses MongoDB as a backing store. It is published under the BSD license.

      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.

      Need advice about which tool to choose?Ask the StackShare community!

      Jobs that mention Strider, Travis CI, and wercker as a desired skillset
      What companies use Strider?
      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 Strider?
      What tools integrate with Travis CI?
      What tools integrate with wercker?
        No integrations found

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

        Blog Posts

        What are some alternatives to Strider, 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.
        GitHub Actions
        It makes it easy to automate all your software workflows, now with world-class CI/CD. Build, test, and deploy your code right from GitHub. Make code reviews, branch management, and issue triaging work the way you want.
        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.
        Azure Pipelines
        Fast builds with parallel jobs and test execution. Use container jobs to create consistent and reliable builds with the exact tools you need. Create new containers with ease and push them to any registry.
        See all alternatives