Is this a request for help?:
No
Is this a BUG REPORT or FEATURE REQUEST?:
FEATURE REQUEST
Current version of jenkins helm chart doesn't support external backup and restore mechanism for job history (some people use it for apps versioning).
For temporary solution I have init-container running along with jenkins-master which backups in some period of time.
tar -C /var/jenkins_home -z --exclude jobs/*/config.xml --exclude jobs/*/workspace* --exclude jobs/*/simulation.log -c config-history jobs -f backup
then backup can be uploaded e.g. to s3 bucket and restored during jenkins startup.
But there are some limitation of this approach.
Which chart:
stable/jenkins
This might be relevant: https://github.com/artsy/jenkins-backup-s3
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale
I would vote for this feature. It would be of great interest to have a way to restore the job history. Even on an chart upgrade.
@svyotov @muehlburger ok guys, if you want I can make a PR with automated backup and restore in place :)
but the question is - will it be accepted as a solution?
Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten
/remove-lifecycle stale
Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close
Most helpful comment
This might be relevant: https://github.com/artsy/jenkins-backup-s3