TFS Agent Setup

Troubleshooting

PowerShell ISE .\config.cmd gets stuck at Connect:

Documentation suggests that you can run .\config.cmd from elevated PowerShell ISE.
This appears to get stuck at Connect:
https://github.com/Microsoft/azure-pipelines-agent/issues/1266

Use Elevated VS Command prompt instead works.

 

Build: No agent found in pool Default which satisfies the specified demands:

msbuild
visualstudio
vstest
Agent.Verion -gtVersion 2.115.0

Solution: Install Visual Studio.
Then I used a VS command prompt elevated as administrator to reconfigure the agent by using:
.\config.cmd remove
.\config.cmd

 

Build Failed: Failed to retrieve information about ‘NETStandard.Library’ from remote source ‘\\<old-server>’

Resolution was not to install .Net Core SDK
It was that the domain had changed and NuGet could no longer see the old packages UNC
Short-term resolution:
Include the packages in source control explorer
Remove the unavailable location from nuget.config

Long-term resolution:
Would be to move the packages to a new accessible location

 

 

Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

%d bloggers like this: