Community
Participate
Working Groups
Currently Hudson is useless because it is shutting down (build views not available, I think). However, the jobs already executing include one (epp-package-build-helios #64) which looks set to run for another 8 hours (4 hours already). This means that hudson is blocked for further use for 8 hours. I think this is anti-social, and request that a policy be adopted for shutting down which involves killing long-running jobs after, say, an hour, so that everything can be restarted in a reasonable time. The jobs killed should be automatically restarted after restart -- I would hope this could be made automatic. If this shutdown policy could be built-in to hudson (as part of the shutdown request), then all would be well -- until then I request it be adopted by the admins.
I note that this situation has been rectified in this instance -- but we are still waiting for a shorter job! Anyhow, the enhancement request holds.
FWIW, I did kill epp-package-build-helios #64 for this case. But agree, in general, as policy, if something has more than an hour or two to finish, a forced shutdown wouldn't be too bad ... especially if its "owner" was not online to say "no, wait, I really need that one to finish for Eclipse critical need". Its hard to know about every case ... and we shouldn't even have to worry about shutdown and restart policies at all :) ... but I wouldn't object if someone wanted to kill my jobs, and I wasn't around to say if they were important, or not.
Closing this beacuse of inactivity and lack of need on new Hudson.
