41–50 of 92 posts
"Implement continuous delivery (CD) of your software to any cloud, including Azure, AWS, and GCP." Interesting move!
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 f…
But we have never said that this was Azure's fault. It wasn't. We've put the blame where it belongs: on us. We're nearly done writing up the root cause analysis and an analysis of our next steps to prevent this from happening in the future.
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 f…
I certainly hope not. I'm not going to argue that this was anything but a disappointment to our customers - and one that we're eager to prevent from happening again. But we have never said that this was Azure's fault. It wasn't. We've put the blame where it belongs: on us. We're nearly done writing up the root cause analysis and an analysis of our next steps to prevent this from happening in the future.
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?
PM for Azure DevOps here (formerly VSTS). It is a rebranding, but it's more than merely a rebranding. We're breaking out the individual services so that they're easier to adopt. For example, if you're just interested in pipelines, you can adopt only pipelines. We've got some neat new features launching today and more coming soon. My favorite new feature is the Azure Pipelines app the the GitHub Marketplace. It makes…
Earlier quoted context omitted.
I certainly hope not. I'm not going to argue that this was anything but a disappointment to our customers - and one that we're eager to prevent from happening again. But we have never said that this was Azure's fault. It wasn't. We've put the blame where it belongs: on us. We're nearly done writing up the root cause analysis and an analysis of our next steps to prevent this from happening in the future.
Do you happen to know where the root cause analysis will be posted if it is made public?
Earlier quoted context omitted.
[PM on the Azure Pipelines team] The primary focus here is making the individual services easier for teams to adopt. Azure pipelines for CI/CD, Azure Boards for planning, etc. Those services support the overall goal of improving your DevOps practices.
I see that this is more than a rebranding and was just commenting with my immediate, fatuous response. I should save fatuous responses for reddit.
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.
I own skmexyz.visualstudio.com (under sk@skme.xyz account) and I tried to transfer it to skmexyz@skmexyz.onmicrosoft.com and now:
1. Both accounts are not admins so I can't delete / modify it (it asks me to contact the administrator when I am obviously the administrator)
2. It claims that it's being managed by Default Directory on Azure but I can't appear do anything with it.
I would really appreciate some help with it.
Earlier quoted context omitted.
PM for Azure DevOps here (formerly VSTS). It is a rebranding, but it's more than merely a rebranding. We're breaking out the individual services so that they're easier to adopt. For example, if you're just interested in pipelines, you can adopt only pipelines. We've got some neat new features launching today and more coming soon. My favorite new feature is the Azure Pipelines app the the GitHub Marketplace. It makes…
I assume "Azure Boards" is the same thing as Planner in Office 365? Is there any specific changes between the two, like for example can you point a changeset at an Azure Boards item from within Visual Studio?
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.
Just drop the "dev" and call it AzureOps. Still way less confusing than the prior branding.
Earlier quoted context omitted.
PM for Azure DevOps here (formerly VSTS). It is a rebranding, but it's more than merely a rebranding. We're breaking out the individual services so that they're easier to adopt. For example, if you're just interested in pipelines, you can adopt only pipelines. We've got some neat new features launching today and more coming soon. My favorite new feature is the Azure Pipelines app the the GitHub Marketplace. It makes…
Does the "pipelines" service support deploying to Kubernetes clusters other than AKS? If/when it does then you have a very compelling service.