support RUNNER_TRACKING_ID background job about gitea

[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

[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

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