Bug 458367 - HUDSON_BUILDS doesn't move existing builds
Summary: HUDSON_BUILDS doesn't move existing builds
Status: NEW
Alias: None
Product: Hudson
Classification: Technology
Component: Core (show other bugs)
Version: 3.2.1   Edit
Hardware: All All
: P3 major (vote)
Target Milestone: ---   Edit
Assignee: Bob Foster CLA
QA Contact: Geoff Waymark CLA
URL:
Whiteboard: candidate-4.0.0
Keywords:
Depends on:
Blocks:
 
Reported: 2015-01-25 17:03 EST by Bob Foster CLA
Modified: 2015-04-21 13:42 EDT (History)
5 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Bob Foster CLA 2015-01-25 17:03:41 EST 
When Hudson has been run for awhile, and is restarted with HUDSON_BUILDS specified, existing builds don't get copied to the specified builds directory.

It appears that existing builds are orphaned, because Hudson locates a builds directory either relative to the HUDSON_BUILDS dir or the job folder, but not both.
Comment 1 Bob Foster CLA 2015-01-25 17:04:49 EST 
I haven't checked the code but "orphaned" probably means disk usage doesn't get reported for pre-existing builds, either.