I\'m trying to set up our build process in hudson.
Job 1 will be a super fast (hopefully) continuous integration build job that will be built frequently.
Job
I had the same issue, and what I ended up going with is separate projects for the long-running tasks. The first step in these projects was to copy all the files from the workspace of Job 1 (i.e. last build) to the Job 2/3/etc workspaces. This usually worked unless Job 1 was building at the time Job 2/3 started, since it would get an incomplete workspace. You could work around this by detecting "end of build" in Job 1 with a sentinel file, or use the Hudson locks plugin (I haven't tried).
You don't have to use a custom workspace if you make assumptions about the placement of the other jobs relative to %WORKSPACE%.