代理池和部署池之间的Azure Devops(VSTS)不同 [英] Azure Devops (VSTS) Different between Agent Pool and Deployment pool

问题描述

我正在为我们的组织制定Azure Devops的过程，尽管我在某种程度上做得很好，但我仍然不理解我认为应该的几个概念.

I'm in the process of setting out Azure Devops for our organisation and although I have got things working to an extent, I still dont understand a couple of concepts that I think I should.

我已经设置了一个部署池(组织设置">部署池")，并使用脚本在我的Dev，Test和Prod服务器上安装和配置了代理，并且已经能够成功地向他们部署代码

I have set up a Deployment Pool (Organization settings > Deployment Pools) and used the script to install and configure the Agents on my Dev, Test and Prod servers, and have been successfully able to deploy code to them

我现在已经能够使用"Azure托管"选项来构建我的项目，但是我真的很想使用本地托管选项，但是当查看代理程序池"(组织设置">代理程序池")时，我只能看到生产服务器，它不会让我使用该版本.我单击了下载代理"按钮，但它使用相同的powershell命令.config.cmd命令下载了我在部署池"阶段已设置的代理

I have been able to build my projects using the Azure Hosted option for now, but I would really like to use the locally hosted option, but when looking at the Agent Pools(Organization settings > Agent Pools) I can only see my Production server and it wont let me use that build with. I clicked the button to "Download Agent" but it downloads the agent I already set up in the Deployment Pool stage using the same powershell command .config.cmd command

据我所知，代理池"中的代理与部署池"之间没有区别，但是由于我看不到代理池中的代理，因此我显然在这里缺少了一些东西.

So as far as I can tell, there is no difference between an agent in an "Agent pool" vs a "Deployment pool", but I'm obviously missing something here as I cannot see the agent in the Agent pool.

谁能帮助我了解我可能错过的内容，以及为什么有两种完全不同的下载同一代理的方式?

Can anyone help me to understand what I might have missed, and why there are two totally different ways of downloading the same agent?

非常感谢！

推荐答案

部署池用于

Deployment pool are for deployment groups are a special agent configuration that are used specifically in release pipelines. They give some additional options for your release pipelines beyond the regular agents.

部署组:

• 指定代理的安全性上下文和运行时目标.创建部署组时，需要添加用户并为他们授予适当的权限，以管理，管理，查看和使用该组.

• Specify the security context and runtime targets for the agents. As you create a deployment group, you add users and give them appropriate permissions to administer, manage, view, and use the group.

让您在部署发生时查看每个服务器的实时日志，并下载所有服务器的日志以跟踪您部署到单个计算机的情况.

Let you view live logs for each server as a deployment takes place, and download logs for all servers to track your deployments down to individual machines.

使您能够使用机器标记将部署限制为特定组的目标服务器

Enable you to use machine tags to limit deployment to specific sets of target servers

它利用相同的管道代理，但是您只是为初始化指定了不同的配置.如果导航到代理程序池"页面，则会有一个下载链接，其中包含用于设置代理程序的配置，当您使用代理程序阶段而不是部署组阶段时，可以在构建管道或发布管道中利用该代理.

It leverages the same pipeline agent but you are just specifying different configuration for the initialization. If you navigate to the Agent Pool page, there is a download link there with the configuration for setting up an agent that you can leverage in a build pipeline or in a release pipeline when you use an Agent Phase instead of a Deployment Group phase.

这篇关于代理池和部署池之间的Azure Devops(VSTS)不同的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！