升级TFS 2015 Build Agent

本文介绍了升级TFS 2015 Build Agent的处理方法，对大家解决问题具有一定的参考价值，需要的朋友们下面随着小编来一起学习吧！ 问题描述

我想在我的TFS 2015上上传一些构建任务，这些任务可以在 https： //github/Microsoft/vso-agent-tasks 。 我确实对某些任务有问题，因为它们确实需要最低代理版本1.89.0。我的构建代理是1.83.2版本。 现在，问题是，如何更新给定池的代理？如果我确实在TFS上右键单击代理程序池，然后选择更新所有代理程序选项，则不会发生任何事情。我想是因为在TFS上可用的代理的最新版本是1.83.2。 在哪里可以找到它的最新版本以及如何对其进行更新？

请注意，我在TFS 2015而非VSO上工作。 p>

谢谢

解决方案

如果右键单击代理池，然后选择更新所有代理，它将升级代理到本地TFS服务器的版本。例如，如果您最初安装了一些RC，然后再将服务器升级到RTM，则某些代理的版本可能较低。否则，就像您提到的那样，因为所有代理都是最新的，所以什么也不会发生。

VSO具有不同的发行模型，并且会不断交付对其代理的更新/修复。这就是版本不断增长的原因。

从技术上讲，可能可以获取最新的VSO代理任务的源代码，并将其推送到TFS 2015的内部部署版本。一个反模式，并且该行为是未记录且不受支持的。

让我引用此讨论中的构建vNext开发人员（请参见线程底部）：

这不是受支持的选项。我们在VSO中拥有的代理很可能无法与本地服务器一起使用。您必须使用服务器随附的代理的版本。

并且：

行为未定义/未测试。它可能会工作，可能不会。设计是为了使代理商通过从您的服务下载的自动更新过程向前拉。自动更新过程可能会更改磁盘上的配置/布局，无论如何。那个未来的代理可能会调用不存在的REST api，等等...代理的主要关注点是的前向兼容性，这样他们就可以懒惰地升级（通过任务最低代理的需求） ，在重新启动或最终排定的作业时）。

I would like to upload on my TFS 2015 some of the build tasks that are available here github/Microsoft/vso-agent-tasks. I do have a problem with certain task as they do require a minimum agent version of 1.89.0. My build agents are 1.83.2 version. Now, the question is, how do I update my agents for a given pool? If I do right click the agent pool on my TFS and choose update all agents option, nothing happens. I suppose because the latest version of my agent available on TFS is the 1.83.2. Where can I find the latest version of it and how do I update it?

Note I'm working on premises TFS 2015 and not VSO.

Thanks

解决方案

If you right-click the agent pool and choose "Update all agents", it will upgrade the agents to the version of the on-premise TFS server. For instance, if you initially installed some RC, and upgraded the server to RTM later, some agents might have lower version. Otherwise, as you mentioned, nothing will happen because all agents are up to date.

VSO has a different release model and updates/fixes to its agents are continuously delivered. That's why the version is constantly growing.

Technically it might be possible to grab the source code of the latest VSO agent tasks, and push it to the on-premise version of TFS 2015. However, it is considered an anti-pattern, and the behavior is undocumented and unsupported.

Let me quote build vNext developers from this discussion (see the bottom of the thread):

That is not a supported option. It is very likely that the agent we have in VSO will not work with the on-prem server. You must use the version of the agent that ships with your server.

And:

The behavior is undefined/untested. It may work, may not. The design is for agents to get pulled forward via an auto update process downloaded from your service. The auto update process may alter configs/layout on disk, whatever. That future agent might call REST apis that don't exist, etc... The primary focus for agents is on forward compat so they can lazily get upgraded (via task minimum agent demand, on restart or eventually a scheduled job).