Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-25147

Cannot access pom.xml directory after Jenkins update


    • Icon: Bug Bug
    • Resolution: Not A Defect
    • Icon: Major Major
    • maven-plugin
    • Windows 7
      Jenkins 1.565.2
      Maven Project Plugin 2.6
      Subversion Plugin 2.4.3

      After updating Jenkins from 1.551 to 1.565.2, some of our Maven-type jobs fail with the following message:

      "[INFO] Scanning for projects...
      [ERROR] The build could not read 1 project -> [Help 1]
      org.apache.maven.project.ProjectBuildingException: Some problems were encountered while processing the POMs:
      [FATAL] Non-readable POM D:\Jenkins\Jobs\JobName\workspace\JobName-test: D:\Jenkins\Jobs\JobName\workspace\JobName-test (Access is denied)"

      D:\...\JobName-test contains the pom.xml.

      It happens when Maven is called through "Invoke top-level Maven targets".
      Maven Version: (Default)
      Goals: verify -X -f "D:\Jenkins\Jobs\JobName\workspace\JobName-test" -Dparam1=abc -Dparam2=def -Dparam3=10

      The Jenkins user account on Windows has all access rights on the Jenkins directories and files.

      The odd thing about this is that we have another set of Maven-type jobs that run just fine, with the same kind of build step. The only difference is that those are generated from a template job while the failing ones are not. All of them worked fine before the update.

      Unfortunately, reconstruction of this error is somewhat complicated since we have an issue with Jenkins giving no SVN credentials that sometimes aborts the build at an earlier point. ( https://issues.jenkins-ci.org/browse/JENKINS-25149 ) I suspect they might be related because the Jenkins update seems to have triggered them both.

            stephenconnolly Stephen Connolly
            hjen Jennifer Hofmeister
            0 Vote for this issue
            2 Start watching this issue