You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@zookeeper.apache.org by Mahadev Konar <ma...@yahoo-inc.com> on 2011/01/13 02:46:51 UTC
FW: triggering automated precommit testing
Please note this change.
------ Forwarded Message
From: Nigel Daley
Date: Wed, 12 Jan 2011 17:44:34 -0800
To: Mahadev Konar
Subject: Re: triggering automated precommit testing
yup.
On Jan 12, 2011, at 5:44 PM, Mahadev Konar wrote:
> Nigel,
> Is this true with zookeeper builds as well?
>
> Thanks
> mahadev
>
>
> On 1/12/11 4:33 PM, "Nigel Daley" <nd...@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
>>
>
------ End of Forwarded Message