3 ms·
You're right that we need to provide some better comparisons here, but the big reason that I'm excited about making individual components easier to adopt isn't
by ethomson 8y ago
You're right that we need to provide some better comparisons here, but the big reason that I'm excited about making individual components easier to adopt isn't for competition, it's to help people round out what they're missing in a dev tools stack.
There's a lot of shops that are happy with their git hosting provider and their agile planning tool and go looking for a CI/CD tool and may have been turned off by VSTS because it looked like a monolith. Making it clear that you can just use Azure Pipelines without having to use the entire stack was a priority for us, but you're absolutely right that we need to round this out with some better case studies. Thanks for the feedback.
- solatic 8y agoYeah that would be a good start. There's clear value-add here for on-prem teams which are starting to move to the cloud, by making it easier to run builds both on Azure and on-prem (seeing the $15/month pricing per agent) from the same cloud-based product, which I don't think anybody else is doing yet? But there doesn't seem to be any documentation about how to get that set up? It would definitely help to see comparisons against competition, e.g. GitLab, CircleCI
- ethomson 8y agoYeah - the hybrid cloud and on-premises build agents is actually one of my favorite features. The open source project that I help maintain (libgit2) uses VSTS's hosted Linux, Windows and macOS build agents, but add support for some other platforms (like ARM) with on-premises build agents. ("On-premises build agents" makes it sound fancier than it is, it's actually Raspberry Pi's on my desk, but hey, whatever works, right?)