-
-
Notifications
You must be signed in to change notification settings - Fork 370
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
bug: 🐝 Cannot create target folder since 4.7.1 on self-hosted runner (rsync: --mkpath: unknown option
)
#1753
bug: 🐝 Cannot create target folder since 4.7.1 on self-hosted runner (rsync: --mkpath: unknown option
)
#1753
Comments
What OS version is your self hosted runner using? |
Ubuntu 20.04 |
we may have similar problem over here:
and the job: https://github.com/Lightning-AI/utilities/actions/runs/12135515450/job/33835493833#step:8:80 UPDATE: seems bumping OS to |
I've got a potential fix for this in the works that I'll work to get up by EOD |
Should be fixed in 4.7.2 |
Describe the bug
Since upgrading to 4.7.1, the deploy action now fails with
rsync: --mkpath: unknown option
.The
--mkpath
option was added in rsync 3.2.3, but our self-hosted runner (based on https://github.com/myoung34/docker-github-actions-runner) only has 3.1.3. Do we need to upgrade rsync for this to work or would it be possible for the action to support older versions?Reproduction Steps
Use a self-hosted runner with rsync <3.2.3.
Logs
/usr/bin/rsync -q -av --checksum --progress --mkpath ... --delete --exclude CNAME --exclude .nojekyll --exclude .ssh --exclude .git --exclude .github rsync: --mkpath: unknown option rsync error: syntax or usage error (code 1) at main.c(1601) [client=3.1.3]
https://github.com/ministryofjustice/hmpps-probation-integration-e2e-tests/actions/runs/12115120629/job/33776527330#step:12:68
Workflow
https://github.com/ministryofjustice/hmpps-probation-integration-e2e-tests/actions/runs/12115120629/workflow#L176-L181
Additional Comments
No response
The text was updated successfully, but these errors were encountered: