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

Cleaning workspace no longer deletes Maven repository

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Component/s: perforce-plugin
    • Labels:
      None
    • Environment:
      Windows XP 64-bit, Hudson 1.386, Maven2 plugin 1.386, perforce plugin 1.1.12
    • Similar Issues:

      Description

      The perforce plugin has a checkbox "Clean Workspace Before Each Build" to delete the workspace for a project. The maven2 plugin has an to "Use private Maven repository" which stores the maven2 .repository directory under the workspace.

      Previously, checking the Clean Workspace option deleted everything in the workspace, including the .repository, which is useful to verify that transient maven dependencies are still available. An update to Hudson has altered the behavior so that Clean Workspace leaves the .repository directory in place. This appears related to the fix for http://issues.jenkins-ci.org/browse/JENKINS-7182. The fix should have included an option to specify whether cleaning the workspace includes cleaning the private maven repository.

        Attachments

          Activity

            People

            • Assignee:
              rpetti Rob Petti
              Reporter:
              dwalling dwalling
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: