They treat Git as first class citizens.
They treat Git as first class citizens.
Beyond that, the new build tooling isn’t half bad - leaps and bounds ahead of the nasty XML nightmare which is why our team has been moving back to it from out TeamCity deployment.
Most of my gripes with VSTS are around the rest of it, everything under “Work” has barely been touched since TFS 2012 - it got a coat of paint but it’s still the same enterprise-grade turd that makes me yearn for JetBrains YouTrack every day. They’ve had adequate git support for a while but the web-based repository browser is such a chore to use that I end up cloning a repository to do a quick search more often than I should need, the admin interface is still a mess to navigate, the list goes on.
Your build and deployments are just a JSON file that you can export and import either from the web or the API.
The other parts of VSTS are obtuse. But since my chosen workflow is Kanban, it's quite easy to setup a Kanban board with WIP Limits.
What I really hate is the Wiki. It supports basic Markdown without all of the bells and whistles of Atlassian but its okay.
The Wiki is pretty terrible too, but I’ve never found a wiki that makes me go “wow, this is AWESOME” either - dokuwiki got reasonably close though because it gets the hell out of the way and offers just enough formatting without letting me choke on markup like MediaWiki or the WYSINWYG hell of Confluence.
The build supports anything - by virtue of the fact that you can run executables, Powershell scripts, batch files, etc.
Releases on the other hand, I could see a need to change more frequently. If that's your desire, there is nothing stopping you from having one release step that runs a Powershell script, Cake script, etc that is run from your repo.