dmnemec / copy_file_to_another_repo_action

This GitHub Action copies a file from the current repository to a location in another repository
Apache License 2.0
182 stars 201 forks source link

Action fails after recent change to entrypoint.sh #39

Closed pmoccioTVR closed 2 years ago

pmoccioTVR commented 2 years ago

I have a number of workflows that use this action and they're failing with this error after the recent change to entrypoint.sh:

Cloning into '/tmp/tmp.icEILo'...
+ echo 'Copying contents to git repo'
Copying contents to git repo
+ mkdir -p /tmp/tmp.icEILo/
+ rsync -avrh CHANGELIST.md /tmp/tmp.icEILo/
/entrypoint.sh: line 27: rsync: not found
stilleshan commented 2 years ago

me too

/entrypoint.sh: line 27: rsync: not found
kickbutts commented 2 years ago

The same with me /entrypoint.sh: line 27: rsync: not found

hannawaffle commented 2 years ago

Same here

facutk commented 2 years ago

I have the same issue

Jason2866 commented 2 years ago

Same here

facutk commented 2 years ago

@dmnemec anything we can do to help you debug this issue?

Jason2866 commented 2 years ago

I forked the repo and reverted the faulty change and use the fork. Works!

lukasklein commented 2 years ago

I have already created a PR for this: https://github.com/dmnemec/copy_file_to_another_repo_action/pull/38

You can theoretically use our fork in your actions (uses: datacake/copy_file_to_another_repo_action@main), though this should only be a temporary solution (no guarantee our fork will be maintained when the upstream repo has been fixed).

RossMurr4y commented 2 years ago

You can just use the most recent successful commit hash instead of a branch name for the Action.

    - name: example
      uses: dmnemec/copy_file_to_another_repo_action@3fe42250d47e0764da9de9939b151b09a26e5857

Then once this is resolved, revert to using main again:

  - name: example
    uses: dmnemec/copy_file_to_another_repo_action@main
eranelbaz commented 2 years ago

We are also having this problem

philipturner commented 2 years ago

Same problem.

Niek commented 2 years ago

Same here

dmnemec commented 2 years ago

Guessing the base image doesn't have rsync, I'll debug it today.

philipturner commented 2 years ago

rsync is one silent error I got. Entrypoint.sh failed at line 27 in the log though. I don’t recall if both errors were the same thing

dmnemec commented 2 years ago

I fixed the rsync not found problem and made it an optional feature on Latest (setting the use_rsync var will enable it). Line 27 was the rsync line.

38 and #40 were the fix PRs