Buildkite vs TeamCity vs Travis CI

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

Buildkite

212
228
+ 1
115
TeamCity

1.2K
1.1K
+ 1
316
Travis CI

27.6K
6.6K
+ 1
1.7K
Get Advice from developers at your company using StackShare Enterprise. Sign up for StackShare Enterprise.
Learn More
Pros of Buildkite
Pros of TeamCity
Pros of Travis CI
  • 18
    Great customer support
  • 17
    Github integration
  • 16
    Easy to use
  • 16
    Easy setup
  • 12
    Simplicity
  • 10
    Simple deployments
  • 9
    Simple and powerful configuration
  • 4
    Bitbucket integration
  • 3
    Github enterprise integration
  • 3
    Amazing swag
  • 2
    Integrates with everything
  • 1
    Sourcecode is hosted by source code owner.
  • 1
    Configuration in cloud
  • 1
    Run your own test containers with their AWS stack file
  • 1
    Superior user experience
  • 1
    Great ui
  • 61
    Easy to configure
  • 37
    Reliable and high-quality
  • 32
    User friendly
  • 32
    On premise
  • 32
    Github integration
  • 18
    Great UI
  • 16
    Smart
  • 12
    Free for open source
  • 12
    Can run jobs in parallel
  • 8
    Crossplatform
  • 5
    Chain dependencies
  • 5
    Fully-functional out of the box
  • 4
    Great support by jetbrains
  • 4
    REST API
  • 4
    Projects hierarchy
  • 4
    100+ plugins
  • 3
    Personal notifications
  • 3
    Free for small teams
  • 3
    Build templates
  • 3
    Per-project permissions
  • 2
    Upload build artifacts
  • 2
    Smart build failure analysis and tracking
  • 2
    Ide plugins
  • 2
    GitLab integration
  • 2
    Artifact dependencies
  • 2
    Official reliable support
  • 2
    Build progress messages promoting from running process
  • 1
    Repository-stored, full settings dsl with ide support
  • 1
    Built-in artifacts repository
  • 1
    Powerful build chains / pipelines
  • 1
    TeamCity Professional is FREE
  • 0
    High-Availability
  • 0
    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

Sign up to add or upvote prosMake informed product decisions

Cons of Buildkite
Cons of TeamCity
Cons of Travis CI
    Be the first to leave a con
    • 3
      High costs for more than three build agents
    • 2
      Proprietary
    • 2
      User-friendly
    • 2
      User friendly
    • 8
      Can't be hosted insternally
    • 3
      Feature lacking
    • 3
      Unstable
    • 2
      Incomplete documentation for all platforms

    Sign up to add or upvote consMake informed product decisions

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

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

    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.

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

    Jobs that mention Buildkite, TeamCity, and Travis CI as a desired skillset
    What companies use Buildkite?
    What companies use TeamCity?
    What companies use Travis CI?

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

    What tools integrate with Buildkite?
    What tools integrate with TeamCity?
    What tools integrate with Travis CI?

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

    Blog Posts

    GitHubDockerReact+17
    40
    36169
    Jun 26 2018 at 3:26AM

    Twilio SendGrid

    GitHubDockerKafka+10
    11
    9938
    GitHubPythonReact+42
    49
    40691
    GitHubPythonNode.js+47
    54
    72281
    What are some alternatives to Buildkite, TeamCity, and Travis CI?
    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.
    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.
    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.
    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.
    See all alternatives