Uploaded image for project: 'Infrastructure'
  1. Infrastructure
  2. INFRA-2555

Jenkins Build Fails After Switching to New Network Share

    XMLWordPrintable

    Details

    • Similar Issues:

      Description

      At my company we are running Jenkins to checkout files from a SVN repository to a network share (using custom work space). Now that we have to start deploying to a different network share, all of a sudden the build will randomly fail after an undetermined amount of files are checked out. Sometimes 30 files check out sometimes 2. There are over 2000 files in the repository. The only difference between the build that originally worked for years and the new build is the custom work space path is different. The failed job only indicates that there are 'no more files.'

       

      org.tmatesoft.svn.core.SVNException: svn: E200030: java.io.IOException: There are no more files

       

      Engineers have double-checked permissions, McAfee on-access scanning, disk space and speed on the network share, timeout and keep-alive rules; and we just can't figure out why builds to the new network share do not work.

       

      I've attached the logs from the failed build and the loggers on the subversion plugin.

        Attachments

        1. failed_build.txt
          15 kB
          Jeff Stewart
        2. scm_log.txt
          351 kB
          Jeff Stewart

          Activity

          There are no comments yet on this issue.

            People

            Assignee:
            Unassigned Unassigned
            Reporter:
            jeffstewart Jeff Stewart
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: