the "export" feature on JENKINS/configuration-as-code page will give you a yaml file to reflect your current configuration, but this is a very experimental feature with many limitations, so you can only use it as inspiration to write your own. Just will make it not as hard as fully starting from scratch.
Le mar. 18 sept. 2018 à 12:41, Mark Bidewell <mbide...@gmail.com> a écrit : > Will there be a pathway to migrate from normal Jenkins configuration to > Configuration as Code, or will server configuration need to be rewritten > from scratch? > > -- > 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/527e2d7f-0ca2-447b-815e-ce8062cdb751%40googlegroups.com > <https://groups.google.com/d/msgid/jenkinsci-users/527e2d7f-0ca2-447b-815e-ce8062cdb751%40googlegroups.com?utm_medium=email&utm_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > -- Nicolas De Loof -- 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/CANMVJz%3D31Yq1%3DixnrQAi8pxx-EaVdZoEsFxgikE3xETjcpRhJA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
