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

Checking out a fresh workspace deletes symlink targets

    • Icon: Bug Bug
    • Resolution: Duplicate
    • Icon: Major Major
    • subversion-plugin
    • None
    • Platform: All, OS: Linux

      We use 'update' mode for our projects, because the checked out tree has local
      configuration settings added to it. We also have symlinks to various places.

      While trying to figure out why subversion had stopped updating, I did a
      $ svn switch --relocate http://... http://user@...

      This fixed the problem, but when I rebuilt, Hudson said:

      "Checking out a fresh workspace because the workspace is not svn+ssh:..."

      It then deleted the checkout, along with all our settings AND the contents of
      every directory pointed to by a symlink!

      This is probably related to:

      https://hudson.dev.java.net/issues/show_bug.cgi?id=585

          [JENKINS-783] Checking out a fresh workspace deletes symlink targets

          jbq added a comment -

          Care to mention which version you are using?

          jbq added a comment - Care to mention which version you are using?

          tal added a comment -

          Good question. It was either 132 or 135, but I can't remember whether I upgraded
          before or after the files got deleted. Sorry.

          tal added a comment - Good question. It was either 132 or 135, but I can't remember whether I upgraded before or after the files got deleted. Sorry.

          Fix to #585 was incomplete.

              • This issue has been marked as a duplicate of 585 ***

          Kohsuke Kawaguchi added a comment - Fix to #585 was incomplete. This issue has been marked as a duplicate of 585 ***

          tal added a comment -

          Thanks.

          By the way, I managed to recover the contents of the symlink targets, because
          Hudson also follows symlinks when archiving the build (no wonder the
          'publishing' phase took so long!) so there were copies in the builds directory!

          tal added a comment - Thanks. By the way, I managed to recover the contents of the symlink targets, because Hudson also follows symlinks when archiving the build (no wonder the 'publishing' phase took so long!) so there were copies in the builds directory!

            Unassigned Unassigned
            tal tal
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved: