> Am 18.03.2015 um 06:24 schrieb Christopher Orr <[email protected]>: > > You can always create a job config programmatically, write config.xml > directly to disk, or upload config via the CLI. > > So basically there's no way of preventing bad config from being entered — > plugins should make a reasonable effort at runtime to sanity check the config.
This is a different thing. A plug-in should always check the input data on the application layer. But additionally, the UI layer should never allow the creation of invalid configurations. This is one of the main reasons that there is an UI layer. > > -Chris > > > On 17/03/15 21:55, Baptiste Mathus wrote: >> +1. >> >> Btw, maybe this is something to add as input for the work going on on >> the UX and the way plugin UI is developed? >> >> Le 17 mars 2015 23:36, "Ulli Hafner" <[email protected] >> <mailto:[email protected]>> a écrit : >> >> I don’t think that this is possible. >> >>> Am 17.03.2015 um 16:48 schrieb Kirill <[email protected] >>> <mailto:[email protected]>>: >>> >>> Hi folks, >>> >>> I added few mandatory fields to my build step's config.jelly with >>> the validation that ensures validation errors appearance if >>> mandatory fields are empty. >>> Is there a way to prohibit saving the job if it's configuration >>> contains validation errors? >>> >>> Regards, >>> Kirill. > > -- > 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/55090C25.10807%40orr.me.uk. > 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/B01E8C6A-A51A-4644-BEB6-73D5D939205F%40gmail.com. For more options, visit https://groups.google.com/d/optout.
signature.asc
Description: Message signed with OpenPGP using GPGMail
