Scenario:
A shared groovy lib which needs to be configured per Jenkins environment (like the URL to some server), but not per build project.

Currently a solution is to define an environment variabel for this. The drawback is that the env variabel is then available to everything in Jenkins. A much cleaner solution would be if it was possible to specify configuration just for this shared groovy lib. For example a key/value pair (configured for the library) which is then available as a variable in the groovy script.