We have a build helper custom plugin that used to work on Jenkins, but seems to
have stopped working.
The plugin fails to create a subdirectory in the Jenkins .m2 repository. I
suspect this is some kind of a permissions issue. You can see the evidence in
this raw log output from our last failed build:
[1] https://builds.apache.org/job/UIMA-AS/123/consoleText
For this run, we moved (temporarily) the .repository to the WORKSPACE, so we
could see it - it's here:
[2] https://builds.apache.org/job/UIMA-AS/ws/.repository/org/apache/uima/
The failing java code is attempting to create the previous directories for a new
file in the .m2 repo, using:
targetFile.getParentFile().mkdirs();
where targetFile (from [1] is
"/home/jenkins/jenkins-slave/workspace/UIMA-AS/.repository/org/apache/uima/uimaj/2.4.0/uimaj-2.4.0-bin.zip"
ThegetParentFile() should strip off the last piece, and make the new directories
"uimaj/2.4.0/" under .../org/apache/uima.
But it fails (no reason given). You can see that it fails in [2] - the
.../org/apache/uima/ directory has no sub directory "uimaj".
Can someone with ssh access to the build machine (ubuntu1) take a look and see
if there is some kind of permission issue? (I'm not sure what userid the build
runs as, and I don't know what "groups" the builder is a member of, and I don't
know what permissions are set on repository's .../org/apache/uima. Having
answers to these may enable us to debug this and move forward).
Thanks very much! -Marshall Schor
