Get Advice Icon

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

Shippable vs TeamCity: What are the differences?

Shippable: Shippable is a SaaS platform that lets you easily add Continuous Integration/Deployment to your Github & Bitbucket repos. 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; TeamCity: TeamCity is an ultimate Continuous Integration tool for professionals. 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.

Shippable and TeamCity belong to "Continuous Integration" category of the tech stack.

Some of the features offered by Shippable are:

  • 1-Click Setup
  • Docker Containers
  • Responsive UI

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

  • Automate code analyzing, compiling, and testing processes, with having instant feedback on build progress, problems, and test failures, all in a simple, intuitive web-interface
  • Simplified setup: create projects from just a VCS repository URL
  • Run multiple builds and tests under different configurations and platforms simultaneously

"Free private repositories" is the top reason why over 17 developers like Shippable, while over 52 developers mention "Easy to configure" as the leading cause for choosing TeamCity.

Stack Exchange, ebay, and Apple are some of the popular companies that use TeamCity, whereas Shippable is used by esa, Reviewable, and Algorithmia. TeamCity has a broader approval, being mentioned in 171 company stacks & 51 developers stacks; compared to Shippable, which is listed in 24 company stacks and 4 developer stacks.

Manage your open source components, licenses, and vulnerabilities
Learn More

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

Blog Posts

What are some alternatives to ?
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.
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.
Concourse
Concourse's principles reduce the risk of switching to and from Concourse, by encouraging practices that decouple your project from your CI's little details, and keeping all configuration in declarative files that can be checked into version control.