search

SkillsFundingAgency / das-azure-pipelines-agents

MIT License
0 stars 2 forks source link

Windows agents not being removed on termination #34

Open EwanNoble opened 4 years ago

mwevill commented 4 years ago

https://docs.microsoft.com/en-us/azure/devops/pipelines/agents/docker?view=azure-devops

If you want a fresh agent container for every pipeline run, you should pass the --once flag to the run command. You must also use some kind of container orchestration system like Kubernetes or Azure Container Instances to start new copies of the container when the work completes.

This appears to have been implemented (Issue raised on 3/4 change implemented 6/4). Need to check if this has worked,

Looks like it has worked

Commit to master

EwanNoble commented 4 years ago

https://github.com/MicrosoftDocs/azure-devops-docs/issues/6019

nbowes24 commented 4 years ago

2020-06-23 14:46:36Z: Listening for Jobs 2020-06-23 15:39:33Z: Running job: Job 2020-06-23 15:43:33Z: Job Job completed with result: Succeeded Cleanup. Removing Azure Pipelines agent... Removing agent from the server Connecting to server ... Succeeded: Removing agent from the server Removing .credentials Succeeded: Removing .credentials Removing .agent Succeeded: Removing .agent

It is hitting the Finally block and cleaning up.

Currently no offline agents showing on VSTS. Something to monitor.