Agent not recognizing all plugins
Answered
I have two TC cloud profiles configured with slightly different AMIs. Both are Windows 2016 images. The older of the two was create with agent 2018.2.1 while the newer is on 2020.1.3 (which matches the version of our server). When they are launched, they recognize two different sets of available plugins. The older AMI lists:
Found 73 non bundled plugins
while the newer lists:
Found 64 non bundled plugins
As a result, I am missing at least one needed tool on the newer agent, namely NuGet.CommandLine.3.5.0. What is causing this disparity in the two AMIs such the newer AMI is not usable for some things.
Thanks.
Please sign in to leave a comment.
Hi Sgygi. Sorry, I am not exactly sure for what the AMI isn't usable. It would help if you could clarify that. However, the fact that the NuGet.CommandLine.3.5.0 tool is not on the agent when it is starting up should not cause your builds to fail.
As mentioned in the documentation, the agent tools are loaded from the server on demand during the first build requiring that tool. That means if the agent hasn't run a build requiring NuGet version 3.5.0, that tool will not be present on the agent, and that is normal. For the agent to be able to download the tool upon starting a build requiring that tool, the specified version tool has to be available on the server in Administration > Tools.