Hi All, Following best practices, we moved our entire build structure to a per-project Jenkinsfile and agents where the various parts of builds happen. The Jenkinsfiles are stored in the git repositories involved and we are using multi-branch projects. All that is working file.
Our issue is that our Jenkins runs inside docker and the node configuration, certificates, and Jenkins system configuration is not yet stored in an SCM environment. We want that to happen so that we can restore Jenkins quickly from scratch if something happens, without having to go through the trouble of recreating the Agent structure from scratch and redefining the multibranch jobs. We've had a newbie or two (me as an example) accidentally blow out the docker config and lost our Jenkins Agent structure. It seems like the Configuration-as-Code plugin might work, but it is hard to get a sense that this can configure Jenkins in its entirety or whether we can take the existing configuration and import/convert it to that plugin, and how config moves in and out of it. Any Sense of this? Thanks, Randall -- 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 jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/dba1ce13-1770-4733-9c8f-f170a443b2b3%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
