azure-devops-self-hosted-agent

Azure Self Hosted agent : A session for this agent already exists , when running more then 1 build agent

老子叫甜甜 提交于 2021-01-29 11:34:55
问题 I have defined 1 agent called "ios_dockeragent" in agent pools configuration : Settings/Agent pools/Default In my Azure DevOps organization, I bought 4 Parallel jobs and 3 Parallel hosted jobs so I do not have a parallel jobs problem. From each build server I start the self hosted server like this where "ios_dockeragent" is defined in devops: docker run -d --rm -t --name=ios_docker_64 -e AZP_WORK=/temp/working_dir -v =/temp/working_dir:/azp -e AZP_URL=https://dev.azure.com/xx -e AZP_TOKEN

How to configure different versions of Ruby / any other software in self hosted agent?

天涯浪子 提交于 2020-08-10 23:50:23
问题 I have installed 3 different versions of Ruby in self hosted agent but i am unable to use them in my vsts task as required. The microsoft document suggests configuring " Agent.ToolsDirectory " but i am not sure how to configure it in the self hosted agents. Can anyone help me with descriptive steps on how to configure it so that i can use the vsts task : "Use Ruby Version task" on my self hosted agent 回答1: how to configure it in the self hosted agents? Agent.ToolsDirectory , this is one of

Visual Studio 2015 Express not recognised by private build agent

隐身守侯 提交于 2020-01-07 05:01:13
问题 If I install Visual Studio 2017 Community edition on a machine and registered it as a build agent, then the 'capabilities' tab against the agent registration shows the following environment variables: VisualStudio C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\ VisualStudio_15.0 C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\ VisualStudio_IDE C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\Common7\IDE\ VisualStudio_IDE_15.0 C:\Program Files (x86)

How Restrict the Agent Job to Run only if Specific Job succeeded

夙愿已清 提交于 2020-01-05 07:10:14
问题 I have 3 Jobs in Azure Devops Release Pipeline : Agent job1 Agent job2 Agent job3 I want to configure Agent job2 In such a way that it should run even if Agent job1 Fails. for that, I have set Agent job2 property of Run this job to even if the previous job fails . Now, I want to configure Agent job3 in such a way that it should run only if Agent job2 succeded What configuration I need to make in Agent Job3 to make it Dependant on Agent Job2 回答1: How Restrict the Agent Job to Run only if

Why are there no files in my release artifacts directory?

若如初见. 提交于 2019-12-13 17:04:45
问题 I created a .netcore 2.1 api project and set up Azure DevOps to deploy it to an On-Prem computer using the Windows Agent. The folder agent_work\r1\a was created on the machine running the agent, however there are no files in it. I can see that a build did occur and that there is an artifact in my release What did I miss doing? [Update] I can see in the agent job, there is a section which is about downloading an artifact. It has the error message There is no build available or the source is

Gradle Daemon being killed in “Finalize Job” step

删除回忆录丶 提交于 2019-12-13 01:18:48
问题 I've got a "Build" pipeline that runs gradlew build on my java code and then just exports the jar as an artifact. It is currently running on a self hosted agent as I was hoping this will help speed up the compilation. I noticed that at the start of every run it says it is starting a new daemon as the stopped ones can't be used. In the "Finalize job" step it says "Start cleaning up orphan processes." and then "Terminate orphan process: pid (17162) (java)". In the image below you can see that

Azure DevOps Hosted Agents - Add Tool (PS Module) to agent

眉间皱痕 提交于 2019-12-02 08:35:14
问题 I am wondering if there is an easy way to incorporate an extra tool to one of the default Microsoft hosted agent pools (specifically VS2017). Basically, I want to add some of the extra ARM powershell modules that are not installed by default as only the core set of modules are installed; i.e. I am looking to leverage some of the extra modules such as AAD as part of the deplyment pipeline, e.g. to create an AAD role definition. I guess the same would be true for CLI extensions if I was using