Details
-
Type:
Bug
-
Status: Open (View Workflow)
-
Priority:
Major
-
Resolution: Unresolved
-
Component/s: external-resource-dispatcher-plugin
-
Labels:None
-
Similar Issues:
Description
I frequently see two jobs using the same resource, whereas only one job has actually locked the resource. These jobs all have a SCM configured.
I suspect that the locking occurs too late (only after the check out). So, while the first job is updating the workspace the resource is not locked yet and the other job thinks he can use that same resource.
I solved this by increasing the reservation time in the External Resource Dispatcher Configuration and limit the checkout time (shorter than the reservation time of the jobs that ). But this is only workaround of course.
I guess that the actually locking of the resources happens too late: now it happens in the prebuild method of JobProperty whereas it should happen earlier (in the onStarted method of RunListener).