Self-Hosted Runner using Window's find.exe instead of unix-style find.exe in git bin
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 6.3k
- Forks
- 1.4k
- Avg merge
- 1d 16h
- Merged PRs (30d)
- 24
Description
Describe the bug
Receive the following error when trying to use find
"FIND: Parameter format not correct"
When opening Git Bash and running the same code, it executes as expected.
- The error only occurs when there's an active job.
- Other paths are working as expected.
- Default shell is set explicitly to
bashand the step where this code is executed does not override that.
To Reproduce
find . -type f -name *.tar.gz
Expected behavior
For the unix style script to work.
Runner Version and Platform
Runner Version: 2.273.6
OS: Windows 10 (current)
What's not working?
I tried to look into how a runner sets up its environment variables but there was no documentation on the subject.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No source file or test is named. First reproduce the command in a Windows 10 self-hosted runner job, compare its environment and PATH with Git Bash outside an active job, and identify why Windows find.exe is selected. Done means find . -type f -name *.tar.gz uses the Unix-style find and succeeds during the job.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- bash, git, github-actions
- Domain
- ci-cd, devops, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100