On Thu, Jun 24, 2021 at 5:18 AM Ullrich Hafner <[email protected]> wrote:
> I often have this problem that my working JCasC configuration suddenly > breaks after an upgrade of JCasC (or another plugin) and Jenkins just not > starts up. And then you need to dig into log files to see what happens. It > would be much better if those errors would be reported in the UI > Maybe it depends on how you are using JCasC. If you treat your JCasC YAML plus a pinned set of versions of Jenkins core and plugins as an atomic configuration set describing your whole system, with a PR-type workflow, then failing fast is a feature not a bug: if either a change to YAML *or* a change to some component version causes a failure, then you can clearly see that this is a bad PR and it should not be merged until the issue is resolved. -- 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/CANfRfr0JbtH9JPz-sq8Enpd-kxXZbEoGQpHzf5giMX4%3D3%2B8TGw%40mail.gmail.com.
