Allow JJB Cache directory to be configured 43/13343/2
authorTrevor Bramwell <tbramwell@linuxfoundation.org>
Tue, 6 Nov 2018 00:30:38 +0000 (16:30 -0800)
committerTrevor Bramwell <tbramwell@linuxfoundation.org>
Wed, 14 Nov 2018 20:58:54 +0000 (12:58 -0800)
commit6cc9dc4bf43d4675704ab3bfe8feb0bcc8dd6472
treeb7fceeff952d7eb3543bda6f17f9ca5f220edc86
parent59fddb14b61b70dcdc2abde099c8a8c8f313d891
Allow JJB Cache directory to be configured

When JJB is ran concurrently on the same system with caching enabled, a
timeout can occur when one job fails after waiting 1 minute to aquire
the lock on the JJB cache directory.

Even if caching is disabled/ignored this timeout can still occur as JJB
always tries to lock the cache directory.

Having the ability to configure the cache directory will allow projects
to override it dynamically (with Jenkins env-vars) and run concurrent
jobs on the same node.

Change-Id: I1187847f658e754621369005e627a0f33a0253bc
Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
docs/jjb/lf-ci-jobs.rst
jjb/lf-ci-jobs.yaml
releasenotes/notes/jjb-cache-3a564a6943a5385e.yaml [new file with mode: 0644]