Task not working after a fresh install on a custom agent running as `Network Service` about gl-vsts-tasks-yarn HOT 4 CLOSED

Hi,

Sorry for the inconvenience, I double checked, but the task is behaving correctly on my builds. So I have questions.

From what I see in your logs, you are on a custom agent and using a locally installed yarn version located in f:\yarn. Which version are you using, is the service account runing vsts agent having sufficient rights?

In addition, can you provide a debug log

from gl-vsts-tasks-yarn.

Hi,

So we had installed yarn with npm (npm install -g yarn). To check permissions like you said, we jumped into the box and tried to run it as Network Service (build agent runs as network service), didn't work.

So we installed again but with the .msi. Tried to run as network service: worked!
En-queue a new build again, didn't work.

Restarted the build machine, tested again.... It worked!

Hope that experience will help others.

Thanks for your comment @sandorfr to put me into the right direction.
And thanks for your work guys. Its awesome!

from gl-vsts-tasks-yarn.

I'm thinking of writing some additional guidance, to point users in the right direction. Thank you for sharing your experience as it will help me. Two important points from your feedback:

• Your first attempt was to install it with npm which is not one of the supported ways, so I guess we should point to the installation instruction (msi or chocolatey).
• The fact that a reboot is needed despite being a common thing with windows can be pretty tricky to troubleshoot, so we should recommend doing so.

from gl-vsts-tasks-yarn.

Hi @sandorfr,

In fact i don't know if a restart of the agent service would do the trick. But we didn't have any queued build, so we did a full reboot. Probably a restart of the service in enough. My understanding is that the agent has to restart so he gets the new environment vars.

from gl-vsts-tasks-yarn.