Skip to content
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

Rsync ARGS not working #189

Closed
NicolasJourdan opened this issue Jul 8, 2024 · 3 comments
Closed

Rsync ARGS not working #189

NicolasJourdan opened this issue Jul 8, 2024 · 3 comments
Labels
stale Issues without activity

Comments

@NicolasJourdan
Copy link

Hello,

I'm using the ARGS environment variable to add some arguments to rsync however it seems like the arguments are not add to the rsync command.

My cd configuration :

            - name: Ssh deploy
              uses: easingthemes/[email protected]
              env:
                  SSH_PRIVATE_KEY: ${{ secrets.DEPLOY_KEY }}
                  ARGS: "-rlgoDzvci"
                  REMOTE_HOST: ${{ secrets.DEPLOY_HOST }}
                  REMOTE_USER: ${{ secrets.DEPLOY_USER }}
                  TARGET: ${{ secrets.DEPLOY_TARGET }}
                  SCRIPT_BEFORE: |
                    whoami
                    ls -al
                  SCRIPT_BEFORE_REQUIRED: true
                  SCRIPT_AFTER: |
                    whoami
                    ls -al
                    echo $RSYNC_STDOUT
                  SCRIPT_AFTER_REQUIRED: true

The github action fails :

rsync: chgrp "***/.git/" failed: Operation not permitted (1)
...
rsync: chgrp "***/project/composer.json" failed: Operation not permitted (1)
...

I tried to sync the file from my PC using the same ssh key and it worked.

rsync project/composer.json ****@****:/home/****/www/project/composer.json -rlgoDzvci
@Shimon42
Copy link

I just encountered this error. Verifying that the remote directory is owned by your SSH user and has the appropriate permissions resolved the issue for me

@NicolasJourdan
Copy link
Author

I tried this the same ssh key from my computer and I don't have any problems. :/

Copy link

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days.

@github-actions github-actions bot added the stale Issues without activity label Oct 12, 2024
@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Oct 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
stale Issues without activity
Projects
None yet
Development

No branches or pull requests

2 participants