Introducing a watcher to reload changes has been proposed for Configuration-as-Code: https://github.com/jenkinsci/configuration-as-code-plugin/issues/76 just need to be implemented ...
Le mar. 15 janv. 2019 à 09:17, Carlos Sanchez <[email protected]> a écrit : > I thought about it, and yes it would be interesting to have an operator > that watches a configmap and ensures jenkins is always updated. > However with serverless jenkins[1] you wouldn't need to worry about that > anymore (if you can use serverless). > > > [1] > https://medium.com/@jdrawlings/serverless-jenkins-with-jenkins-x-9134cbfe6870 > > On Tue, Jan 15, 2019 at 6:37 AM 夏润泽 <[email protected]> wrote: > >> Hi dev: >> In the cloud native domain, kubernetes is an important part, and now >> many software are using kubernetes operator to manage applications in >> kubernetes. >> Now we can manage jenkins through groovy scripts, casc plugins, etc.In >> particular, the casc plugin allows us to manage jenkins with declarative >> code. >> But I think there are still some problems in it. I deployed my jenkins >> in the kubernetes cluster and managed my jenkins through the groovy script >> and the casc plugin. But once the jenkins is started, I need to modify the >> configuration of the casc, then I need to submit the configuration to the >> jenkins dashborad, and the submitted configuration is not necessarily >> successful, and there is no failure record. In other words, although I have >> a casc configuration file, it is difficult for me to ensure that my >> environment is consistent with the casc configuration. Or at least let me >> know that my current configuration is incorrect, I need to fix it. >> If we can provide an official jenkins operator to manage jenkins in >> kubernetes, it must be great. >> I hope to hear your opinions. >> >> Best wishes >> RunzeXia >> >> -- >> 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/7939b7df-2935-4aeb-a1f5-3f300990119f%40googlegroups.com >> <https://groups.google.com/d/msgid/jenkinsci-dev/7939b7df-2935-4aeb-a1f5-3f300990119f%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> For more options, visit https://groups.google.com/d/optout. >> > -- > 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/CALHFn6OYTfn4Bn_qJvtimvggJcSpHERm1m%2BTrqyV%2BVrEfYYDPg%40mail.gmail.com > <https://groups.google.com/d/msgid/jenkinsci-dev/CALHFn6OYTfn4Bn_qJvtimvggJcSpHERm1m%2BTrqyV%2BVrEfYYDPg%40mail.gmail.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 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/CANMVJzmk-ULGcGcPTpCoURQnTwEqwnuwxv6a_ZCFudD6a57g5w%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
