OK, but that does not help with the build logs etc. i.e. If I loose my server, I not only want to recreate the instance, but I want to restore the build logs. This requirement may not be for everyone. But for people who consider the build history valuable it would be important to back that up also.
Unfortunately I do not think that Jenkins has an enterprise grade backup solution available out of the box. You have to put it together by yourself. And then there is no way to do it 100% correctly without a full shutdown of the Jenkins master at some point. Which is unfortunate, since that makes it impossible to have a high availability Jenkins that is also being backed up regularly and automatically at the same time. One can get close with clever use of a copy-on-write snapshotting file systems like Btrfs, but you will not have 100% guarantee that the snapshot is consistent since Jenkins has no quiescing facility. ________________________________________ From: Victor Martinez <[email protected]> Sent: 17 August 2017 13:52:08 To: Jenkins Users Cc: Artur Szostak Subject: Re: Affordable solution for Jenkins CI and build slaves in the cloud? My answer was suggesting how to move from traditional backup processes since there are already tools/frameworks, as you just mentioned, which help to configured everything fully as code. I guess, that's why it's related to backup :) -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/2022a80edcf74ceaacc3c68a3e4eaf61%40partner.eso.org. For more options, visit https://groups.google.com/d/optout.
