-
Bug
-
Resolution: Fixed
-
Critical
-
None
-
jenkins 2.54 lockable resources plugin 2.0
We are doing automated regression testing with jenkins and using the lockable resources plugin to run one test job at a time. But sometimes it fails to acquire the lock on the testing system and one or more test job starts before the first one finished depending on when the lockable resource plugin starts to work again. Example wrong behavior:
17:09:23 Started by timer
17:09:23 [lockable-resources] acquired lock on []
17:09:23 [EnvInject] - Loading node environment variables.
Please tell me what kind of logs do you need to debug this issue.
- relates to
-
JENKINS-47235 lockable-resources resource autocomplete creates faulty resource names
-
- Resolved
-
- links to
[JENKINS-43574] Lockable resources plugin does not take effect
Priority | Original: Major [ 3 ] | New: Critical [ 2 ] |
Description |
Original:
We doing automated regression testing with jenkins and using the lockable resources plugin to run one test job at a time. But sometimes the fails the acquire the lock on the testing system and one or more test job start before the first one finished depending on when the lockable resource plugin starts to working again. Example wrong behavior: *17:09:23* Started by timer*17:09:23* [lockable-resources] acquired lock on []*17:09:23* [EnvInject] - Loading node environment variables. Please tell me what kind of logs do you need to debug this issue. |
New:
We doing automated regression testing with jenkins and using the lockable resources plugin to run one test job at a time. But sometimes it fails to acquire the lock on the testing system and one or more test job starts before the first one finished depending on when the lockable resource plugin starts to work again. Example wrong behavior: *17:09:23* Started by timer *17:09:23* [lockable-resources] acquired lock on [] *17:09:23* [EnvInject] - Loading node environment variables. Please tell me what kind of logs do you need to debug this issue. |
Description |
Original:
We doing automated regression testing with jenkins and using the lockable resources plugin to run one test job at a time. But sometimes it fails to acquire the lock on the testing system and one or more test job starts before the first one finished depending on when the lockable resource plugin starts to work again. Example wrong behavior: *17:09:23* Started by timer *17:09:23* [lockable-resources] acquired lock on [] *17:09:23* [EnvInject] - Loading node environment variables. Please tell me what kind of logs do you need to debug this issue. |
New:
We are doing automated regression testing with jenkins and using the lockable resources plugin to run one test job at a time. But sometimes it fails to acquire the lock on the testing system and one or more test job starts before the first one finished depending on when the lockable resource plugin starts to work again. Example wrong behavior: *17:09:23* Started by timer *17:09:23* [lockable-resources] acquired lock on [] *17:09:23* [EnvInject] - Loading node environment variables. Please tell me what kind of logs do you need to debug this issue. |
Link |
New:
This issue relates to |
Remote Link | New: This issue links to "PR #89 (Web Link)" [ 20030 ] |
Resolution | New: Fixed [ 1 ] | |
Status | Original: Open [ 1 ] | New: Resolved [ 5 ] |