Azure DevOps内部部署成本 [英] Azure DevOps on-premise costs

问题描述

在SO上问这个问题似乎很奇怪，但这就是MS希望我们这样做的地方...

Seems strange asking this on SO but that's what MS want us to do so here goes...

我正在考虑设置本地Azure DevOps 2019服务器，但是像往常一样，许可和成本不是很透明.

I'm looking at setting up an on-premise Azure DevOps 2019 server, but as usual the licensing and costs aren't very transparent.

我们的开发团队可能会获得Visual Studio Pro订阅，我相信该订阅将随附DevOps服务器许可证和CAL.如果我们停止这些订阅会发生什么?这是否意味着我们将无法再使用内部DevOps服务器?

Our dev team are likely to be getting Visual Studio Pro subscriptions, which I believe comes with a DevOps server license and CALs. What happens if we stop these subscriptions - does it mean we can no longer use our on-premise DevOps server?

我不太清楚我们可能需要支付的额外费用"(扩展，管道)，而且我也不想被任何意外打中.基本要求是:

I'm not very clear on what "extras" we may need to pay for (extensions, pipelines), and I don't want to be hit by any surprises. The essential requirements are:

• 能够触发签入的构建.我不知道这是一个内置功能还是需要某种扩展和/或管道(以及是否有免费功能?)
• 使用构建任务来创建NuGet软件包并将其托管在内部服务器上.同样，这是否需要任何付费的扩展或管道?
• 每月构建时间应该没有限制(与我认为是240分钟的VSTS不同)

推荐答案

据我所知:

您可以使用至少一个Visual Studio专业版或企业版许可证运行Azure DevOps Server 2019 a>.

每个用户可用的功能基于分配给用户的许可证:利益相关者(无许可证)获得基本知识，基本访问(专业)为您提供大部分功能，企业版为您提供所有功能.

The features available to each user are based on the licence assigned to the user: Stakeholders (no license) get the very basics, Basic access (Professional) gives you most of the features, Enterprise gives you all the features.

基本与企业之间最明显的区别是:

The most notable differences between Basic and Enterprise are:

• 查看发布和管理批准
• Microsoft发布的工件
• Azure DevOps扩展

但是，每

However, per this annoucement, Artifacts are now included in the Basic/professional license.

因此，只有专业许可证，您才适合通过Artifact Feed触发构建，发布和使用nuget软件包.我认为安装扩展程序可能需要Enterprise用户，并且在没有Enterprise许可的情况下尚未测试查看发布和管理批准".这似乎与我们一直在使用的较旧的TFS有所不同，在该版本中，Basic用户可以创建和查看发行版.

So with only professional licenses you should be good for triggering builds, publishing and using nuget-packages via Artifact feeds. I'd think that installing extensions might require Enterprise user and haven't tested "View Releases and Manage Approvals" without Enterprise license yet. That seems to have changed from older TFS we've been using, in which Basic users were able to create and view releases.

因此，无论如何建议至少获得一个企业许可证.

So would recommend getting at least one Enterprise license, in any case.

这篇关于Azure DevOps内部部署成本的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！