build-agent

问题 I have a build for a .NET solution that is running in a private agent. The solution contains both .NET Core 2.1 and .NET Standard 2.0 projects. Some of the nuget packages installed are the following: NETStandard.Library v2.0.3 Microsoft.AspNetCore.Mvc v2.0.0 Microsoft.NETCore.App v2.1.5 The build fails when trying to restore the nuget packages with the following error: "F:\Agent01\w\141\s\xxxxxxx.sln" (Restore target) (1) -> (Restore target) -> C:\Program Files\dotnet\sdk\2.1.500\NuGet

问题 According to https://github.com/MicrosoftDocs/vsts-docs/blob/master/docs/pipelines/agents/hosted.md the virtual machine size of the Microsoft-Hosted Agent is: Currently utilizing Microsoft Azure general purpose virtual machine sizes ( Standard_DS2_v2 and Standard_DS3_v2 ) What does that mean? Which size is used? Standard_DS2_v2 or Standard_DS3_v2? Can I decide which one I want to use? Kind regards, Peter 回答1: There isn’t the way to force build/release to use DS3_v2 vm agent, it usually try to

问题 According to https://github.com/MicrosoftDocs/vsts-docs/blob/master/docs/pipelines/agents/hosted.md the virtual machine size of the Microsoft-Hosted Agent is: Currently utilizing Microsoft Azure general purpose virtual machine sizes ( Standard_DS2_v2 and Standard_DS3_v2 ) What does that mean? Which size is used? Standard_DS2_v2 or Standard_DS3_v2? Can I decide which one I want to use? Kind regards, Peter 回答1: There isn’t the way to force build/release to use DS3_v2 vm agent, it usually try to

问题 I want to install a TeamCity BuildAgend as a user. When entering my user credentials here: I always get this error: NOTE: My account (user) is Administrator with full permission! How can I do this? 回答1: The error message says it does not have "enough rights to run as a service" , this is slightly different from just being an administrator. Go to Control Panel> Administrative Tools> Local Security Policy . Select Local Policies> User Rights Assignment . Scroll down through the list of policies

问题 I m using TFS 2015, I saw that my build Agent is Offline : I launch the VsoWorker.exe to see the logs and understand the error, Here is what I get but I found nothing from the internet : Any Idea please ? 16:07:57.649004 Sending trace output to log files: C:\Users\Administrator\Downloads\agent\_diag 16:07:57.649004 vsoWorker.exe was run with the following command line: "C:\Users\Administrator\Downloads\agent\Agent\Worker\VsoWorker.exe" 16:07:57.649004 VsoWorker.Main(): Create AgentLogger 16

问题 I m using TFS 2015, I saw that my build Agent is Offline : I launch the VsoWorker.exe to see the logs and understand the error, Here is what I get but I found nothing from the internet : Any Idea please ? 16:07:57.649004 Sending trace output to log files: C:\Users\Administrator\Downloads\agent\_diag 16:07:57.649004 vsoWorker.exe was run with the following command line: "C:\Users\Administrator\Downloads\agent\Agent\Worker\VsoWorker.exe" 16:07:57.649004 VsoWorker.Main(): Create AgentLogger 16

问题 I seem to be unable to install a build agent on our TeamCity 5.1.2 build server that is compatible with a VS2010 (sln) build configuration. Under "Build Runners", the following runners are listed: Ant: Runner for Ant build.xml files Duplicates finder (.NET): C# and VB duplicate code finder Command Line: Simple command execution And under "Compatible configurations", the project I've configured to build with the Visual Studio 2010 (sln) build runner is listed under "Incompatible configurations

问题 I'm trying to write a build step within TFS that relies on knowing where the Build agent has nuget.exe stored (the standard nuget-install step mucks around with the order of arguments in a way that breaks build execution, so I want to run the exe myself using one of the batch/shell/ps steps). It would seem that setting up a capability on the Build Agent with that path would make sense, but I cannot seem to reference the value in any of my build steps, and I cannot find anything helpful on

问题 We want to migrate from VS 2017 to VS 2019. We are still on TFS 2017 and want to stay there for now. I set up the build infrastructure a long time ago, so I am not certain anymore what the role of VS on the build agent is.. I certainly sometimes use it to manually open a solution that does not compile for unclear reasons, and I think it also was needed for some libraries. I want the automated build process to use same VS as on developer machines, for consistency. Can I uninstall VS 2017 and

问题 We have .Net project build definition on VSTS and it's using Azure Storage Emulator for running tests. And we want to use Hosted 2017 agents for the build definition. I saw this question (Azure SDK not available on Hosted VS2017 VSTS Build Agent) and the comment that I can use command " C:\Program Files (x86)\Microsoft SDKs\Azure\Storage Emulator\AzureStorageEmulator.exe init /server (localdb)\MSSQLLocalDb " to initialize Azure Storage Emulator. However, when I tried to start Azure Storage