- 
    New Feature 
- 
    Resolution: Fixed
- 
    Major 
- 
    None
Hi everyone,
The new year is starting and we have a brand new mailing group for
hudson users.
The future of Hudson looks brilliant.
However there was a request for enhancement proposed last year by
Michael March, which seems to been left over despite the interest
shown by users: ability to have the 'builds' directories not be a
branch off the "jobs/job_name" hierarchy.
http://hudson.361315.n4.nabble.com/builds-directory-in-a-separate-location-td2994828.html
In the discussion there is a patch proposed to eventually set 2
additional variables besides HUDSON_HOME:
  HUDSON_WORKSPACES
  HUDSON_BUILDS
So that you can have a Hudson configuration like this:
  HUDSON_HOME=/stable_filesystem/hudson/
  HUDSON_WORKSPACES=/fast_ssd_filesystem/workspaces/
  HUDSON_BUILDS=/slow_sata_high_capacity_raid/builds/
Anyone could have a look at the patch proposed and provide some
feedback?
Thanks a lot,
Francois
- depends on
- 
                    JENKINS-21942 Unreliable defaulting of Jenkins.workspaceDir -         
- Open
 
-         
- 
                    JENKINS-17138 Deleting/renaming jobs using external builds directory does not move builds -         
- Resolved
 
-         
- 
                    JENKINS-17137 Bogus permalinks created when using external builds directory -         
- Resolved
 
-         
- is blocking
- 
                    JENKINS-48188 Broken Symlinks with External Build Record Root Directory and Maven Modules -         
- Open
 
-         
- is related to
- 
                    JENKINS-12251 Maven3 with 'builds' directory in a separate location tries to create folders with colons in the module name which is not allowed on windows. -         
- Resolved
 
-