Details
-
Type:
Improvement
-
Status:
Resolved
-
Resolution: Fixed
-
Affects Version/s: None
-
Fix Version/s: 1.1-rc-1
Description
I'm seeing this on windows when the indexer is on.
It manifests as java.io.IOException: Unable to delete file/directory, and then a subsequent clean will succeed.
We could cater for this by noting that a particular operation failed, and then retrying it again at the end or after some time.
Activity
Pivotal Tracker Integration
made changes -
| Field | Original Value | New Value |
|---|---|---|
| Status | Open [ 1 ] | In Progress [ 3 ] |
Luke Daley
made changes -
| Fix Version/s | 1.1-rc-1 [ 10360 ] |
Adam Murdoch
made changes -
| Resolution | Fixed [ 1 ] | |
| Status | In Progress [ 3 ] | Resolved [ 5 ] |
Luke Daley
made changes -
| Summary | Cleaning should be more robust (e.g. to deal with OS indexers that quickly lock/unlock files) | Cleaning should be more robust on Windows |
Luke Daley
made changes -
| Assignee | Luke Daley [ ldaley ] |
Pivotal Tracker Integration
made changes -
| Status | Resolved [ 5 ] | Closed [ 6 ] |
Luke Daley
made changes -
| Workflow | jira with pivotal tracker [ 15595 ] | jira with pivotal tracker (no resolved, only closed) [ 17668 ] |
Luke Daley
made changes -
| Status | Closed [ 6 ] | Resolved [ 5 ] |
| Workflow | jira with pivotal tracker (no resolved, only closed) [ 17668 ] | Copy of jira with pivotal tracker (no closed, only resolved) [ 20303 ] |
Unable to get TeamCity builds: No active plugin license is found! Please visit http://stiltsoft.com/teamcity for details
If we develop this feature they will probably have to remember all undeletable dirs. So I'd vote to also improve the error message to include the list of all dirs that the build could not delete at clean. This would be very useful in windows.