You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Would you please update the documentation to reflect which directories the action will have access to when running from Docker? I was trying to specify junit_files like this:
- name: Publish test resultsuses: EnricoMi/publish-unit-test-result-action@v2if: always()with:
check_name: Test Results for ${{ github.workflow }}junit_files: ${{ runner.temp }}/pytest-reports/**/*.xml
but GitHub only provides a few volume mounts, and ${{ runner.temp }} isn't covered by them. I moved the files to a relative directory and this is working fine, but I had to debug a bit to reach this conclusion. FWIW here are the relevant docker run command line options that GitHub uses to launch this action:
Yes, running the action in Docker container has very limited access to paths. Ideally is using relative paths. I will improve documentation to stress this fact. Thanks for reporting.
Would you please update the documentation to reflect which directories the action will have access to when running from Docker? I was trying to specify
junit_files
like this:but GitHub only provides a few volume mounts, and
${{ runner.temp }}
isn't covered by them. I moved the files to a relative directory and this is working fine, but I had to debug a bit to reach this conclusion. FWIW here are the relevantdocker run
command line options that GitHub uses to launch this action:You could even go so far as to fail the action if any of the
*_files
args attempt to reference anything not under the four mounted directories.The text was updated successfully, but these errors were encountered: