Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

ovirt-engine maven caching configuration in CI prevents using mock_runner locally

Description

The engine STD-CI is configured currently to store the maven cache on the slave in '/home/jenkins/maven_cache'. This works well in CI but effectively renders that STD-CI scripts unusable for people trying to run 'mock_runner.sh' locally with the engine repo.

We need to move the cache somewhere else that would be writeable on any machine. '/var/tmp' seems like a good candidate.

Activity

Show:

Barak Korren April 1, 2018 at 12:43 PM

I don't thing this would be suitable as a 1st task, fixing this properly may require adding features to mock_runner.sh

Eyal Edri April 1, 2018 at 11:46 AM

can this count as 'first task' candidate? did we get complaints on it recently?

Barak Korren September 28, 2017 at 9:26 AM

Maybe we should just fix mock_runner so it can run 'mkdir' as root, this way we can just put the cache in '/var/cache' which is where caches belong.

Eyal Edri September 28, 2017 at 9:22 AM

So do we have any decision on how to solve it? IIRC we had a thread on devel list that didn't lead to a conclusion.

Barak Korren September 28, 2017 at 8:18 AM

The impact is that mock_runner cannot currently be used locally with our flagship project. This is a big stain on the set of capabilities we are supposed to be providing.

Details

Assignee

Reporter

Blocked By

Components

Priority

Created May 7, 2017 at 8:57 AM
Updated June 24, 2018 at 8:09 AM