Closed pri-kise closed 2 years ago
I only see this error for BC 19 right now. Maybe this could help to find the problem.
Could it be that you are using multiple agents on the same server? Because that could be conflicting when both are doing the same on the same place .. causing an interaction, which PS doesn't allow (needs interaction).
Yes this might cause the issue. Is there some flag that we can set to deal with this probelm? Or maybe could you copy the alc.exe to the agent workspace folder that multiple agents do not conflict with each other?
I wouldn't want to do that, because we also use this to speed up builds (caching)
And .. it's a Microsoft recommendation to NOT put multiple agents to one machine: https://docs.microsoft.com/en-us/azure/devops/pipelines/agents/agents?view=azure-devops&tabs=browser#install
So in all honesty, we might mitigate this issue, only to expect the next one at some point in time...
@waldo1001 I understand your point. We have multiple agents on one system to speed up, too. Since the downloading of different images is often the part that takes the most time.
I understand. Multiple agents is important. Can't you split them in VMs or something?
We are also looking into setting this up for the community, so that other people can use our build agents ... I think that can simplify things as well .. .
I've got the exact same problem with a single agent
It seems the cause of this issue might be something different after all.
I see "DSA-LAPTOP" - I hope this is not a Windows11 or 10?
I see "DSA-LAPTOP" - I hope this is not a Windows11 or 10?
It is, since we are awaiting our final server. Is this not supported? (I have used a self-hosted agent on Windows 10 in the past). I might be missing something?
No, Windows 10 comes with a whole lot of challenges. As such, a build server does run on it, but we're doing a lot in PowerShell and Docker (especially Docker) that simply isn't supportable on a non-server-system.
I have a blogpost here that kind of gives you the best way to install a build server: https://www.waldo.be/2020/07/13/installing-a-devops-agent-with-docker-with-the-most-chance-of-success/
No, Windows 10 comes with a whole lot of challenges. As such, a build server does run on it, but we're doing a lot in PowerShell and Docker (especially Docker) that simply isn't supportable on a non-server-system.
I have a blogpost here that kind of gives you the best way to install a build server: https://www.waldo.be/2020/07/13/installing-a-devops-agent-with-docker-with-the-most-chance-of-success/
Ok thank you for the information. I agree this is quite uncommon. We'll wait for our final server to arrive so we can set up ALOps
I'll close this issue for now, since there are alternative solutions in place. Please, if you have this issue on a windows server AND with a single build server on it, you can open a new issue, with full log and yml details.
Describe the bug We receive strange errors for our pipelines.
the used yaml please provide the yaml that you used. It helps you put the yaml like this:
the output Also the complete output is necessary for us to see what is going on. Also use backtics:
Expected behavior Sometimes our pipelines are running and sometimes we receive this error. Please fix this or help with the error message.
Screenshots
Additional context