On Friday, 25 January 2019 04:35:05 UTC+1, 夏润泽 wrote: >> Making backup of ~50GB is not good idea. I don't want to make snowflake. When new Jenkins master comes up it should starts with empty `$JENKINS_HOME` and jenkins-operator have to configure it to desire >> state. Backup is triggered before Jenkins master pod deletion and it have to be quick as possible. It have impact on how quick new Jenkins master can start up.
> I think pvc may be more suitable for the public than backup. You mentioned using aws s3 for backup. I don't think all users can use this solution. For example, using other cloud vendors or deploying in > a private environment, etc. PVC backup will be in options but it is not recommended. > I don't know much about the backup mechanism, it sounds like some state will be lost. In my scenario, I didn't use casc to manage all the configurations, such as role-strangy. Because this part of the > > configuration will change frequently, I will use the REST API provided by the plugin for processing. I believe there will be other users and other plugins that are not managed using the casc/groovy init script. I think you can do everthing with Jenkins via groovy scripts. Every single change in Jenkins configuration will be automatically applied by jenkins-operator. > In addition to the comments on pvc, I think the custom update center address is needed, my environment could not access Internet (maybe there are many such cases in China), we will build a private > update center in our own environment, To complete the update and download of the plugin I'm adding this feature to my TODO list. -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" 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-dev/b30e938d-3298-4732-abae-05a53f935405%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
