There are some flags you can use to tune this behaviour: https://github.com/jenkinsci/configuration-as-code-plugin/blob/a6983ff60e0cf198ce02d7992bcba927197174db/test-harness/src/test/resources/io/jenkins/plugins/casc/validSelfConfig.yml#L1-L5
The default is to show an error page with what failed. > I concur. My initial impression is that JCasC lacks polish, and I was > surprised to see it promoted so heavily when issues like this remain. I think the consensus has been it's 'good enough', there's plenty of room for improvement, but in general it works 'just fine' for most use-cases On Thu, 24 Jun 2021 at 16:54, Basil Crow <[email protected]> wrote: > On Thu, Jun 24, 2021 at 2:18 AM Ullrich Hafner <[email protected]> > wrote: > > This is a very bad user experience (actually I don’t know of any other > application that does not start because of a configuration error). > > I concur. My initial impression is that JCasC lacks polish, and I was > surprised to see it promoted so heavily when issues like this remain. > > > This is also the approach that we are using if a plugin changes > serialization (or if a plugin cannot be started because of missing > dependencies): in this case Jenkins still continues to work and the > problems are highlighted in the UI. > > Core isn't entirely consistent in this regard, either. Yes > OldDataMonitor and PluginWrapperAdministrativeMonitor exist. But I > just tried corrupting core's config.xml file and Jenkins wouldn't > start at all. But when I corrupted Email Extension's > hudson.plugins.emailext.ExtendedEmailPublisher.xml, Jenkins started > but with the default values for Email Extension and no administrative > monitor in the UI. The latter clearly could use some improvement, but > I'm not sure about the former. It seems that we want _some_ > configuration loading errors to be fatal. But which ones, exactly? In > the JCasC issue on GitHub, Antonio raised the valid point that errors > in loading security-related configuration should be fatal (for obvious > reasons). > > -- > 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/CAFwNDjrLf3jJ-dTk%2BOX1E4b2%3DvB2rsWDFgMX0%2BzKNHMbcgRcJA%40mail.gmail.com > . > -- 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/CAH-3BidoM3VfGS%2B4hiMs5dncaVywyrVm7OMt%3DZN6Yj%2BCTDwCyA%40mail.gmail.com.
