Status: Open (View Workflow)
From an end-user's point of view, having multiple plugins with overlapping functionality for this is not good.
I think that you are making a really nice job, but merging your work with the work realized by tofuatjava in the thinBackup will result in excellent plugin to do really goods backups.
Please, could you speak with tofuatjava?
Thank you very much.
Really i think that this collaboration can be very successful for the Jenkins project.
Any update on this issue? Are there any plans in the near future to merge Backup and ThinBackup plugin features?
From an end-users point of view it is a must-have plugin.
Its been quite sometime that these plugins were not merged. I have a feeling that different owners of the plugins are more rigid on their decision on list of features and architecture. Once they decide on what they want to do and provide in that plugin, they either get busy with their time and/or do not have time anymore to support or fix issues with it. That has been the case with all the three plugins. I do not see anyone working and fixing or improving open issues/features. Anyone has any update on where we stand on merging these plugins?
There is a small problem when I use a dedicated volume for the backup:
SEVERE: Cannot perform a backup. Please be sure jenkins/hudson has write privileges in the configured backup path '/var/backup/jenkins'.
java.io.IOException: Failed to list contents of /var/lib/jenkins/lost+found
The workaround is quite clear. On the other hand: 'lost+found' is a well known name, thinBackup should ignore it if it is unreadable.
I've added a document in the wiki to avoid having dozens of plugins doing the same thing: https://wiki.jenkins-ci.org/display/JENKINS/Before+starting+a+new+plugin