[JIRA] (JENKINS-15495) Workspace got deleted for custom workspaces after updating to 1.485

Klaus Scharpf created JENKINS-15495

Workspace got deleted for custom workspaces after updating to 1.485

Issue Type:	Bug
Affects Versions:	current
Assignee:	Unassigned
Components:	core
Created:	11/Oct/12 8:39 PM
Description:	After updating to 1.485 some of my builds broke. When checking the workspace they were all deleted. I found out that workspaces on slaves are deleted after 30 days of inactivity. But I don't have any slaves, and these workspaces are never updated, since they only contain some ANT scripts, or plain batch, that only copies files outside of Jenkins. My last version before this update was 1.481, I am running these scripts for over a year, and nothing like this ever happened.
Environment:	Windows 7. Jenkins runs via its own server, no master-slave setup, i.e. only running by itself
Project:	Jenkins
Priority:	Critical
Reporter:	Klaus Scharpf

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

Jesse Glick updated JENKINS-15495

Workspace got deleted for custom workspaces after updating to 1.485

Assuming reproducible, not a critical bug; workspaces are designed to be disposable, i.e. they can be freely recreated at the expense of a longer build.
Change By:	Jesse Glick (15/Oct/12 6:59 PM)
Priority:	Critical Major

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

Klaus Scharpf commented on JENKINS-15495

Workspace got deleted for custom workspaces after updating to 1.485

The problem is that these workspaces were not in version control, since they only contain some scripts that never change. From time to time I back them up - and normally our company always does backups - but it still deleted some valuable items. I think this is still a serious issue since Jenkins allows workspaces without version control association, and therefore they will not be automatically re-created. Also, I have custom workspaces pointing into directories of my current development environment to run some scripts easily. Deleting them would delete ongoing development work. And yes, sometimes a specific branch might be dormant for a while...

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

Jesse Glick commented on JENKINS-15495

Workspace got deleted for custom workspaces after updating to 1.485

Never put original scripts directly in the workspace. Rather, version the scripts somewhere, either as part of some VCS-controlled project or inlined in the job configuration (which you should back up), and copy them to the workspace as a build step.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira