Prevent running multiple instances of the gitlab-runner process using the same configuration file
What does this MR do?
Adds a lock mechanism that effectively prevents running two GitLab Runner processes, when they are started using the same configuration file.
Why was this MR needed?
Please read #4407 (closed) for context.
Are there points in the code the reviewer needs to double check?
After the base MR will be merged, target branch here should be changed to master
and
only then we can remove the WIP status.
Does this MR meet the acceptance criteria?
-
Documentation created/updated -
Added tests for this feature/bug -
In case of conflicts with master
- branch was rebased
What are the relevant issue numbers?
Closes #4407 (closed)
Edited by Tomasz Maczukin