oneapi-src / oneapi-src/unified-memory-framework

[CI] Cleaning self-hosted runners

Open
#630 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement
Dominant language
C
Stars
98
Forks
48
Avg merge
3d 20h
Merged PRs (30d)
6

Description

[CI] Cleaning self-hosted runners

Rationale

There is a need to harden self-hosted runners. Typically there are a few ways to do that:

From my point of view, the first option is the easiest to adopt, just one shell script with passing as an input when running a runner.
ACTIONS_RUNNER_HOOK_JOB_STARTED=cleaning_script.sh ACTIONS_RUNNER_HOOK_JOB_COMPLETED=cleaning_script.sh ./run.sh

Description

API Changes

None, transparent from the workflow point of view.

Implementation details

Depending on the chosen approach, other implementation requirements will be mostly related to the infrastructure setup.

Meta

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the linked GitHub Actions documentation on pre- and post-job hooks, then compare that approach with ARC and volatile VMs using the options listed in the issue. Define the infrastructure changes needed to clean self-hosted runners and confirm that workflows remain unchanged after the selected approach is adopted.

Written by the indexing model from the issue text.

Assessment

Tech stack
github-actions, shell
Domain
ci-cd, infrastructure
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.