Hi, On Fri, Sep 24, 2010 at 11:05 AM, Niklas Gustavsson <nik...@protocol7.com> wrote: > These three builds are set to be checking for updates on a periodic > basis (polling the SCM every hour) and when upstream dependencies are > built.
That shouldn't be too much of a burden, or is it? It doesn't tie up executors like some of the other failing builds. I'm all for disabling builds that continuously keep failing, but in these cases only the last build has failed, and I totally expect the builds to go blue again as soon as someone gets around to touching the codebases. Instead of the time limit, would it make more sense to only disable those jobs where >n of the last builds have failed? BR, Jukka Zitting
