On Jul 10, 2009, at 4:37 AM, Justin Mason wrote:
On Thu, Jul 9, 2009 at 14:12, Justin Mason wrote:
On Thu, Jul 9, 2009 at 13:29, Jukka
Zitting wrote:
Hi,
On Thu, Jul 9, 2009 at 2:19 PM, Justin Mason wrote:
FWIW, my experience over the last few days of monitoring has been
that
our build ba
Hi,
On Fri, Jul 10, 2009 at 1:37 PM, Justin Mason wrote:
> Nigel's on holidays. I've gone ahead and done this anyway ;)
Excellent, thanks!
BR,
Jukka Zitting
On Thu, Jul 9, 2009 at 14:12, Justin Mason wrote:
> On Thu, Jul 9, 2009 at 13:29, Jukka Zitting wrote:
>> Hi,
>>
>> On Thu, Jul 9, 2009 at 2:19 PM, Justin Mason wrote:
>>> FWIW, my experience over the last few days of monitoring has been that
>>> our build backlogs on the Hudson machine are due to
On Thu, Jul 9, 2009 at 13:29, Jukka Zitting wrote:
> Hi,
>
> On Thu, Jul 9, 2009 at 2:19 PM, Justin Mason wrote:
>> 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; partic
Hi,
On Thu, Jul 9, 2009 at 2:19 PM, Justin Mason wrote:
> 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 projec
On Wed, Jul 8, 2009 at 21:43, Nigel Daley wrote:
> On Jul 8, 2009, at 4:24 AM, Jukka Zitting wrote
>> On Wed, Jul 8, 2009 at 12:50 PM, Justin Mason 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?
ok. I think this is now fixed; I've made it require a "bug[space]" prefix.
annoyingly it's a global setting, not per-project :(
--j.
On Wed, Jul 8, 2009 at 21:45, Nigel Daley wrote:
> Many thanks Justin!
>
> I think there's something funky with the Bugzilla Plugin config.
>
> Our Jira issues are
On Jul 8, 2009, at 4:24 AM, Jukka Zitting wrote:
Hi,
On Wed, Jul 8, 2009 at 12:50 PM, Justin Mason 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 long
Many thanks Justin!
I think there's something funky with the Bugzilla Plugin config.
Our Jira issues are being broken into 2 links now. Example,
MAPREDUCE-693 is broken into
1) MAPREDUCE- links to Jira issue
2) 693 links to bugzilla
Nige
On Jul 7, 2009, at 3:43 AM, Justin Mason wrote:
I'
Hi,
On Wed, Jul 8, 2009 at 12:50 PM, Justin Mason 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. wee
> We tried the build timeout before, I think, and it didn't help. But I
> think some of the timeouts we're seeing now are due to broken tests on
> some projects, and we've upgraded Hudson itself since the last try, so
> it's worth a retry in my opinion.
>
> I also checked the recent Hudson changel
I'm installing the following plugins:
- Audit Trail plugin ('Keep a log of who performed particular Hudson
operations, such as configuring jobs', handy in our configuration with
so many users)
- Bugzilla Plugin ('This plugin integrates Bugzilla into Hudson', we use
bugzilla in SpamAssassin
12 matches
Mail list logo
