Dragoon already has file-locking implemented to prevent multiple jobs from running on the same file (and potentially causing weirdness), but we also don't want multiple copies of a job fighting over system resources like disk, RAM, etc.
Maybe this could be an option, in case someone does want the same copy of the job to run multiple times.
Dragoon already has file-locking implemented to prevent multiple jobs from running on the same file (and potentially causing weirdness), but we also don't want multiple copies of a job fighting over system resources like disk, RAM, etc.
Maybe this could be an option, in case someone does want the same copy of the job to run multiple times.
gballan
added the bug label 2022-07-17 16:55:33 -04:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Dragoon already has file-locking implemented to prevent multiple jobs from running on the same file (and potentially causing weirdness), but we also don't want multiple copies of a job fighting over system resources like disk, RAM, etc.
Maybe this could be an option, in case someone does want the same copy of the job to run multiple times.