Need advice about which tool to choose?Ask the StackShare community!
Bitrise vs TeamCity: What are the differences?
Bitrise: Automate your mobile app development from building through testing to deployment. In short Bitrise is a Continous Integration and Delivery (CI/CD) Platform as a Service (PaaS) with a main focus on mobile app development (iOS, Android). You can automate the testing and deployment of your apps with just a few clicks. When you trigger a build a Virtual Machine is assigned to host your build and your defined Workflow (series of Steps scripts) will be executed, step by step; 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.
Bitrise can be classified as a tool in the "Mobile Continuous Integration" category, while TeamCity is grouped under "Continuous Integration".
Some of the features offered by Bitrise are:
- Continuous Delivery
- Hosted Environment
- Customizable Workflows
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
"Easy setup" is the top reason why over 10 developers like Bitrise, 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 Bitrise is used by Bitrise, ZeeMee, and Multunus. TeamCity has a broader approval, being mentioned in 171 company stacks & 51 developers stacks; compared to Bitrise, which is listed in 29 company stacks and 14 developer stacks.
Pros of Bitrise
- Easy setup18
- Bitbucket Integration9
- Advanced Workflow configuration8
- Github Integration7
- Slack integration7
- Great tools for iOS and Android development5
- Friendly & Easy to use5
- Great support4
- Pricing by concurrency, not team size3
- Discounts for contributors2
- Fast Updates2
- Open Source2
- Fast Builds1
- Developer centric1
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
Sign up to add or upvote prosMake informed product decisions
Cons of Bitrise
Cons of TeamCity
- High costs for more than three build agents3
- Proprietary2
- User-friendly2
- User friendly2
Sign up to add or upvote consMake informed product decisions
What is Bitrise?
What is TeamCity?
Need advice about which tool to choose?Ask the StackShare community!
What companies use TeamCity?
Sign up to get full access to all the companiesMake informed product decisions
What tools integrate with TeamCity?
Sign up to get full access to all the tool integrationsMake informed product decisions
Blog Posts
+22
+46
+35