Due to some maintenance issues, this service has been switched in read-only mode, you can find more information about the why

and how to migrate your plugin documentation in this blogpost

Skip to end of metadata
Go to start of metadata

Plugin Information

View Storable Configs on the plugin site for more information.

This plugin allows you to save and load set of job parameters.

Hudson 1.366 or later.

This plugin was created for Hudson 1.366. It might not work with earlier versions of Hudson.

User guide

This plugin saves and loads job parameters (Boolean value, String parameter, ScriptSelectionTaskDefinition and etc.).

1. Select job. In menu there is button "Storable configs". Press this button.

2. You should see the following page with empty configuration list.

3. For saving current job parameters you need to enter the filename and to press "Save settings" button. Plugin will save all job parameters in HUDSON_HOME\jobs\job_name\storable-configs\filename.xml . This file will appear in "Load configuration" section. You may view all available configuration files.

4. For loading parameters you need to choose one file from the list and to press "Change settings" button.

Changelog

Version 1.0 (February 28, 2011)
  • Initial release.

3 Comments

  1. Unknown User (maxime_lem)

    Hi,

    I'm getting this stack trace when I click on the "change settings button" for loading a config xml:javax.servlet.ServletException: java.lang.NoClassDefFoundError: hpi/ScriptSelectionTaskDefinition
    org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:603)
    ...
    root cause
    java.lang.NoClassDefFoundError: hpi/ScriptSelectionTaskDefinition
    hpi.StorableConfigsPlugin.doChangeSettings(StorableConfigsPlugin.java:188)

    As you can see, ScriptSelectionTaskDefinition plugin is not installed on my Jenkins instance, and I'd like to not have to.

    Another issue with this plugin is that saving a config file requires "configure" permission. I think it's a bad choice because these configs file do not actually change the configuration of the job, but just store parameters.
    IMO, build permission is enough.

    @+

  2. Unknown User (maxime_lem)

    I just fixed quickly these 2 problems, but the plugin is still not working. Loading saved parameters leave parameters fields empty and strip away html content in parameters description. The worst is that the job *configuration* is being saved like this. If I launch a new build, my parameters are still broken.

    So, as the plugin currently (not) works, the configure permission is indeed more suitable than the build permission...

  3. Unknown User (kishorerp)

    even i am observing the same issues mentioned above...the comments have not been updated since 2.5 years..which mentions..they may not be fixed as of now by the author