logs from GitHub Actions · python

Stream: python

Topic: logs from GitHub Actions

Philip Durbin 🚀 (Sep 24 2025 at 14:56):

@Jan Range see https://github.com/gdcc/api-test-runner

Philip Durbin 🚀 (Sep 24 2025 at 14:56):

      - name: Dump docker logs on failure
        if: failure()
        uses: jwalton/gh-docker-logs@v2
        with:
          dest: './logs'
      - name: Tar logs
        if: failure()
        run: tar cvzf ./logs.tgz ./logs
      - name: Upload logs to GitHub
        if: failure()
        uses: actions/upload-artifact@master
        with:
          name: logs.tgz
          path: ./logs.tgz

Jan Range (Sep 24 2025 at 16:59):

@Philip Durbin 🚀 I have added the log saves to the script in pyDataverse. Will add it to the action as well now

Jan Range (Sep 24 2025 at 18:50):

Looking at the GitHub Action, adding the log step as a post-step will be difficult. Since we are using a composite action, all steps defined will be run in sequence, and only then the next steps in any CI will be taken. Either we rewrite the action in JavaScript, which allows both pre- and post-runs, or we simply document how one can retrieve the logs in the CI. What are your thoughts?

Jan Range (Sep 24 2025 at 19:51):

Okay, I went down the Node actions rabbit hole with a little help from Claude, and I think I am almost there. Only thing missing is that the logs are pushed as artifacts, but they are present in the action runs now :slight_smile:

https://github.com/gdcc/dataverse-action/actions/runs/17987836304/job/51170398822