|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
- [JIRA] (JENKINS-16426) Backup fails while co... [email protected] (JIRA)
- [JIRA] (JENKINS-16426) Backup fails whi... [email protected] (JIRA)
- [JIRA] (JENKINS-16426) Backup fails whi... [email protected] (JIRA)
- [JIRA] (JENKINS-16426) Backup fails whi... [email protected] (JIRA)
- [JIRA] (JENKINS-16426) Backup fails whi... [email protected] (JIRA)

There is no special reason why I would not include files in the job directory to the back up. The idea of thinBackup is to back up only a minimum set of configuration to keep it small and handy. As normally the jobs folder is under control of jenkins. I never would put files in this folder by my own. However, you have done it. I suggest to put the configurations under JENKINS_HOME (where all other global configurations are placed), alternativly I would suggest the userContent folder.
Including files in the job folder to the backup will also open the question why not include files in other jenkins controlled folders. So this will open a neverending task because several plugins (e.g. CloudBees Folders or Matrix Job Configuration) will have their own folder structure, which makes it complicated to back up only a minimal set of files.
Is, moving the files to the suggested folders, an option for you? If not I need to refactor some code and redefine some ideas, technical it is possible, but I'm not sure if I should do it at the moment.