mirror of
https://gitea.com/gitea/act_runner.git
synced 2026-08-03 05:13:10 +00:00
0cd0e52a24
Starting two runner daemons with the same `.runner` file makes both present an identical UUID+token, so Gitea treats them as one runner and they cancel each other's jobs. This adds a non-blocking advisory lock on a sibling `<runner-file>.lock`: the daemon (and `register`) acquire it at startup, and a second process on the same host fails fast with a clear error instead of silently interfering. The OS releases the lock when the process exits — including a hard kill — so no stale lock is left behind. Legitimate multi-runner setups are unaffected since each already uses its own `runner.file`. Note: this covers the common single-host case; two hosts sharing a copied `.runner` (e.g. over NFS) would still need server-side detection in Gitea. --------- Co-authored-by: Zettat123 <zettat123@gmail.com> Reviewed-on: https://gitea.com/gitea/runner/pulls/1099 Reviewed-by: Zettat123 <39446+zettat123@noreply.gitea.com>
17 lines
199 B
Plaintext
17 lines
199 B
Plaintext
/gitea-runner
|
|
.env
|
|
!/act/runner/testdata/secrets/.env
|
|
.runner
|
|
.runner.lock
|
|
coverage.txt
|
|
.tmp/
|
|
/config.yaml
|
|
|
|
# Jetbrains
|
|
.idea
|
|
# MS VSCode
|
|
.vscode
|
|
__debug_bin
|
|
# gorelease binary folder
|
|
/dist
|
|
.DS_Store |