3 ms·
Having never used TeamCity (but being intrigued), what's so bad about it?
by cglong 6y ago
Having never used TeamCity (but being intrigued), what's so bad about it?
- snuxoll 6y agoAs somebody who does like TeamCity - it can be a bit clunky to navigate around. It’s much like Zabbix in that once you figure it out it’s not a problem, but the learning curve for anything beyond basic use can be steep. I pretty much use Gitlab CI these days for anything outside my day job though, and the stuff at work is all Azure Pipelines (via Azure DevOps) now.
- anon73044 6y agoVariable scope and templates can get a little weird. At work we're experiencing several issues with triggers that don't kickoff when there are changes in the repo. Builds stuck for 2 hours or more on "Collecting changes". Builds that build from the default branch, even though they were called with a specific branch to build from. I could go on.
- AnthonBerg 6y agoI personally don't have any problems with the TeamCity UI. I've used it in anger over extended periods of time. It's appropriately complex given what it does, and presents things efficiently.