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

Support of symbolic links which are not done by jenkins

    • Icon: New Feature New Feature
    • Resolution: Unresolved
    • Icon: Minor Minor
    • thinbackup-plugin
    • None

      When I try to restore a thin backup, nothing happens. The Jenkins system log shows:

      Nov 12, 2013 3:50:56 PM INFO org.jvnet.hudson.plugins.thinbackup.ThinBackupMgmtLink doRestore
      Starting restore operation.
      Nov 12, 2013 3:51:00 PM SEVERE org.jvnet.hudson.plugins.thinbackup.ThinBackupMgmtLink doRestore
      Could not restore. Aborting.

      thinBackup version 1.7.4 on Jenkins 1.537 on OSX 10.8.5

      A good first step would be to update the code so the log contains information about the Exception being thrown (or is information about this exception being stored somewhere else?)

          [JENKINS-20547] Support of symbolic links which are not done by jenkins

          Thomas Fürer added a comment - - edited

          is just one backupset which causes this error?
          Are there any processes rsync, backup, .. which accesses this file?
          Where is the backup set located (network mount, local, usb, raid, ...)?

          Thomas Fürer added a comment - - edited is just one backupset which causes this error? Are there any processes rsync, backup, .. which accesses this file? Where is the backup set located (network mount, local, usb, raid, ...)?

          I happens for every backup set.
          There were no processes that accessed the backup files.
          The backup file was on a local hard disk.

          If I rename my "jobs" directory and create a new empty jobs directory, the backup succeeds. It doesn't like my jobs directory.

          One clue: My jobs directory is on a second partition via a symbolic link:
          /Users/Shared/Jenkins/Home/jobs -> /Volumes/Jenkins/jobs

          Chris Shearer Cooper added a comment - I happens for every backup set. There were no processes that accessed the backup files. The backup file was on a local hard disk. If I rename my "jobs" directory and create a new empty jobs directory, the backup succeeds. It doesn't like my jobs directory. One clue: My jobs directory is on a second partition via a symbolic link: /Users/Shared/Jenkins/Home/jobs -> /Volumes/Jenkins/jobs

          Thomas Fürer added a comment -

          changed to new feature, because the usecase is to link parts of the home directory

          Thomas Fürer added a comment - changed to new feature, because the usecase is to link parts of the home directory

          Thomas Fürer added a comment -

          thank you chris,
          this is the problem, it will not support links.

          can you explain my why you have the job configuration out of the home directory?

          Thomas Fürer added a comment - thank you chris, this is the problem, it will not support links. can you explain my why you have the job configuration out of the home directory?

          We were trying to get around an unfortunate flaw in the design of Jenkins - the "jobs" directory contains both inputs (config.xml) and outputs (the "builds" directory). Some of our builds can get quite large, so we moved the entire "jobs" directory to a separate partition where we could manage it better. We then regularly back up the config.xml files onto the primary partition.

          Chris Shearer Cooper added a comment - We were trying to get around an unfortunate flaw in the design of Jenkins - the "jobs" directory contains both inputs (config.xml) and outputs (the "builds" directory). Some of our builds can get quite large, so we moved the entire "jobs" directory to a separate partition where we could manage it better. We then regularly back up the config.xml files onto the primary partition.

            tofuatjava Thomas Fürer
            cscooper Chris Shearer Cooper
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: