-
Notifications
You must be signed in to change notification settings - Fork 982
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
Hook feature - Set up runner step failed when working-directory specified #1808
Comments
Thanks for the report @retzero, thats a bug we will get a fix in the next runner version |
@thboop |
I am using the latest version '2.301.1' for self hosted runner but still facing the same issue. I have also tried specifying the working directory at job level. |
I'm facing the same issue |
facing the same issue |
1 similar comment
facing the same issue |
Describe the bug
A clear and concise description of what the bug is.
Hello,
I'm trying to use start/complete hook feature. (v 2.289.1)
But it's failing when default
working-directory
is set in the workflow.Can you please guide me how to overcome this?
My workflow
Error prints
To Reproduce
Steps to reproduce the behavior:
Expected behavior
A clear and concise description of what you expected to happen.
Runner Version and Platform
Version of your runner?
2.289.1
OS of the machine running the runner? OSX/Windows/Linux/...
Linux (Ubuntu)
What's not working?
Please include error messages and screenshots.
Job Log Output
If applicable, include the relevant part of the job / step log output here. All sensitive information should already be masked out, but please double-check before pasting here.
Runner and Worker's Diagnostic Logs
If applicable, add relevant diagnostic log information. Logs are located in the runner's
_diag
folder. The runner logs are prefixed withRunner_
and the worker logs are prefixed withWorker_
. Each job run correlates to a worker log. All sensitive information should already be masked out, but please double-check before pasting here.The text was updated successfully, but these errors were encountered: