[
https://issues.jenkins-ci.org/browse/JENKINS-12823?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
SCM/JIRA link daemon resolved JENKINS-12823.
--------------------------------------------
Resolution: Fixed
> Clean up temporary config files at the very end, not before post-build
> ----------------------------------------------------------------------
>
> Key: JENKINS-12823
> URL: https://issues.jenkins-ci.org/browse/JENKINS-12823
> Project: Jenkins
> Issue Type: New Feature
> Components: config-file-provider
> Reporter: oeuftete
> Assignee: domi
>
> 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.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
