Configuration-as-Code is the (proposed) mechanism to configure jenkins master automatically from plain text recipes. It relies on component internal model auto-discovery, and as such assume plugins do follow best practices for UI data-binding and internal design.
Using the export feature to generate a configuration yaml-file
it's partially supported, but significant configuration attributes don't follow expected design.
as a resume
- manual JSON parsing vs data-binding
- no setters for databound configuration elements
- optional block vs optional property
Part of the experienced Exception: