It would be nice if Config File Provider temporary configuration files stuck around for the entire lifetime of a job execution, instead of being cleaned up before the post-build tasks. I just tried to use a maven settings file in a Sonar post-build action, but the temporary file was gone by that time. I confirmed it did exist during the build process (by cat-ting it in a regular build step).

I've worked around this by having the plugin put the file in an explicit location in the workspace for now, and using it from there.