It would be great if email-ext was compatible with Jenkins Configuration as Code.
This way the plugin could be configured at Jenkins startup with a single yaml file.
There is already a bunch of PRs filed on other plugins doing the same, for example how it was done for kubernetes plugin:
Basically the purpose is:
- Review CasC support, and implement it if not already in place.
- Review symbols and YAML format so that it's "nice". Example: avoid the unclassified group.
- Create automated tests to validate the support.