gitea icon indicating copy to clipboard operation
gitea copied to clipboard

Published 20 hours ago • verified publisher icon go-gitea

support RUNNER_TRACKING_ID background job

Open PterX opened this issue 10 months ago • 2 comments

Feature Description

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

Screenshots

No response

PterX avatar Apr 05 '24 05:04 PterX

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 avatar May 12 '24 08:05 ChristopherHX

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 avatar May 12 '24 09:05 PterX