-
Improvement
-
Resolution: Unresolved
-
Minor
Until now, plugins are archived as a list which makes Jenkins, when restored, re-download and re-install the plugins.
Alternatively, there should be an option to archive the actual plugin archives themselves.
Also, It is not possible to archive arbitrary files that aren't selected by the built-in filters. It would be useful to allow for an arbitrary regex pattern to select additional files, since oftentimes plugins use config files that fall outside of the backup set.
What's wrong with the idea to save only the meta data of the plugins and download/install it during restore operation? Why do you want to save data which already stored in the internet.
Don't get me wrong I only want to understand your usecase, because I'm currently working an thinbackup 2.0 with several improvements.