send via e-mail from sarchule@hotmail.com on March 13th, 2012:
Hi Thomas, Matthias,
From the thinBackup web page:
"Please let us know if you would have another option or feature for this plugin by simply enter an issue or write us an email. THANKS"
I've been using your thinBackup client and it's worked out great. We're now starting to take advantage of Jenkins built-in web server whose content is stored in the JENKINS_HOME\userContent folder. I'd like to request a feature such that content within this folder could optionally be included in the backup. The entry field for the settings might work similar to other plugins which allow a list of files (and wildcards) to be specified, but this is simply a suggestion.
For example:
Files within userContent folder to backup: index.html, topic1\foo.html, topic2\myfile.txt => backup specific files
or
Files within userContent folder to backup: ** => backup all folders and files, recursively
or
Files within userContent folder to backup: **.html => backup all .html files, recursively
In keeping with the spirit of a "thin" backup, it would be sufficient to simply backup files directly under userContent or perhaps only specific files (first example above). However, obviously, it would be much more flexible if it could include any content (files or folders) within userContent.
Thanks for considering this new feature,
Steve
send via e-mail from sarchule@hotmail.com on March 13th, 2012:
Hi Thomas, Matthias,
From the thinBackup web page:
"Please let us know if you would have another option or feature for this plugin by simply enter an issue or write us an email. THANKS"
I've been using your thinBackup client and it's worked out great. We're now starting to take advantage of Jenkins built-in web server whose content is stored in the JENKINS_HOME\userContent folder. I'd like to request a feature such that content within this folder could optionally be included in the backup. The entry field for the settings might work similar to other plugins which allow a list of files (and wildcards) to be specified, but this is simply a suggestion.
For example:
Files within userContent folder to backup: index.html, topic1\foo.html, topic2\myfile.txt => backup specific files
or
Files within userContent folder to backup: ** => backup all folders and files, recursively
or
Files within userContent folder to backup: **.html => backup all .html files, recursively
In keeping with the spirit of a "thin" backup, it would be sufficient to simply backup files directly under userContent or perhaps only specific files (first example above). However, obviously, it would be much more flexible if it could include any content (files or folders) within userContent.
Thanks for considering this new feature,
Steve