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
To support unit and integration tests that run on supported GPU hardware, we utilize Amazon EC2 instances to run the jobs of Github Actions that require this hardware.
In order to facilitate starting an EC2 instance, registering the instance as a self-hosted runner of this repository and shut it down (and remove it as a runner), we use this Github action: https://github.com/machulav/ec2-github-runner
Generally, the structure of running a task that requires a specific instance type looks like:
Start runner (outputs registered runner label)
Configure AWS credentials
Start runner instance of specified type
Run task
Run the required task (runs-on: Start runner's output label)
Stop runner
Configure AWS credentials
Stop runner instance
Start runner and stop runner run on default Github actions Linux instances.
Registering EC2 Instances as Github Actions Self-Hosted Runners
The ec2-github-runner action takes care of starting the EC2 instance and getting it registered to the repository as a self-hosted Github Actions runner. To do this it requires the permissions provided by a token with repo access (see the action's documentation for further details). The token is provided as a Actions repo secret and the actions run as pull_request_target so that job definitions always run from the target branch of a PR for security.
Generating required token
If the token that provides these permissions expires or needs to be regenerated, a maintainer can follow these steps to make and register a new one:
Go to your GH account settings Developer->Personal Access Tokens->Tokens(classic)
Make a new token with repo permissions, copy the token
Go to the repo's Settings->Secrets and Variables->Actions
Either edit the existing token or add a new one if you want to change the name, paste in the value
CIIssues related to the Github actions CI/CD. For build issues use CMake/Build
1 participant
Heading
Bold
Italic
Quote
Code
Link
Numbered list
Unordered list
Task list
Attach files
Mention
Reference
Menu
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Introduction
To support unit and integration tests that run on supported GPU hardware, we utilize Amazon EC2 instances to run the jobs of Github Actions that require this hardware.
In order to facilitate starting an EC2 instance, registering the instance as a self-hosted runner of this repository and shut it down (and remove it as a runner), we use this Github action: https://github.com/machulav/ec2-github-runner
Generally, the structure of running a task that requires a specific instance type looks like:
Start runner and stop runner run on default Github actions Linux instances.
Registering EC2 Instances as Github Actions Self-Hosted Runners
The
ec2-github-runneraction takes care of starting the EC2 instance and getting it registered to the repository as a self-hosted Github Actions runner. To do this it requires the permissions provided by a token withrepoaccess (see the action's documentation for further details). The token is provided as a Actions repo secret and the actions run aspull_request_targetso that job definitions always run from the target branch of a PR for security.Generating required token
If the token that provides these permissions expires or needs to be regenerated, a maintainer can follow these steps to make and register a new one:
Beta Was this translation helpful? Give feedback.
All reactions