Open ewelinawilkosz opened 6 years ago
Even from a technical point of view we prevented configuration to be applied using the check
method, this is indeed very disappointing for end-user, and might even let him feel like we just broke his installation. We need to offer something comparable to FormValidation
with relevant diagnostic message
I'll rename the issue then so it reflects the actual problem
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
It does help that we have reduced the stack trace down to everything that happens after export usually that resulted in very long stack traces inside stapler and jetty. Thanks to #836.
However, it could be better
HI,
i would like to work on this.
HI,
i would like to work on this.
Sure, ask any questions here and just send a PR
@timja would our validation that we add via https://github.com/jenkinsci/configuration-as-code-plugin/pull/1121 give us a shorter error message ?
@timja would our validation that we add via #1121 give us a shorter error message ?
Yes but we currently aren't validating before applying
I would expect with a yaml:
I'll get a warning from dryrun saying the file is not applicable - it's
systemMessage
, not a pluralsystemMessages
. Is this how dryrun should work? :)Instead I get this stacktrace:
cc @ndeloof