After all these years, we finally migrated from Groovy initialization scripts to JCasC on our Jenkins controllers.
While any configuration error is a problem, I noticed that the way these errors are reported differs from one mechanism to the next. With Groovy initialization scripts, errors in one initialization script are logged but this does not prevent subsequent initialization scripts from running and startup from completing. In contrast, an error in a JCasC configuation file causes subsequent changes not to be applied and halts Jenkins startup. Do others view this lack of consistency as a problem? If so, would we want to resolve the inconsistency by making JCasC more lenient or by making Groovy initialization scripts more draconian? I could see arguments both ways: making things more draconian is likely to break things for someone out there, while making things more lenient is likely to hide legitimate errors and decrease operability. I could also see an argument for maintaining the status quo if people are happy with it. If there is a consensus about this I could look into implementing the change. -- 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/CAFwNDjqih7TVJi8rvkcPbXgn-jzrdRTo%2B8EBuv8y_jQoZJipOA%40mail.gmail.com.
