I'm an active teamcity user (and a jetbrains fan in general). I work in games, and we compile C++ on windows & linux for multiple platforms using 8/16/32 core machines, so BYOW is super important for us. I'd like to use Buildkite but they don't support Perforce, so our choices are Bamboo, TeamCity and Jenkins.
With that said, I can't see us switching to this TeamCity Cloud with its current pricing model. Paying per agent _and_ per user is double dipping, and the pricing of both of them is moderately expensive to boot. Top that off with monthly expiring credits for their hosted runners (which would be helpful for running deploys on), it seems to me they've totally missed the mark - compared to BuildKite for example!
1 comment
[ 3.2 ms ] story [ 7.6 ms ] threadWith that said, I can't see us switching to this TeamCity Cloud with its current pricing model. Paying per agent _and_ per user is double dipping, and the pricing of both of them is moderately expensive to boot. Top that off with monthly expiring credits for their hosted runners (which would be helpful for running deploys on), it seems to me they've totally missed the mark - compared to BuildKite for example!