Need advice about which tool to choose?Ask the StackShare community!
Get Advice from developers at your company using StackShare Enterprise. Sign up for StackShare Enterprise.
Learn MorePros of Buildkite
Pros of TeamCity
Pros of Travis CI
Pros of Buildkite
- Great customer support18
- Github integration17
- Easy to use16
- Easy setup16
- Simplicity12
- Simple deployments10
- Simple and powerful configuration9
- Bitbucket integration4
- Github enterprise integration3
- Amazing swag3
- Integrates with everything2
- Sourcecode is hosted by source code owner.1
- Configuration in cloud1
- Run your own test containers with their AWS stack file1
- Superior user experience1
- Great ui1
Pros of TeamCity
- Easy to configure61
- Reliable and high-quality37
- User friendly32
- On premise32
- Github integration32
- Great UI18
- Smart16
- Free for open source12
- Can run jobs in parallel12
- Crossplatform8
- Chain dependencies5
- Fully-functional out of the box5
- Great support by jetbrains4
- REST API4
- Projects hierarchy4
- 100+ plugins4
- Personal notifications3
- Free for small teams3
- Build templates3
- Per-project permissions3
- Upload build artifacts2
- Smart build failure analysis and tracking2
- Ide plugins2
- GitLab integration2
- Artifact dependencies2
- Official reliable support2
- Build progress messages promoting from running process2
- Repository-stored, full settings dsl with ide support1
- Built-in artifacts repository1
- Powerful build chains / pipelines1
- TeamCity Professional is FREE1
- High-Availability0
- Hosted internally0
Pros of Travis CI
- Github integration506
- Free for open source388
- Easy to get started271
- Nice interface191
- Automatic deployment162
- Tutorials for each programming language72
- Friendly folks40
- Support for multiple ruby versions29
- Osx support28
- Easy handling of secret keys24
- Fast builds6
- Support for students4
- The best tool for Open Source CI3
- Hosted3
- Build Matrices3
- Github Pull Request build2
- Straightforward Github/Coveralls integration2
- Easy of Usage2
- Integrates with everything2
- Caching resolved artifacts1
- Docker support1
- Great Documentation1
- Build matrix1
- No-brainer for CI1
- Debug build workflow1
- Ubuntu trusty is not supported1
- Free for students1
- Configuration saved with project repository1
- Multi-threaded run1
- Hipchat Integration1
- Perfect0
Sign up to add or upvote prosMake informed product decisions
Cons of Buildkite
Cons of TeamCity
Cons of Travis CI
Cons of Buildkite
Be the first to leave a con
Cons of TeamCity
- High costs for more than three build agents3
- Proprietary2
- User-friendly2
- User friendly2
Cons of Travis CI
- Can't be hosted insternally8
- Feature lacking3
- Unstable3
- Incomplete documentation for all platforms2
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?
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?
What tools integrate with TeamCity?
Sign up to get full access to all the tool integrationsMake informed product decisions
Blog Posts
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.