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

Run test plans on self-hosted GHA machines #92

Closed
wants to merge 0 commits into from

Conversation

galargh
Copy link
Contributor

@galargh galargh commented Dec 30, 2022

Description

This PR moves GHA workflows that are defined in this repository to self-hosted runners. The runners definition can be found here: https://github.com/pl-strflt/tf-aws-gh-runner/blob/main/runners.tf#L28

Why?

To address issues with:

  • storage needs
  • speed
  • flakiness
How?
Testing
  • CI (running on self-hosted runners)

id: config
with:
script: |
if (`${context.repo.owner}/${context.repo.repo}` === 'libp2p/test-plans') {
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That approach looks great. Do we need to take into account the fact that these jobs are used through reusable workflows?

https://docs.github.com/en/actions/using-workflows/reusing-workflows#using-github-hosted-runners

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If I understand the docs correctly, the context here will reference the caller repo which is exactly what we want. So if we call the reusable workflow from libp2p/test-plans, then we're going to use self-hosted runners. Otherwise, we'll fall back to the gh hosted ones.

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

Successfully merging this pull request may close these issues.

2 participants