4 ms·
I've been using VSTS (Visual Studio Team Services) for a few years now, and I think it's great. But this looks like they've just changed the URL and stuck the
by GordonS 8y ago
I've been using VSTS (Visual Studio Team Services) for a few years now, and I think it's great.
But this looks like they've just changed the URL and stuck the name "Azure DevOps" onto the VSTS site? Even the pricing and plans seem to be the same - I really don't get how they're talking like they're launching something new, rather than just having a rebranding exercise after buying GitHub.
- tarekmadkour 8y agoRebranding is part of it. Also: * Pipelines is a stand-alone service that can be acquired and used separately * Pipelines can be directly acquired and configured from the GitHub marketplace * Pipelines is effectively free to use for open source * Pipelines free limits have been significantly increased for private projects * Other Azure DevOps services (e.g. Boards) can now be used separately, too
- manigandham 8y agoThat's exactly what it is: https://visualstudio.microsoft.com/team-services/ https://visualstudio.microsoft.com/team-services/ Although there have been slight tweaks and UI/UX updates.
- GordonS 8y agoThere have already been quite a lot of UI/UX updates over the past 6 months of so. TBH, I kind of wish you'd leave it the hell alone for a bit! In particular, I'm not a fan of the most recent changes to the 'build and release' pages. To edit the build pipeline, the edit link is at the top of the list of builds, rather than at the top of the list of build pipelines... I end up searching for the link every. single. time :(
- manigandham 8y agoI don't work on it, you should reply to the PM on this page or reach them via twitter/email to discuss further. Seems they are willing to listen: https://news.ycombinator.com/item?id=17953476 https://news.ycombinator.com/item?id=17953476
- ethomson 8y agoAt the risk of sounding philosophical, when you're building a cloud service that gets continuous delivery of features... when is that simply an iteration, versus something new? Anyway, I'm not a philosopher. But I don't think that this is simply a "rebranding exercise", and it's been in the works for quite a while; it's not related to GitHub (which, for the record, we have not yet acquired). We've made a huge engineering effort into the individual components that make up Azure DevOps, and those deserve (in my opinion) to be recognized. So, now "Azure Pipelines" gets to shine on its own.