I'd benefit from the "Subversion: Credentials" feature described here. Can you provide me a link to a document describing the strategy used to add this type of functionality? If I knew where to start I'd be a lot more likely to implement a feature for the config slicer. I'm hoping that the document that you point me to describes whether the model to embed into the config slicing plugin's codebase information about every plugin's setting that it manipulates OR if you teach the other plugin to expose 'sliceable' config values to the config slicing plugin.

There's no specific documentation besides looking at the source code of the configuration slicing plugin itself.

I had originally hoped that other plugin makers might adopt slicing implementations within their plugins, but that seems unlikely given the complexity of stacked plugin dependencies. The alternative would be to move the slicing functionality into Jenkins core, so other plugin implementors would be more likely to see it. A number of other contributors have picked up work on the slicing plugin in the last few years. As I look at the UI of slices, it seems a little overwhelming right now. So I think taming the UI complexity of selecting a slice would be the next big step for this plugin.

Perhaps it could be moved closer to the configuration page for individual projects, instead of listing everything at once.