www-builds mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Justin Mason ...@jmason.org>
Subject Re: Hudson administrivia, build timeout
Date Thu, 09 Jul 2009 12:19:03 GMT
On Wed, Jul 8, 2009 at 21:43, Nigel Daley<ndaley@yahoo-inc.com> wrote:
> On Jul 8, 2009, at 4:24 AM, Jukka Zitting wrote
>> On Wed, Jul 8, 2009 at 12:50 PM, Justin Mason<jm@jmason.org> wrote:
>>>
>>> Should we set policy for the ASF hudson instance regarding the max
>>> runtime of builds, seeing as we only have 4 build executor slots?
>>
>> That would be good, though we may want to allow longer builds that
>> only run relatively seldom (e.g. weekly).
>
> +1.  There may need to be exceptions to this.  If I recall, the Harmony
> builds take a long time.

+1

OK, I suggest we set a relaxed policy of a 2-hour built timeout for
most projects.

If you see a project causing a backlog due to a longer build duration,
then feel free to log in and click through into its Configuration
page, where the build timeout can be set to 120 minutes. (and stop the
build, of course, using the [x].)

If the project indicates in its name, description, or build schedule
that it's a long-running, infrequent (e.g. weekly) build, then we can
relax that 2-hour limit and maybe allow it to run for longer, 4
hours/240 mins maybe?  Play it by ear, anyway. ;)

FWIW, my experience over the last few days of monitoring has been that
our build backlogs on the Hudson machine are due to contention for the
limited number of executors; particularly the 2 on the main instance.
There are a few projects that perform 1.5-hour deployments from this.
IMO we need to come up with a way to accomodate this.

I haven't observed any "hung" builds that the build timeout didn't
deal with, btw.

--j.

Mime
View raw message