-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
FAKE 5 Runner task doesn't work on Linux build agent #33
Comments
I found a problem: I ran build agent from root user. When I created dedicated user for build agent only error disappeared |
Interesting, the relevant output looks to be:
Strange how an exception managed to print out the usage string. |
I've switched back to root build agent with FAKE_DETAILED_ERRORS and got the following.
|
Sorry, can you try with a lower case 't' in 'true'?
Sadly it didn't include any additional output |
Sure
|
I went through the corresponding code-paths. There is not anything suspicious there but given what we know (that it works as non-root) and the linux specific code-path I'd say the most likely scenario is that Thanks for the quick follow-ups! |
On my build agent machine HOME is set to /root for root user but when using build agent the variable is not set. After setting HOME variable in Azure DevOps pipeline the error disappears (and after removing paket.lock) |
@BlooDCrescent Thanks for confirming. I reported the issue fsprojects/Paket#3791, so I'll close this here. We could add a workaround here, but we should really fix this at the root. Additionally, I added some logic to FAKE itself to report better errors when paket initialization failed, so it shouldn't take as long in the future to find the root cause. Again thanks for reporting :) |
Description
FAKE 5 Runner task doesn't work on Linux build agent
Repro steps
1.5 Add custom capability in order to run DevOps task
Expected behavior
Application is built
Actual behavior
Azure DevOps pipeline fails with error
Details
Known workarounds
Copy and paste build command directly in terminal
The command runs successfully
Related information
Fake 5.19.0
The text was updated successfully, but these errors were encountered: