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

Slave workspaces deleted too often

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Critical Critical
    • core
    • None
    • Platform: All, OS: All

      I have a job running on a slave. Once the job runs I can see the workspace in
      hudson. If I wait overnight and check again in the morning the workspace is gone
      with this error:
      Error: no workspace

      1. The project was renamed recently and no build was done under the new name.
      2. The slave this project has run on for the last time was removed.
      3. The workspace directory (null) is removed outside Hudson.

      Run a build to have Hudson create a workspace.

      Turning on more logging, I see the following:
      May 4, 2009 6:44:01 AM hudson.model.WorkspaceCleanupThread
      FINE: Directory
      /nfshomes/hudson/.hudson/jobs/B3_Full_Regression/workspace is not owned
      by any project

      May 4, 2009 6:44:01 AM hudson.model.WorkspaceCleanupThread
      FINE: Directory
      /nfshomes/hudson/.hudson/jobs/B3_Short_Regression/workspace is not owned
      by any project

      May 4, 2009 6:44:01 AM hudson.model.WorkspaceCleanupThread
      FINE: Directory /nfshomes/hudson/.hudson/jobs/PET-linux/workspace is
      only 4 days 20 hr old, so not deleting

      May 4, 2009 6:43:48 AM hudson.model.WorkspaceCleanupThread
      FINE: Directory /hudson/workspace/B3_Full_Regression is not owned by any
      project

      All of these workspaces are owned by a project and should not be deleted.

            Unassigned Unassigned
            jpschewe jpschewe
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: