by Someone1234 on 9/10/18, 5:30 PM
I wonder if Azure DevOps will have a day long outage like VSTS had last week? That had a legitimately productivity cost to a lot of companies, and the more vested in the VSTS toolchain you were the harder hit you were.
I'm legitimately surprised they're launching this so soon after that, particularly considering there's been no real post-mortem, and no update on how they'll stop this happening again.
"It is Azure's fault" isn't an answer, and re-branding this Azure DevOps makes that excuse almost hilarious. I'm well aware that Azure AD was down, and that VSTS has a strong dependency on it, but ultimately we're still talking about a single data center bringing down VSTS for all of North America for an entire work-day.
It has been a week and now they're trying to encourage you to push your whole deployment toolchain (manage, build, test) into their cloud.
by SamuelAdams on 9/10/18, 3:19 PM
Is this just a rebranding?
As a long time user of VSTS, I am failing to see how Azure DevOps is different from VSTS. Boards, CI/CD, testing - that's already part of VSTS, and has been for quite some time. Is Microsoft just rebranding for keyword searching or something? Or are there actual technical changes / new features that are being introduced?
by dsr_ on 9/10/18, 3:40 PM
The term "DevOps" is now meaningless. The search for a new short term to describe "operations and development teams working together using high quality software tools to define, automate and distribute configuration and management information, integrating QA, release management and security" has begun.
by jbigelow76 on 9/10/18, 3:50 PM
Eh, not a big fan of this, but if it's a just a rebrand no big deal I guess. But what happens when if the DevOps concept turns out to be a fad? Visual Studio has such a positive and strong brand association among .Net developers it seems a shame to jettison it but I suppose it's necessary as MS is trying to convince other stacks to use the Azure DevOps(VSTS) CI/CD pipelines.
by sorrymate on 9/10/18, 4:44 PM
I've been impressed by the ease of use for VSTS. We've adopted it for our team, and it has really reduced the friction in our CI/CD pipeline. We've been able to automate the entire process. It seemed to be easy to setup because there is a Task for just about anything you want to do. Shout out to the Azure DevOps (VSTS/TFS) team. Keep it up, nice work!
by 2-m3m3n70 on 9/10/18, 5:17 PM
I'd like to point out that it appears their Pipelines is the only hosted CI tool on the market that supports every platform. Are there any others?
by all_usernames on 9/10/18, 4:30 PM
"Implement continuous delivery (CD) of your software to any cloud, including Azure, AWS, and GCP."
Interesting move!
by styfle on 9/10/18, 6:22 PM
How many times has this thing been re-branded?
1. Team Foundation Server (TFS)
2. Visual Studio Team Services (VSTS)
3. Azure DevOps
Imagine if GitHub renamed itself every few years?
Or is the idea that this is going to be marketed towards Azure users and GitHub will be promoted to the new VSTS once it gets a few more features for project management and PRs?
https://twitter.com/styfle/status/1032702016064286720
by GordonS on 9/10/18, 6:21 PM
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.
by ethomson on 9/10/18, 5:33 PM
PM for Azure DevOps here. The team is really excited about this launch, and many of us are here to answer questions on Azure DevOps, or any of the individual services like Azure Pipelines, the new GitHub Marketplace app, or our free build offer for open source projects.
by rjbwork on 9/10/18, 4:30 PM
Still no Mercurial. yawn Really sucks to see Microsoft giving up on us Hg users, considering it was the only viable DVCS on windows for years until people finally got git working with a bunch of issues.
by ianceicys on 9/12/18, 1:08 AM
by deskamess on 9/10/18, 9:33 PM
Can MSDN subscribers apply their credit towards this service?
by itomato on 9/10/18, 3:42 PM
A new velvet cushion filled with the same old sawdust and horsehair.