On 20.09.10 12:38, Niklas Gustavsson wrote:
On Sun, Sep 19, 2010 at 10:22 AM, Niklas Gustavsson
<nik...@protocol7.com> wrote:
On Sun, Sep 19, 2010 at 1:49 AM, Gav...<ga...@16degrees.com.au> wrote:
If there are many projects like this using up resources that more attentive
projects could otherwise be using
then I think they should be removed after ONE WEEK of failing at the VERY
LATEST.
+1, I'll look into scripting this. Don't think we need to remove them,
but we should at least disable them.
Given a limit of one month, these are the jobs that would be disabled
(sorry for the formatting):
ActiveMQ-SysTest-5.3 | 6 mo 21 days
Ant-Build-Matrix | 1 mo 3 days
Ant_JDK_1.4_Test | 1 mo 1 day
AsyncWeb | 2 mo 28 days
buildr-ci-build-jruby-jdk5 | 1 mo 18 days
Camel | 1 mo 10 days
Cayenne-doc | 1 mo 17 days
clerezza-site | 3 mo 17 days
Derby-trunk_clover | 7 mo 24 days
Empire-DB multios | 1 mo 19 days
Felix-FileInstall | 1 mo 17 days
Felix-Gogo | 2 mo 7 days
Felix-WebConsole | 1 mo 19 days
Hadoop-20-Build | 2 yr 3 mo
Hadoop-Hdfs-21-Build | 5 mo 2 days
Hadoop-Hdfs-trunk | 5 mo 16 days
Hadoop-Mapreduce-21-Build | 3 mo 21 days
Hadoop-Mapreduce-trunk | 3 mo 21 days
Hadoop-Mapreduce-trunk-Commit | 5 mo 16 days
Hadoop-Patch-h1.grid.sp2.yahoo.net | 3 mo 17 days
Hadoop-Patch-h4.grid.sp2.yahoo.net | 3 mo 12 days
Hadoop-Patch-h9.grid.sp2.yahoo.net | 8 mo 8 days
Hama-Patch | 2 mo 24 days
Hama-Patch-Admin | 1 mo 6 days
Hdfs-Patch-h2.grid.sp2.yahoo.net | 5 mo 17 days
Hdfs-Patch-h5.grid.sp2.yahoo.net | 5 mo 17 days
Hive-trunk-h0.18 | 1 mo 6 days
Hive-trunk-h0.19 | 4 mo 16 days
Jackrabbit-1.6 | 1 mo 8 days
Jackrabbit-classloader | 3 mo 6 days
Jackrabbit-ocm | 3 mo 6 days
jspf-trunk | 1 mo 6 days
Mahout-Patch-Admin | 1 yr 11 mo
mailet-standard-trunk | 2 mo 0 days
Mapreduce-Patch-h3.grid.sp2.yahoo.net | 4 mo 23 days
Mapreduce-Patch-h4.grid.sp2.yahoo.net | 3 mo 25 days
Mapreduce-Patch-h6.grid.sp2.yahoo.net | 4 mo 12 days
Mapreduce-Patch-h9.grid.sp2.yahoo.net | 6 mo 20 days
MINA-1.0.X | 3 mo 10 days
MINA-1.1.X | 3 mo 10 days
Nutch-trunk | 2 mo 15 days
ODE-trunk-m2-jdk5-nightly-deploy | 1 mo 2 days
ODE-trunk-maven2-jdk5 | 1 mo 11 days
org.apache.kato.eclipse | 1 yr 2 mo
Pig-Patch-h7.grid.sp2.yahoo.net | 3 mo 13 days
Pig-Patch-h8.grid.sp2.yahoo.net | 4 mo 26 days
ServiceMix-Plugins | 2 mo 8 days
ServiceMix-Specs | 1 mo 2 days
ServiceMix-Utils | 2 mo 6 days
Shiro | 1 mo 9 days
sling-contrib-1.5 | 6 mo 14 days
struts-annotations | 1 yr 0 mo
tapestry-5.0-freestyle | 6 mo 7 days
TestBuilds | 1 yr 0 mo
Turbine Fulcrum | 3 mo 17 days
Tuscany-1x | 9 mo 2 days
Tuscany-2x | 1 mo 6 days
Tuscany-run-plugin | 3 mo 25 days
Zookeeper-Patch-h1.grid.sp2.yahoo.net | 2 mo 2 days
Zookeeper-Patch-h7.grid.sp2.yahoo.net | 1 mo 16 days
If your project is in that list, please fix it. I will run the script
to automatically disable those jobs failing for more than one month in
a few days. Now, should your job get disabled, you can simply enable
it again after fixing the build problems. No configuration or history
will be lost.
Hi,
I think it is a good idea to disable jobs that keep failing for a long
time, +1. Thanks, Niklas.
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)
--
Kristian
/niklas
