-
Bug
-
Resolution: Unresolved
-
Major
-
None
-
Jenkins 2.206 Lockable Resources 2.7
Jenkins 2.221 Lockable Resources 2.7
Scenario:
Create new Jenkins project of type Freestyle
Enable lockable resources option and provide for field Label valid label value, for example OPERA
Run build
org.jenkins.plugins.lockableresources LOGGER output
aLogger shows that check has been run 2 times, although first run should be enough as all resources were free and was acquired during 1st run
This behaviour can be reproduced also if running Groovy script
With more complex Groovy scripts it can be noticed that check sometimes runs more then 2 times although first check was successful, when it is run 2nd time it messes with resource count check, and then it is run again two more times