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

Workspace folder not renamed/deleted when renaming job

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Minor Minor
    • subversion-plugin
    • None
    • Jenkins LTS 1.532.2 with Svn plugin 2.2
      Windows Server 2008 SR2 with Oracle JDK 1.7.0_25

      When renaming a (Maven) job, the old workspace folder on disk is left unchanged. On the next build a new workspace folder (with the new job name) is created, leaving the old one as a leftover which has to be removed manually by logging onto the server.
      I think that the workspace folder should be renamed as well, or deleted (and then re-created on the next build).

          [JENKINS-22240] Workspace folder not renamed/deleted when renaming job

          Simon Watts added a comment -
          1. This issue is marked against the subversion-plugin – why is this related to the SCM?  It seems like a core issue.
          2. When we talk about job's workspace, can we confirm that this is on any agent and not just the master.
          3. Will any solution support agents which are off-line when a job is deleted/removed/renamed?

          For perspective - in our department we have many Jenkins masters and many more agents (the Jenkins master I use has close to 100 agents). It is highly impractical to go through manually cleaning workspaces - especially where the Multi-Branch plugin generates names which may not clearly identify the job associated with them.

          Simon Watts added a comment - This issue is marked against the subversion-plugin – why is this related to the SCM?  It seems like a core issue. When we talk about job's workspace, can we confirm that this is on any agent and not just the master. Will any solution support agents which are off-line when a job is deleted/removed/renamed? For perspective - in our department we have many Jenkins masters and many more agents (the Jenkins master I use has close to 100 agents). It is highly impractical to go through manually cleaning workspaces - especially where the Multi-Branch plugin generates names which may not clearly identify the job associated with them.

            Unassigned Unassigned
            ahammar Anders Hammar
            Votes:
            16 Vote for this issue
            Watchers:
            18 Start watching this issue

              Created:
              Updated: