summaryrefslogtreecommitdiffstats
path: root/jenkins_jobs/cache.py
Commit message (Collapse)AuthorAgeFilesLines
* Fix the yaml load warning.Daniel Bengtsson2019-12-101-1/+1
| | | | | | | | | | | In the new version of PyYAML the API changed to be more explicit. Now the default value for the Loader is None, see: https://github.com/yaml/pyyaml/blob/5.1/lib3/yaml/__init__.py#L103 The load is unsafe. It's better to use safe_load function. Change-Id: Ia1cd16f2ff970ca220a266c99b6554dd4254ebd9
* Auto-generated output from python-blackThanh Ha2019-09-091-20/+25
| | | | | | | | | Please review the following patch containing the code changes in the repo. This patch is a transition patch and is the auto-generated output of the python-black tool. Change-Id: I2d2de71da8a105fb62b561899ae78441ddab4032 Signed-off-by: Thanh Ha <zxiiro@gmail.com>
* Fix flake8 failures and make its execution more consistentSorin Sbarnea2018-10-281-1/+1
| | | | | | | | | | | | | | | | - upgrade flake8 to 3.6.0 - remove use of hacking since pre-commit replaced it - mentioned minimal flake8 version on pre-commit config - fixed newer linting errors - disable W504 as it seems not possible to fix (conflict with W403) - replaced buggy tox deps installation with native pip install, which address the issue of missing to install new deps when the reqs files are updated, developer being forced to to recreate the virtualenv. - prepare for migration from tox-pep8 to tox-linters, now these being just aliases. Change-Id: I310578dce215aaf00a5b2d54716f90da9a1ecb4d Depends-On: https://review.openstack.org/#/c/613726/
* re-raise the original Exception instead of raising a new oneEvgeni Golov2017-11-061-1/+1
| | | | | | this preserves the error traceback and makes debugging easier Change-Id: Ia513ac009b81d35e3df11939771aa29e40700c08
* Allow using lockfile per jenkins masterDarragh Bailey2017-06-271-0/+23
| | | | | | | | | | | | | | | | | | 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
* Move CacheStorage to its own module.Wayne Warren2016-09-021-0/+117
And rename it to JobCache. The word "Cache" already implies "Storage" so it makes more sense to name it after the things that it stores...Jobs! Change-Id: If7a7a56e8f6a3637f62e285eaa7ba989f67002dc