When comparing Strider vs TeamCity, the Slant community recommends TeamCity for most people. In the question“What are the best self-hosted continuous integration tools?” TeamCity is ranked 1st while Strider is ranked 5th. The most important reason people chose TeamCity is:
TeamCity has different installation packages for different operating systems. All the user needs to do is download the correct one and run it.
Specs
Ranked in these QuestionsQuestion Ranking
Pros
Pro Fast, fun combat
Strider is a really fast-paced side-scrolling hack and slash. The enemies will never stop trying to shoot your or end you in any way possible. This could easily become punishingly difficult, but is avoided thanks to the very responsive controls. You'll scale walls and kill groups of enemies within seconds, which truly makes you feel like an assassin with inhuman reflexes.
The boss fights increase the tempo and may seem really cheap at first. Luckily, you'll learn their abilities over time, which will allow you to predict and counter them all. Defeating a boss without taking a single hit feels incredibly satisfying.
Pro Tons of collectibles
You can find new upgrades, concept art, story info, character info, and costumes during the game. There are also hidden challenges such as Survival and Beacon. Only the upgrades are marked on the map, so the rest can be difficult to find, making 100% completion a tough goal to reach.
Pro Big game world that rewards exploration
The world of Strider is massive city where you'll be climbing a lot of high walls and tall buildings. It also hides a lot of upgrades that will help you clear a level or beat a boss a lot easier. Most of these can only be accessed later when you have the right type of weapon (similar to Metroid Prime). So you'll be spending a lot of time exploring (backtracking) if you decide to access these new locations.
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.
Cons
Con Cannot skip pre-boss chatter
This is not an issue if you don't die to a boss, but if you do, you have to sit through their introduction and banter every time. You cannot skip talk scenes you've already seen. The final boss, in particular, is quite the chatter-box.
Con No "Fast-Travel" really
It is a big game world, and most of the time you are stuck exploring it all by foot. There is something that lets you travel between areas, but they are few and far between and not really all that helpful. Plus, it is unlocked fairly late into the game. If you know there is something you need to return to on the other side of the game, you are in for a good hike.
Con Story is not explained
Strider has a very simple "good guy defeats evil tyrant" type of story, but none of the characters are truly fleshed out.
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.