Files excluded in `.gitignore` files?

[burnett01]

Files excluded in `.gitignore` files?

[cwilby]

FYI - I found a solution I'm happy with 🎉

A GitHub workflow has many Jobs, and each Job can specify which runner it should run on.

Instead of one job, I now run Test/Build on the self hosted runner, and Deploy on a GitHub hosted runner.

The Build script uses https://github.com/actions/upload-artifact to upload the build output to the workflow.

The Deploy script uses https://github.com/actions/download-artifact to download the build output from the workflow, and then uses this rsync action successfully to push to environments.

[cwilby]

Ok, I managed to get my CI process working, but no solution to this problem yet.

When rsync runs on the runners runtime, it is able to find and sync those files.

[Burnett01]

Ok, I managed to get my CI process working, but no solution to this problem yet.

When rsync runs on the runners runtime, it is able to find and sync those files.

Hello @cwilby, thank's for reaching out. It is interesting to know that all your intended files are synced when running the action on the runners runtime but not on your self-hosted runner.
Are there any rsync switches active or filters?

[cwilby]

Thanks for responding - here is the build step, the switches are -avzr --delete.

      - name: Deploy build artifact
        if: github.ref == 'refs/heads/develop'
        uses: burnett01/[email protected]
        with:
          switches: -avzr --delete
          path: public/
          remote_path: ${{ secrets.SSH_PATH }}
          remote_host: ${{ secrets.SSH_HOST }}
          remote_user: ${{ secrets.SSH_USER }}
          remote_key: ${{ secrets.SSH_KEY }}

[cwilby]

I've discovered the issue is related to running self hosted runners using Docker, where the runner container shares a Docker daemon with the host.

The issue is that the when the volume is mounted to the container that runs this action, the mount point is from the host operating systems perspective, not the runner containers perspective (which contains the build output).

This is only a problem when running self hosted runners using Docker.

[Burnett01]

Congrats @cwilby for solving this issue and for investigating. I am glad you figured it out and thank you for your contribution! I have pinned this issue and added the documentation label, in case anyone else runs into the same problem.
Using separate runners on each job combined with the artifacts actions is a straightforward way of dealing with your usecase.

Have a great week,
greetings
Steve

[cwilby]

Additionally using https://github.com/marketplace/actions/delete-artifact to delete artifacts at the end of each build (I don't need to keep them around) to prevent taking up space I don't need.