Visual Studio Team Services - an agile workflow and CD/CI toolchain.
March 06, 2018
Visual Studio Team Services - an agile workflow and CD/CI toolchain.
Score 10 out of 10
Vetted Review
Verified User
Overall Satisfaction with Microsoft Visual Studio Team System
Using VSTS in an agile fashion, we are using the change management features like view history, view changesets, compare, create shelvesets, and to create work items. We optionally could use VSTS for continuous integration/delivery to Azure, but the expense far outweighs AWS. VSTS has made us into a .net shop that is useful for checking in artifacts from Example Author, Microsoft Office/365, or other third party vendors.
- Change management
- Continuous integration/delivery, automate application deployment
- Code reviews, conduct a design review
- VSTS online code editor
- Complete Azure integration
- Distributed workflow
- Cost
- More robust API
- More straightforward comparison tool
- Collaboration tools cut down on discrepancies between codebases. Time saver.
- Prohibitive cost. An open source alternative would be a great way to discover the benefits of the full version of VSTS.
- Hard to get acquainted with starting out, but makes sense after a few days. Obviously the Visual Studio IDE integration is top-notch.
Easier to use than GitHub, but it comes at a cost. Although you can script VSTS, the online version could use a more substantial editor. Those who remember project Monaco and its current implementation in Azure, App Service Editor, will be disappointed if looking for more of an Apache Orion-like online editor.