Community
Participate
Working Groups
This *may* be related to "3 deep" cascading job definitions. In our Eclipse Platform builds (where we run unit tests, we do not actually "build code") we have had a repeating problem where I will meticulously go through, and make sure all the configurations have the "Advanced Job Option" of "clean workspace before build" checked. But ... at some later point, they "lose" that check, and then do not clean workspace before build. Eventually this results in a "disk full" error (such as bug 478639). We are currently using Hudson: 3.2.2 (though, I've seen same problem, on earlier versions). We do have our definitions organized as "cascading jobs", so at top level, we have ep-unit (this is where we want to set "clean workspace") Then 3 platform specific ones ... it is these that seem to "lose" the inherited value. ep-unit-lin64 ep-unit-mac64 ep-unit-win32 And from there, we have "stream specific" jobs, such as below. It is these that do the "real work". (And, appear to lose their clean workspace flag, only because their parent does). ep46I-unit-lin64 ep46I-unit-mac64 ep46I-unit-win32 ep46N-unit-lin64 ep46N-unit-mac64 ep46N-unit-win32 You can see all these jobs in the view https://hudson.eclipse.org/shared/view/Eclipse%20and%20Equinox/
FWIW, I've found is is hard to "clean the workspace" myself. Not sure what's going on, exactly. Might be related to NFS? Might be related to Hudson reporting "done" (after a killed job) but some processes are still running? Documented more in bug 478639.
I experience the same problem in my installation after upgrading to 3.3.3. It is easy to reproduce this problem: 1. Create new free-style software job. Let's call it TestJob. In new job wizard check clean workspace before build and in my case also block build when upstream job is building (advanced options section). Save job. 2. Create second free-style software job - TestJobSub. Select TestJob as cascading job and save job. 3. At this point configuration looks good. TestJobSub inherits properties from TestJob but when you select to reload Hudson configuration form disk or restart Hudson configuration changes and properties are no longer inherited.
