On Mon, Sep 20, 2010 at 2:10 PM, Kristian Waagan <kristian.waa...@oracle.com> wrote: > Just want to point out that not all the jobs on the list have been running > regularly, so they haven't been using resources. > In any case, disabling jobs that haven't been run for a long time is > probably ok too. > One could consider removing "dead jobs", but I want to keep the Derby job a > little longer ;) > (is failing because Clover is/was unable to handle the data volume, but > hasn't been run for nine months)
Right, if the last build was successful, the job will not be disabled, even if the last build was older than one month. However, if your last job was unsuccessful and no one has fixed that for more than a month, I think disabling is probably appropriate. In your case, simply enable the job again when you fixed the problem with Clover. If you haven't used the job for nine months, unchecking a checkbox is probably not that much work when you're ready to run again :-) /niklas
