![]() |
|
|
|
|
Issue Type:
|
![Bug]() Bug
|
|
Affects Versions:
|
current |
|
Assignee:
|
rsandell
|
|
Components:
|
external-resource-dispatcher |
|
Created:
|
10/Apr/13 9:33 AM
|
|
Description:
|
The plugin allows to configure resources that have names, but no IDs. This breaks the locking mechanism.
The plugin should check this requirement for all inputs or use other distictions than the specified ID for the internal locking mechanism.
Steps to reproduce:
- Create two resources with different names, without specifiing an ID
- give those resources an equal property (e.g. type=tablet)
- create two jobs requiring one of these two resources (selection criterium: type=tablet)
- execute the two jobs in parallel
Expected result:
- both resources get locked and then unlocked by the two jobs
Actual result:
- the first job that finished will do well, unlocking the first resource
- the second jobs fails to unlock it's resource, stating WARNING The resource has already been unlocked by some other means.
- the second resource remains locked
|
|
Environment:
|
Windows 7, Jenkins 1.500
|
|
Project:
|
Jenkins
|
|
Priority:
|
![Major]() Major
|
|
Reporter:
|
Benjamin Debeerst
|
|
|
|
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
|
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
[email protected].
For more options, visit
https://groups.google.com/groups/opt_out.
