![]() |
|
|
|
|
Issue Type:
|
![Bug]() Bug
|
|
Assignee:
|
Unassigned |
|
Components:
|
summary_report-plugin |
|
Created:
|
06/Feb/15 11:29 AM
|
|
Description:
|
After a report is published there is a java process holding a handle to the report configuration file. Thus this file can't be cleaned up by Jenkins (either though the workspace wipe process, or the Workspace Cleanup plugin This has unpredictable and confusing results, as the next time a build fails, a report is still generated using the previous successful build configuration file.
Perhaps related to JENKINS-19994, but deletion always seems to fail specifically on the summary report configuration file.
|
|
Environment:
|
Jenkins-CI 1.593, Windows Server 2008
|
|
Project:
|
Jenkins
|
|
Priority:
|
![Major]() Major
|
|
Reporter:
|
Ioannis Moutsatsos
|
|
|
|
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
|
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit
https://groups.google.com/d/optout.
