From 6e237c4369530b509a6fc997cc4bda08ff81a90b Mon Sep 17 00:00:00 2001 From: Darragh Bailey Date: Thu, 15 Sep 2016 11:01:37 +0100 Subject: Allow using lockfile per jenkins master 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 --- requirements.txt | 1 + 1 file changed, 1 insertion(+) (limited to 'requirements.txt') diff --git a/requirements.txt b/requirements.txt index 4f19904e..07e73a21 100644 --- a/requirements.txt +++ b/requirements.txt @@ -6,3 +6,4 @@ PyYAML>=3.10.0 # MIT pbr>=1.8 # Apache-2.0 stevedore>=1.17.1 # Apache-2.0 python-jenkins>=0.4.8 +fasteners -- cgit