www-builds mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Niklas Gustavsson <nik...@protocol7.com>
Subject Re: Conventions on long running Jenkins jobs
Date Mon, 23 May 2011 07:53:03 GMT
On Sun, May 22, 2011 at 8:29 PM, Grant Ingersoll <gsingers@apache.org> wrote:
> Do we have any convention/policy on how long a job can run before it's killed, so as
to play nice with others?  I've got some long running tests that I want to run once a week
on Saturday morning (early, US time).    For now they would be on the main build servers,
since Mahout doesn't have it's own jail/zone.

Not really. We do run a script to set time outs on all jobs every
other month or so. This script will use the estimated build time from
Jenkins times three.

How long time are we talking about here? For very long running jobs
(several hours) I would encourage you to look into getting a jail.

If the run time is a few hours: the Ubuntu and Solaris slaves are
pretty busy, so if you would be able to run the build on for example
the BSD slave instead, that would probably work better.


View raw message