Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-26827

Unable to delete Summary Report XML Configuration file

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Resolved (View Workflow)
    • Priority: Major
    • Resolution: Not A Defect
    • Component/s: summary_report-plugin
    • Labels:
      None
    • Environment:
      Jenkins-CI 1.593, Windows Server 2008
    • Similar Issues:

      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.

        Attachments

          Activity

          Hide
          ioannis Ioannis Moutsatsos added a comment -

          As it turned out this was not an issue with the summary report plugin, but with a custom groovy build step that was creating, but not properly closing the xml configuration file. Once the file was closed properly, it could be deleted by the Workspace Cleanup plugin and the Workspace wipe action

          Show
          ioannis Ioannis Moutsatsos added a comment - As it turned out this was not an issue with the summary report plugin, but with a custom groovy build step that was creating, but not properly closing the xml configuration file. Once the file was closed properly, it could be deleted by the Workspace Cleanup plugin and the Workspace wipe action

            People

            • Assignee:
              Unassigned
              Reporter:
              ioannis Ioannis Moutsatsos
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: