hadoop-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Nigel Daley <nda...@mac.com>
Subject Re: triggering automated precommit testing
Date Fri, 14 Jan 2011 16:42:03 GMT
Ian, Todd, Cos, Konst, Jakob, Anyone else given this access:

PLEASE do NOT kill any builds from Hudson (little red x box) even if they appear hung.  Hudson
does not kill the underlying processes properly so they get left behind and can silently affect
subsequent jobs.  Instead, email this list that a job appears to be hung.  Giri or I can then
clean up the job properly. 

Thanks,
nige

On Jan 14, 2011, at 5:41 AM, Ian Holsman wrote:

> added.. (and Todd as well).
> 
> On Jan 13, 2011, at 3:21 PM, Suresh Srinivas wrote:
> 
>> Please add me...
>> 
>> 
>> On 1/12/11 5:18 PM, "Ian Holsman" <hadoop@holsman.net> wrote:
>> 
>> and done.
>> anybody else want access?
>> 
>> On Jan 12, 2011, at 8:12 PM, Nigel Daley wrote:
>> 
>>> I believe ommitters can gain access following this:
>>> http://wiki.apache.org/general/Hudson#How_do_I_get_an_account
>>> Ian would have to run a command on people.apache.org.
>>> 
>>> Nige
>>> 
>>> On Jan 12, 2011, at 4:41 PM, Konstantin Shvachko wrote:
>>> 
>>>> So, who has the permissions. I don't. Should I?
>>>> --Konstantin
>>>> 
>>>> On Wed, Jan 12, 2011 at 4:33 PM, Nigel Daley <ndaley@mac.com> wrote:
>>>> 
>>>>>> Jakob Homan commented on HDFS-884:
>>>>>> ----------------------------------
>>>>>> 
>>>>>>> Konstantin, if you're trying to kick a new patch build for this
you no
>>>>> longer move it to "Open" and back to "Patch Available". Instead, you
must
>>>>> upload a new patch. Or, if you have permission, you can kickhttps://
>>>>> hudson.apache.org/hudson/job/PreCommit-HDFS-Build/ and enter the issue
>>>>> number.
>>>>>> 
>>>>>> That makes me sad.  Is this a new feature or regression?
>>>>> 
>>>>> [For everyone's benefit, moving this to general@]
>>>>> 
>>>>> Jakob, I referenced the change here: http://tinyurl.com/4crxlvy
>>>>> The new system is much more robust partial because it no longer relies
on
>>>>> watching Jira generated emails to determined when issues move into Patch
>>>>> Available state. There is limited info I can get from the Jira API, thus
the
>>>>> triggering mechanism had to change.
>>>>> 
>>>>> Cheers,
>>>>> Nige
>>>>> 
>>> 
>> 
>> 
> 


Mime
View raw message