Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

support: self-hosted runner #1085

Open
3 tasks done
bryantvolk opened this issue Aug 8, 2024 · 0 comments
Open
3 tasks done

support: self-hosted runner #1085

bryantvolk opened this issue Aug 8, 2024 · 0 comments
Assignees
Labels
support User support

Comments

@bryantvolk
Copy link

bryantvolk commented Aug 8, 2024

Checklist

  • I am using the latest version of this action.
  • I have read the latest README and followed the instructions.
  • I have read the latest GitHub Actions official documentation and learned the basic spec and concepts.

Describe your question

is it possible to use a self hosted runner for the pages build and deployment workflow that this triggers?

here's my job snippet

jobs:
  storybook:
    runs-on: self-hosted

    steps:
      - name: Checkout code
        uses: actions/checkout@v3

      - name: Deploy Storybook Staging
        if: github.ref != 'refs/heads/main'
        uses: peaceiris/actions-gh-pages@latest
        with:
          github_token: ${{ secrets.GITHUB_TOKEN }}
          publish_dir: ./storybook-static
          destination_dir: ./sb/${{ steps.branch-name.outputs.short_ref }}

i skipped all the fun stuff.

this results in my storybook job running on the runner self-hosted but the triggered pages build and deployment is running on the github hosted ubuntu-lastest or whatever.

this is an issue because the runner is timing out due to upload size/artifact count (presumably)

Relevant links

Public repository: not public
YAML config: see above
YAML workflow: see above

Relevant log output

the workflow has the annotation

The hosted runner lost communication with the server. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.

can't even read the logs for the upload artifacts step because there are so many it crashes my browser :)

Additional context.

No response

@bryantvolk bryantvolk added the support User support label Aug 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
support User support
Projects
None yet
Development

No branches or pull requests

2 participants