8 -STACK_RUNNING_DIR = "/var/lib/jenkins/cu2d/work"
9 -STACK_STATUS_PUBLISHING_DIR = "/var/lib/jenkins/cu2d/result_publishing"
10 +STACK_RUNNING_DIR = "/iSCSI/jenkins/cu2d/work"
11 +STACK_STATUS_PUBLISHING_DIR = "/iSCSI/jenkins/cu2d/result_publishing"
Francis: are you sure about those changes?
the stacks run and we were able to publish content, so it means (I ls /var/lib/jenkins/cu2d/work and see latest content here). Can you double check? What's in "/var/lib/jenkins/cu2d/work" then and why does it work with some autopilot tests (like sdk today)
On changing latest_autopilot_results and stack_status, jibel did those scripts, so better to check with him
8 -STACK_RUNNING_DIR = "/var/lib/ jenkins/ cu2d/work" STATUS_ PUBLISHING_ DIR = "/var/lib/ jenkins/ cu2d/result_ publishing" jenkins/ cu2d/work" STATUS_ PUBLISHING_ DIR = "/iSCSI/ jenkins/ cu2d/result_ publishing"
9 -STACK_
10 +STACK_RUNNING_DIR = "/iSCSI/
11 +STACK_
Francis: are you sure about those changes?
the stacks run and we were able to publish content, so it means (I ls /var/lib/ jenkins/ cu2d/work and see latest content here). Can you double check? What's in "/var/lib/ jenkins/ cu2d/work" then and why does it work with some autopilot tests (like sdk today)
On changing latest_ autopilot_ results and stack_status, jibel did those scripts, so better to check with him