Introducing Azure DevOps • Hacker News Board

Re: Introducing Azure DevOps

#31

Post by all_usernames » Mon, Sep 10, 2018, 5:14 PM UTC

dsr_ wrote: post #7

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.

The discussion about how DevOps is an overloaded term is definitely now meaningless, in that it's been discussed ad nauseam.

In the meantime, interesting work continues to be done developing the ideas of DevOps and extending them.

[1] The Site Reliability Workbook, from Google, 2018 https://books.google.com/books?id=fElmDwAAQBAJ

[2] Securing DevOps, Julien Vehent, 2018 https://www.manning.com/books/securing-devops

Re: Introducing Azure DevOps

#32

Post by 2-m3m3n70 » Mon, Sep 10, 2018, 5:17 PM UTC

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?

Re: Introducing Azure DevOps

#33

Post by partiallypro » Mon, Sep 10, 2018, 5:17 PM UTC

jbigelow76 wrote: post #12

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.

Re: Introducing Azure DevOps

#34

Post by Someone1234 » Mon, Sep 10, 2018, 5:22 PM UTC

ethomson wrote: post #5

SamuelAdams wrote: post #2

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…

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?

Re: Introducing Azure DevOps

#35

Post by samstave » Mon, Sep 10, 2018, 5:24 PM UTC

dsr_ wrote: post #7

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.

That is a great sentence, thanks for writing that.

I personally dont like the term devops either... I prefer a more specific definition fo a role.

Re: Introducing Azure DevOps

#36

Post by Someone1234 » Mon, Sep 10, 2018, 5:30 PM UTC

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.

Re: Introducing Azure DevOps

#37

Post by ethomson » Mon, Sep 10, 2018, 5:33 PM UTC

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.

Re: Introducing Azure DevOps

#38

Post by dsr_ » Mon, Sep 10, 2018, 5:36 PM UTC

bovermyer wrote: post #24

dsr_ wrote: post #7

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.

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.

Perhaps you would re-read what I wrote? I didn't suggest that people should add more hats -- I suggested that people should cooperate more, and learn from each other.

It makes no sense to have a security policy and an implementation of that policy and not have it be automatically distributed and applied, for instance. And security implementations should be tested just as much as any other code.

Re: Introducing Azure DevOps

#39

Post by michaelmurray » Mon, Sep 10, 2018, 5:36 PM UTC

ethomson wrote: post #5

SamuelAdams wrote: post #2

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…

We are considering using TFS (now Azure DevOps Server) for CI/CD of database related projects. Curious, how does DevOps handle SQL Database, SSIS, SSRS and SSAS visual studio projects when it comes to CI/CD? We have a custom solution currently in place, but would like to simplify this if possible.

Re: Introducing Azure DevOps

#40

Post by devonkim » Mon, Sep 10, 2018, 5:44 PM UTC

dsr_ wrote: post #7

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.

I gave myself a title at my last job that more accurately reflected the nature of the work - Senior Software Therapist. You get what you put into it, hopefully you don’t need the person for long, but most people that start it will probably not listen to the therapist and stay in treatment for longer. If your software and organization building and running it works 100% fine then you don’t need the therapist.

I have not gotten much traction.