I have opened a ticket: 

https://jira.linuxfoundation.org/servicedesk/customer/portal/2/IT-17061

but I hear those are not readable by public,

so below is a copy of its contents.

Vratko.

---

Console of a failing [0] job, and not-failing [1] for comparison.
(Run #1751 was also failing the same way.)

The symptom:
12:15:31 ln: target './/mvn33-new/' is not a directory: No such file or directory

I noticed the path to installation script is different:
- 09:41:52 [mvn33-new] $ sh -e /w/tools/hudson.tasks.Maven_MavenInstallation/mvn33-new/hudson4189296939696778309.sh
+ 12:15:30 [mvn33-new] $ sh -e /tools/hudson.tasks.Maven_MavenInstallation/mvn33-new/hudson11229393165569659711.sh
(Notice the leading /w/.)

This particular job does not even use maven, except the final fdio-infra-shiplogs macro.

We will try to remove the installation step, but as the failure happens fairly early, other jobs (which do really need maven) are probably affected as well.

[0] https://jenkins.fd.io/view/csit/job/csit-trending-daily-master/1752/console
[1] https://jenkins.fd.io/view/csit/job/csit-trending-daily-master/1750/consoleFull