Open timja opened 10 years ago
Periodic backup plugins allows to backup configurations only.
It means that the most of job data won't be backed up.
See https://wiki.jenkins-ci.org/display/JENKINS/PeriodicBackup+Plugin
A Symbolink link to jobs folder would help if you backup the data manually using "don't follow symlinks" option (available in both cp and rsync)
The only thing, which could be done in the core, is a configurable jobs directory path. I'd say that it is not required due to workarounds above, but feel free to contribute
Yeah, it's useful advice for workarounds. And having a configuration option would be nice.
But mostly it would be nice if it was better behaved by default. Really, if you moved the job directory and didn't give the option, I think it'd be a vast improvement.
The 'Build Record Root Directory' option caused numerous bugs in build symlinks, job rename, job move, job delete, ... everything that could conceivably break.
Therefore I think the risk and effort just isn't worth it. Just create a symlink.
FWIW the motivation stated is questionable at best IMO. Don't use `cp` or `xcopy` to backup Jenkins home, use `tar`, `rsync` or `robocopy`, all of which allow specifying exclusion rules.
I have a bunch of projects on my jenkins server, and a bunch of them run on master. Backing up the jenkins root means archiving all that job data - which is not what I want. I just want the config data.
It would be WAY nicer if there were at least an option to store jobs in some other directory.
Originally reported by kwerle, imported from: job data should not live with jenkins config data