Add to Chrome
Add to Edge
Add to Firefox
Add to Opera
Add to Brave
Add to SafariWhen comparing TeamCity vs Nevercode, the Slant community recommends Nevercode for most people. In the question“What are the best continuous integration tools for mobile app developers?” Nevercode is ranked 4th while TeamCity is ranked 6th. The most important reason people chose Nevercode is:
Simulating or emulating tests is good - actually testing on real hardware is better as you'll catch device (manufacturer) specific issues that would kill your app ratings in the wild.
Specs
Question Ranking
Pros
Pro Easy installation
TeamCity has different installation packages for different operating systems. All the user needs to do is download the correct one and run it.
Pro Cross-platform build support
The fact that it is based on Java does not hinder TeamCity's ability to support different build environments. TeamCity in fact supports a large number of languages and tools for each of those languages (build runners and test frameworks).
Some of the languages/platforms that are supported include: Ruby, .NET, Java.
Pro Brilliant interface
The user interface of TeamCity is clear, well thought out and the dashboard is highly customizable.
Pro Supports build chains
The user can easily compose dependencies between builds by adding snapshot and artifact dependencies, all on the one screen. All output of upstream builds is available to downstream builds. Triggering sets off the entire build chain and supports re-running of the portions of the chain that failed.
Pro Well documented
Pro Extensible
TeamCity offers well defined APIs for extending, as well as a REST interface.
Pro Testing support
TeamCity supports both MSTest and NUnit (which is open source) to run tests.
Pro Best choice for .NET
Seems to be the best choice for .NET applications, but to be honest: if you stray from the default settings you will be in a lot of pain most of the time.
Pro Ability to run tests on real devices
Simulating or emulating tests is good - actually testing on real hardware is better as you'll catch device (manufacturer) specific issues that would kill your app ratings in the wild.
Pro Multiple integrations to cover your needs
Simplifies the instant access to the latest state of your apps.
Pro Easy to setup
There's no configuration files to write, nothing to download or install, nothing to really configure. Setting it up takes basically only adding your Git repository and waiting for the clone, build and test to finish.
Pro Focused on mobile app development
It's dedicated to mobile platforms and supports Andorid, iOS native apps + a couple of cross-platform frameworks such as Cordova and Ionic.
Cons
Con Expensive
TeamCity has a free tier which includes a maximum of 100 build configurations and up to 3 build agents. If you want to add 10 more configurations and 1 more agent, it will cost $299; unless you choose to buy an enterprise license which starts at $1999.
Con Poor quality plugins
At least some of them do not work, probably because they're not updated to more recent TeamCity versions.
Con Inter-branch merges trigger emails to unrelated committers
Whenever an inter-branch merge occurs, TeamCity pulls up the first parent of the merge commit and sends them an e-mail. However, this sort of information would be more useful to the merge author.
Con Project settings view could have a better UX to make it simpler for new users
Con Inflexible, can't implement multiple build tasks or target multiple modules
