What do you dislike about Azure DevOps Server?
I am always encountering problems with TFSVC and we have so many projects that the team is afraid to convert to fully to git. Here are some of the issues I've encountered recently:
* TFSVC: Commits through Visual Studio regularly complain that the commit failed and code was auto-merged, so try again (no indication of what was auto-merged)
* TFSVC: Auto-generating version numbers from changesets (via MSBuild Community Tasks TFSClient) often results in a 'tfs.exe exited with code 100' error and the only fix is to build projects serially
* TFS Web Access: Clearing cookies in Chrome after TFS2015 Update 1 results in TFS being unusable for me in Chrome, so I have to use IE (which I hate)
* TFS: TFS doesn't intuitively associate Code Reviews, Changesets, and other Work Items, making it a huge pain to report on these as a whole
* TFS: Customizing process templates is a huge pain. For example, we've added code review tabs to user stories and tasks to track collaboration and the only way to hook up code reviews to these items is as a 'Related' item
* TFS: While vso plugins are 'getting there', it is still a struggle to integrate a lot of the open source community tools we use (karma, protractor, cucumber, etc.)
* TFS: Configuring new agents and their 'system variables' is not well documented
* TFS: In general TFS requires a lot more overhead than using GitHub Enterprise as I did with a previous employer. However, TFS gives you reporting, built-in proprietary testing tools, and a slew of other things you wouldn't get immediately with GitHub.
* TFSVC: From a development perspective, I spend more time getting TFSVC to do what I want it to do than I ever did with git Review collected by and hosted on G2.com.