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.
Introducing Azure DevOps
21–30 of 92 posts
Re: Introducing Azure DevOps
#22"Implement continuous delivery (CD) of your software to any cloud, including Azure, AWS, and GCP."
Interesting move!
Re: Introducing Azure DevOps
#23Is 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…
As a mostly very satisfied user, I gotta say, y'all have a great product. The CI/CD part of VSTS (I like the old name better :P) is killer and by far my favorite platform to use now. However, I've had my builds break twice out of nowhere with no recourse other than submitting a forum post and hoping someone gets back to me in a reasonable amount of time. I can't imagine going back to another platform, but its really frustrating when your production release process for a client is completely down and you have no way to fix it. Is there a way to get better support in those scenarios?
Re: Introducing Azure DevOps
#24The 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.
The discipline broadly described as "DevOps engineering" is just a way for employers to get senior staff to do the work that really should be handled by multiple, narrower disciplines (e.g., security engineers, automation engineers, tooling engineers, etc.) for a lower cost.
Re: Introducing Azure DevOps
#25I'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!
Re: Introducing Azure DevOps
#26The 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.
The discipline broadly described as "DevOps engineering" is just a way for employers to get senior staff to do the work that really should be handled by multiple, narrower disciplines (e.g., security engineers, automation engineers, tooling engineers, etc.) for a lower cost.
[deleted]
Re: Introducing Azure DevOps
#27Earlier quoted context omitted.
> But what happens when if the DevOps concept turns out to be a fad? Time to re-rebrand
[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.
Re: Introducing Azure DevOps
#28Still 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.
The yawn was really not necessary.
Re: Introducing Azure DevOps
#29Earlier 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…
As a mostly very satisfied user, I gotta say, y'all have a great product. The CI/CD part of VSTS (I like the old name better :P) is killer and by far my favorite platform to use now. However, I've had my builds break twice out of nowhere with no recourse other than submitting a forum post and hoping someone gets back to me in a reasonable amount of time. I can't imagine going back to another platform, but its really…
I'm sorry to hear that - without knowing more about how it broke, it's hard for me to say. Can you give me some more information about how it's broken in the past? Links to the forums posts would be great. Probably the best way to get them to me is by email, it's my HN name @microsoft.com.
Re: Introducing Azure DevOps
#30The 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.
[deleted]