support RUNNER_TRACKING_ID background job #12783

New Issue

GiteaMirror · 2025-11-02T10:20:56-06:00

GiteaMirror commented

2025-11-02 10:20:56 -06:00

Originally created by @PterX on GitHub (Apr 5, 2024).

Feature Description

ref: https://github.com/actions/runner/issues/598#issuecomment-721151364

Screenshots

No response

Originally created by @PterX on GitHub (Apr 5, 2024). ### Feature Description ref: https://github.com/actions/runner/issues/598#issuecomment-721151364 ### Screenshots _No response_

GiteaMirror added the type/proposal label 2025-11-02 10:20:56 -06:00

GiteaMirror commented

2025-11-02 10:20:56 -06:00

@ChristopherHX commented on GitHub (May 12, 2024):

The act_runner has no process tree kill mechanism, so it always behave like setting RUNNER_TRACKING_ID to ""

Setup an unsecure runner using mybackgroundjobs:host as label
- the only possible mode of actions/runner, default docker container are a gitea/act extension
- to bypass creating a docker container that would kill any background job
Just start the background process and act_runner doesn't care about it
- you can set RUNNER_TRACKING_ID="" like described in the referenced issue if you want to support both GitHub and Gitea Actions

@ChristopherHX commented on GitHub (May 12, 2024): The act_runner has no process tree kill mechanism, so it always behave like setting RUNNER_TRACKING_ID to "" - Setup an unsecure runner using `mybackgroundjobs:host` as label - the only possible mode of actions/runner, default docker container are a gitea/act extension - to bypass creating a docker container that would kill any background job - Just start the background process and act_runner doesn't care about it - you can set RUNNER_TRACKING_ID="" like described in the referenced issue if you want to support both GitHub and Gitea Actions

GiteaMirror commented

2025-11-02 10:20:57 -06:00

@PterX commented on GitHub (May 12, 2024):

The act_runner has no process tree kill mechanism, so it always behave like setting RUNNER_TRACKING_ID to ""

Setup an unsecure runner using mybackgroundjobs:host as label

the only possible mode of actions/runner, default docker container are a gitea/act extension

to bypass creating a docker container that would kill any background job

Just start the background process and act_runner doesn't care about it

you can set RUNNER_TRACKING_ID="" like described in the referenced issue if you want to support both GitHub and Gitea Actions

thx for your help,I have got a way use systemd-run cmd run backgroud

@PterX commented on GitHub (May 12, 2024): > The act_runner has no process tree kill mechanism, so it always behave like setting RUNNER_TRACKING_ID to "" > > * Setup an unsecure runner using `mybackgroundjobs:host` as label > > * the only possible mode of actions/runner, default docker container are a gitea/act extension > * to bypass creating a docker container that would kill any background job > * Just start the background process and act_runner doesn't care about it > > * you can set RUNNER_TRACKING_ID="" like described in the referenced issue if you want to support both GitHub and Gitea Actions thx for your help,I have got a way use systemd-run cmd run backgroud

Sign in to join this conversation.

Branches Tags

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/gitea#12783