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

Failing to save build records to UNC path on Windows 7

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Not A Defect
    • Component/s: core
    • Labels:
      None
    • Environment:
      Windows 7, Ver 2.60.3, JAVA 1.8.0
    • Similar Issues:

      Description

      Hi,

      I can't figure out why jenkins is failing to right to a UNC path to generate the build records.

      Keeps failing with the error:

      No such file:
      file path to server share\buildjobname\62\log

       

      The share is fine, it has been set to allow access for anyone.

       

      Log shows following:

      Failed to save build record
      java.io.IOException: The system cannot find the path specified

      {{at java.io.WinNTFileSystem.createFileExclusively(Native Method) }}

      {{at java.io.File.createTempFile(Unknown Source) }}

      {{at hudson.util.AtomicFileWriter.<init>(AtomicFileWriter.java:68) }}
      Caused: java.io.IOException: Failed to create a temporary file in \\SERVER-SHARE\SoftwareGroup\private\Builds\JenkinsBuilds\CleanupJenkinsWorkspace\60
      {{at hudson.util.AtomicFileWriter.<init>(AtomicFileWriter.java:70) }}

      {{at hudson.util.AtomicFileWriter.<init>(AtomicFileWriter.java:57) }}

      {{at hudson.XmlFile.write(XmlFile.java:168) }}

      {{at hudson.model.Run.save(Run.java:1923) }}

      {{at hudson.model.Run.execute(Run.java:1792) }}

      {{at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) }}

      {{at hudson.model.ResourceController.execute(ResourceController.java:97) }}

      at hudson.model.Executor.run(Executor.java:405)

       

      Any help would be appreciated.

      Thanks

        Attachments

          Activity

          Hide
          markewaite Mark Waite added a comment -

          Closing as "Not a defect" on the assumption that it is a configuration error rather than a Jenkins bug.

          Asking for help in the Jenkins bug tracker severely limits the number of people who see your request for help. You're much more likely to receive help in the chat systems or on the mailing lists because there are many more people that read those locations than read Jenkins issue reports.

          Show
          markewaite Mark Waite added a comment - Closing as "Not a defect" on the assumption that it is a configuration error rather than a Jenkins bug. Asking for help in the Jenkins bug tracker severely limits the number of people who see your request for help. You're much more likely to receive help in the chat systems or on the mailing lists because there are many more people that read those locations than read Jenkins issue reports.

            People

            Assignee:
            Unassigned Unassigned
            Reporter:
            osanders Oliver
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: