问HN:Azure DevOps 是否实际上已经结束生命周期?

1作者: sam25610 天前原帖
我并不讨厌 Azure DevOps。相反,在过去五年多的时间里,它对我们组织来说是一个出色的工具。它的安全性相对容易保障,我们有很多优秀的管道来检查我们的代码、进行部署、与第三方服务集成等。我们对组织的运作有很好的可视化了解。 但是……我不禁觉得它跟不上 GitHub 的步伐,现在面临的问题是:如果我们想保持相关性,是否基本上没有选择,只能痛苦地迁移到 GitHub Enterprise? 特别是我们感受到的痛点: 1. Copilot 的 PR 审查在哪里?在 GitHub 上,我只需点击一个按钮,就能获得 Copilot 对任何 PR 的即时初步审查。当然,这并不完美,但基本上是免费的。 2. MCP?好吧,DevOps 终于有了一个 MCP 服务器,而且实际上还不错。但它的推出花了很长时间。这会是一个重复的模式吗?我们必须等上一年才能获得 GitHub 用户立即可以使用的工具? 3. Claude Code。在 GitHub 上,我可以从任何地方给 Claude Code 分配任务——浏览器、桌面、手机——它会在一个小的开发容器中运行,并将 PR 返回给我。同样,这并不总是完美的,但初级开发者的 PR 也不一定完美。而且 Claude Code 不在乎我是否在周五晚上给它分配任务。 所以,标题中的问题是:ADO 是否实际上已经到了生命周期结束的阶段? 我希望答案是否定的,我们可以坚持到情况好转。不过,我开始担心这只是沉没成本谬论。无论如何,有什么希望可以提供吗?
查看原文
I don&#x27;t hate Azure DevOps. On the contrary, it&#x27;s been a phenomenal tool for our organization over the past 5+ years. It&#x27;s been fairly easy to secure, we have tons of great pipelines that check our code, do deploys, integrate with third-party services, etc. We get great visibility into our organization.<p>But... I can&#x27;t help but feel like it&#x27;s not keeping up with GitHub and am now facing the question: do we basically have no choice but to do a painful migration over to GitHub Enterprise if we want to stay relevant?<p>In particular, pain we&#x27;ve felt:<p>1. Where&#x27;s the Copilot PR review? In GitHub I just click a button and I get an instant first level review of any PR by Copilot. Sure, it&#x27;s not perfect, but it&#x27;s more or less free.<p>2. MCP? Ok there finally is an MCP server for DevOps and it&#x27;s actually pretty good. But it took forEVER to come out. Is this a pattern that&#x27;s going to repeat? We have to wait a year for tools GitHub users get right away?<p>3. Claude Code. On GitHub I can give Claude Code assignments from anywhere -- browser, desktop, phone -- and it runs off in a little dev container and comes back to me with with a PR. Again, not always perfect, but neither are PRs from junior devs. And Claude Code doesn&#x27;t care if I give it the assignment on a Friday night.<p>So the titular question: Is ADO effectively EOL?<p>I&#x27;m hoping the answer is no, and we can just hold on till things get better. I&#x27;m starting to worry, though, that this is just the sunk cost fallacy. Anyway have hope to offer?