简体繁体 English

同一服务器上的多个自托管 Azure 管道代理

[英]Multi Self-hosted Azure pipeline agents on same server

原文 2020-01-17 16:18:02 1 2 azure/ azure-devops/ azure-pipelines

We currently have more than one self-hosted Azure pipeline agents running on one server.我们目前在一台服务器上运行着不止一个自托管的 Azure 管道代理。 Recently we have notices the pipelines are failing with "Network Path Issues", looks like all the steps run on one agent and somehow one of the steps jumps to a different agent causing it to fail.最近我们注意到管道因“网络路径问题”而失败，看起来所有步骤都在一个代理上运行，但不知何故其中一个步骤跳转到另一个代理导致它失败。 Is there a way to separate this other than creating new servers for each agent?除了为每个代理创建新服务器之外，有没有办法将其分开？

2 个解决方案

Looks like all the steps run on one agent and somehow one of the steps jumps to a different agent causing it to fail.看起来所有步骤都在一个代理上运行，并且其中一个步骤以某种方式跳转到另一个代理，导致它失败。 Is there a way to separate this other than creating new servers for each agent?除了为每个代理创建新服务器之外，有没有办法将其分开？

I can't reproduce same issue on my side.我无法在我这边重现相同的问题。 I assume the self-agents you mentioned above are in same agent pool, if so, as I know Devops doesn't have one option to separate agents from same agent pool when these agents are installed in same machine.我假设你上面提到的自我代理在同一个代理池中，如果是这样，我知道当这些代理安装在同一台机器上时，Devops 没有一个选项可以将代理从同一个代理池中分离出来。

About the strange behavior you met, you can try this to resolve it:关于你遇到的奇怪行为，你可以试试这个来解决：

1.Since you may have more than one self-agents in same Agent Pool running in same server, I suggest you can try separate those agents in different Agent Pool. 1.由于在同一台服务器上运行的同一个Agent Pool中可能有多个self-agents，我建议您可以尝试将这些agents分开在不同的Agent Pool中。 Since your agents are running in same server, in this situation one agent pool for one agent can be more suitable.由于您的代理运行在同一台服务器上，在这种情况下，一个代理池更适合一个代理。

2.Assuming your steps may not in same agent job, check and make sure your different agent jobs use same agent pool. 2.假设您的步骤可能不在同一个代理工作中，请检查并确保您的不同代理工作使用相同的代理池。

Hope it helps:)希望能帮助到你：）

After going through lot of logs and all the pipelines that were having issues was able to find some similarities.在查看了大量日志和所有有问题的管道后，能够找到一些相似之处。 Most of the issues were having on the step where we were using Powershell task and the task was outdated (replaced with new one by Azure).大多数问题出现在我们使用 Powershell 任务的步骤中，并且该任务已过时（由 Azure 替换为新任务）。 After updating all the powershell tasks the issue seems to have gone.更新所有 powershell 任务后，问题似乎已经消失。