6e237c4369
When a jjb run is thrown when another jjb is already running, it can cause corruption of cache. Start using a fasteners to ensure this won't be happening and run securely on automated systems. Ensure unlock is called from only the destructor, so that it is only called when the JJB process is guaranteed to be finished using it. Make it obvious that _lock is intended to be internal to the cache storage implementation. Potentially we may not need to call it at all, as python might unlock it for us on exit by closing the file when no longer needed. However better to make it explicit. Change-Id: I53a1f92cf2bfbbe87c9ea205c377f93869353620
10 lines
333 B
Plaintext
10 lines
333 B
Plaintext
# The order of packages is significant, because pip processes them in the order
|
|
# of appearance. Changing the order has an impact on the overall integration
|
|
# process, which may cause wedges in the gate later.
|
|
six>=1.9.0 # MIT
|
|
PyYAML>=3.10.0 # MIT
|
|
pbr>=1.8 # Apache-2.0
|
|
stevedore>=1.17.1 # Apache-2.0
|
|
python-jenkins>=0.4.8
|
|
fasteners
|