stale[bot]
commented
3 years ago This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Any further update will cause the issue/pull request to no longer be considered stale. Thank you for your contributions.
Is your feature request related to a problem? Please describe.
The backup process copies many file paths to S3, which creates some bloat. The bloat costs more to store in S3, and bogs down both the backup and restore processes. The slow transfer speeds then create fragility, requiring the user to restart restore from scratch if the network has a hiccup.
There are hundreds upon hundreds of objects that should not be persisted in S3.
k8s://jenkins/jenkins-1620395207-0/jenkins/var/jenkins_home/caches/git-a552b9a1e0083d22fb0f201fb2f414b5/.git/objects/34/05d38e8afb3514faeb9386e3d70fa82cf6ffbf
...
Describe the solution you'd like
Limit file patterns accepted into backup media. I wonder if the restore procedure only needs a handful of text files, such as the primary XML configuration, and the Jenkins credentials. Whatever you would need to finish provisioning a fresh Jenkins deployment.
Note that the current skbn tool does not have the ability to remove file patterns, so we can instead specify the file patterns to include. So that skbn never witnesses a file pattern that we do not want to include.
Example solutions:
find