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

Workspace folder not renamed/deleted when renaming job

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Open (View Workflow)
    • Priority: Minor
    • Resolution: Unresolved
    • Component/s: subversion-plugin
    • Labels:
      None
    • Environment:
      Jenkins LTS 1.532.2 with Svn plugin 2.2
      Windows Server 2008 SR2 with Oracle JDK 1.7.0_25
    • Similar Issues:

      Description

      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).

        Attachments

          Issue Links

            Activity

            Hide
            swatts 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.

            Show
            swatts 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.

              People

              • Assignee:
                Unassigned
                Reporter:
                ahammar Anders Hammar
              • Votes:
                14 Vote for this issue
                Watchers:
                16 Start watching this issue

                Dates

                • Created:
                  Updated: