On Fri, Sep 24, 2010 at 10:48 AM, Jukka Zitting <jukka.zitt...@gmail.com> wrote: > On Fri, Sep 24, 2010 at 10:37 AM, Niklas Gustavsson > <nik...@protocol7.com> wrote: >> Jackrabbit-1.6 | 1 mo 12 days >> Jackrabbit-classloader | 3 mo 10 days >> Jackrabbit-ocm | 3 mo 10 days > > These are builds that are configured to run only when there's a change > in the related codebase, so even if they've been red for a long time, > they don't really consume build resources. As soon as someone gets > around to fixing the pending errors, I expect the CI build to start up > again automatically to verify the fix. > > I suggest that we only disable *periodic* building of codebases that > have been failing for a long time.
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. /niklas
