Skip to content
This repository has been archived by the owner on Mar 4, 2021. It is now read-only.

Still getting EISDIR: illegal operation on a directory, read #67

Closed
nuhkoca opened this issue Oct 29, 2020 · 2 comments
Closed

Still getting EISDIR: illegal operation on a directory, read #67

nuhkoca opened this issue Oct 29, 2020 · 2 comments

Comments

@nuhkoca
Copy link

nuhkoca commented Oct 29, 2020

Hello,

I am still getting EISDIR: illegal operation on a directory, read error despite the fact that I followed solutions in #35. Here is my sample .yml content. Can you please tell me what I am doing wrong? Thanks!

      - name: Upload Sample Artifacts
        uses: actions/upload-artifact@v2
        if: always()
        with:
          name: release-apk
          path: app_name/build/outputs/apk

      - name: Download the artifact
        uses: actions/download-artifact@v2
        with:
          name: release-apk
          path: release-apk

      - name: Create Release
        id: create_release
        uses: actions/create-release@v1
        env:
          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
        with:
          tag_name: ${{ github.ref }}
          release_name: Release ${{ github.ref }}
          draft: false
          prerelease: false

      - name: Upload Release Asset
        id: upload-release-asset
        uses: actions/upload-release-asset@v1
        env:
          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
        with:
          upload_url: ${{ steps.create_release.outputs.upload_url }}
          asset_path: release-apk
          asset_name: ${{ github.ref }}
          asset_content_type: application/zip
@nuhkoca nuhkoca closed this as completed Oct 30, 2020
@lgtmbro
Copy link

lgtmbro commented Nov 4, 2020

having the same issue, did you find a solution?

@nuhkoca
Copy link
Author

nuhkoca commented Nov 4, 2020

Hi @howzitcal

Yes! The main part here is that download-artifact always downloads and unzip files to the target directory. Since I missed unzipping logic, I was pretty confused. I continuously tried to access the zipped file with its explicit name which I specify in upload-artifact step. Instead, I solved this by accessing its unzipped file name. For example;

  • I upload my artifacts under release-apk name. It is a zip file. Remember, upload-artifact always works with zip operation.
  • I download the zipped files to the root directory. Remember, the file name is release-apk and path is ./
  • Previous step downloaded and unzipped the files into the root directory. The file name is my-artifact.apk in my case.
  • You can use below bash command to list files/folders recursively.
- name: Display structure of downloaded files
  run: ls -R
  • Then I accessed my file with its explicit name(my-artifact.apk) in upload-release-asset step.

Please let me know if you need any help.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants