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

Broken symlinks in reused workspaces

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Major Major
    • p4-plugin
    • Jenkins ver 2.89.2
      java.version 1.8.0_51 (Oracle 64bit on RHEL6.6 [master])
      P4 Plugin 1.8.4

      It appears that when the workspace is cleaned by Jenkins after/before use, the targets of symlinks are deleted, but the symlinks themselves are not.

      We now have most workspaces containing dead symlinks - some of which were checked out of the Perforce repository, and some created during the build process (when they had valid targets). None of the symlinks point outside of the workspace - most (all?) are to another file/directory in the same parent directory.

      These builds are driven by Jenkinsfiles as DSL pipeline scripts.

      Explict error – build failure due to Archive trying to fingerprint a broken symlink.

            p4paul Paul Allen
            simon_watts Simon Watts
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: