Introducing Azure DevOps
azure.microsoft.com
Introducing Azure DevOps
1–10 of 92 posts
Re: Introducing Azure DevOps
#2Is 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?
Re: Introducing Azure DevOps
#3Is 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?
This is a rebranding yes.
VSTS was a bad name that confused potential customers because they thought of the IDE, and so no one really knew what the product was from the name alone.
(Work on VSTS team)
Re: Introducing Azure DevOps
#4Is 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?
it looks like rebrand + redesign + decoupling the individual services so they're easier to adopt independently?
Re: Introducing Azure DevOps
#5Is 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 it one-click to build a continuous integration and pull request validation pipeline right from your GitHub repository, you don't even need an Azure DevOps account to get started.
Re: Introducing Azure DevOps
#6Is 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…
If the point of the rebranding is to help drive adoption of the individual components of what used to make up VSTS, then it seems to me like the strategy is to try and get people to switch from pre-existing toolsets to Azure tooling.
Maybe it would be more persuasive if you could show some kind of comparison or case study for switching? For instance, if you want to make it easier for people to adopt Azure Boards, then why should they adopt Azure Boards over the myriad other agile planning products out there?
More importantly, if you're trying to make individual services easier to adopt, why is there only unified Azure DevOps pricing and not pricing solely for the individualized products (excepting Azure Pipelines pricing, which is a per-agent pricing model)?
Re: Introducing Azure DevOps
#7The 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.
Re: Introducing Azure DevOps
#8A new velvet cushion filled with the same old sawdust and horsehair.
Re: Introducing Azure DevOps
#9Is 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?
Part of the change is 10 free parallel build jobs on Linux, macOS, and Windows for open source projects.
Re: Introducing Azure DevOps
#10Is 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?
it looks like rebrand + redesign + decoupling the individual services so they're easier to adopt independently?
Yes that's right + free pipeline for OSS project. From: PM for Azure DevOps here (formerly VSTS)