Jenkins Plug-in - Post-build Step - with many config options

Question

I'm currently working on a Jenkins plug-in which is a post-build step (extends hudson.tasks.Builder). I make use of both global.jelly & config.jelly within the matching resources directory structure.

Up to now, for each field I've been using the following...

• @DataBoundConstructor with a parameter for each field in my config
• private final field for each field in my config
• Custom getter for each field in my config

I have lots of things to configure, I feel there must be some easier way, to do with the JSON it uses in the background, which I can traverse myself much more cleanly?

How is the data actually persisted, as my current understanding is that it uses the getter's populate the value and how it actually stores the values I'm not sure?

Answer 1

Unfortunately that is the only way I know of to configure your builder. Jenkins persists all your configurations in your job's config.xml file.