> 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

So, who has the permissions. I don't. Should I?
--Konstantin

On Wed, Jan 12, 2011 at 4:33 PM, Nigel Daley <[EMAIL PROTECTED]> 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
>

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 <[EMAIL PROTECTED]> 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
>>

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 <[EMAIL PROTECTED]> 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
>>>
>

yes, please.

On Wed, Jan 12, 2011 at 5:18 PM, Ian Holsman <[EMAIL PROTECTED]> 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 <[EMAIL PROTECTED]> 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
>>>>
>>
>
>

Me too, please.
--
  Take care,
Konstantin (Cos) Boudnik

On Wed, Jan 12, 2011 at 17:18, Ian Holsman <[EMAIL PROTECTED]> 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 <[EMAIL PROTECTED]> 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
>>>>
>>
>
>

done.. (for both cos & jghoman).

regards
Ian
On Jan 12, 2011, at 9:29 PM, Konstantin Boudnik wrote:

> Me too, please.
> --
>   Take care,
> Konstantin (Cos) Boudnik
>
>
>
> On Wed, Jan 12, 2011 at 17:18, Ian Holsman <[EMAIL PROTECTED]> 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 <[EMAIL PROTECTED]> 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
>>>>>
>>>
>>
>>

Please add me...
On 1/12/11 5:18 PM, "Ian Holsman" <[EMAIL PROTECTED]> 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 <[EMAIL PROTECTED]> 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
>>>
>

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" <[EMAIL PROTECTED]> 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 <[EMAIL PROTECTED]> 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
>>>>
>>
>
>

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" <[EMAIL PROTECTED]> 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 <[EMAIL PROTECTED]> 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
>>>>>
>>>
>>
>>
>

Hi Ian,

Could you add me to the  hudson-jobadmin group?  It seems that Hudson sometimes
does not run automatically.

Nicholas Sze

________________________________
From: Nigel Daley <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Sent: Wed, January 12, 2011 5:12:57 PM
Subject: Re: triggering automated precommit testing

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

done.
give it a shot and let me know how it goes.

On Mar 15, 2011, at 8:09 AM, Tsz Wo (Nicholas), Sze wrote:

> Hi Ian,
>
> Could you add me to the  hudson-jobadmin group?  It seems that Hudson sometimes
> does not run automatically.
>
> Nicholas Sze
>
>
>
>
>
> ________________________________
> From: Nigel Daley <[EMAIL PROTECTED]>
> To: [EMAIL PROTECTED]
> Sent: Wed, January 12, 2011 5:12:57 PM
> Subject: Re: triggering automated precommit testing
>
> 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

Hi Ian,
Thanks for the fast response!  It works. I just have started a build.
Nicholas
________________________________
From: Ian Holsman <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Sent: Mon, March 14, 2011 3:11:07 PM
Subject: Re: triggering automated precommit testing

done.
give it a shot and let me know how it goes.

On Mar 15, 2011, at 8:09 AM, Tsz Wo (Nicholas), Sze wrote:

> Hi Ian,
>
> Could you add me to the  hudson-jobadmin group?  It seems that Hudson sometimes
>
> does not run automatically.
>
> Nicholas Sze
>
>
>
>
>
> ________________________________
> From: Nigel Daley <[EMAIL PROTECTED]>
> To: [EMAIL PROTECTED]
> Sent: Wed, January 12, 2011 5:12:57 PM
> Subject: Re: triggering automated precommit testing
>
> 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

Nicholas, what do u mean it doesn't always start automatically?

Cheers,
Nige

Sent from my iPhone4

On Mar 14, 2011, at 2:09 PM, "Tsz Wo (Nicholas), Sze" <[EMAIL PROTECTED]> wrote:

> Hi Ian,
>
> Could you add me to the  hudson-jobadmin group?  It seems that Hudson sometimes
> does not run automatically.
>
> Nicholas Sze
>
>
>
>
>
> ________________________________
> From: Nigel Daley <[EMAIL PROTECTED]>
> To: [EMAIL PROTECTED]
> Sent: Wed, January 12, 2011 5:12:57 PM
> Subject: Re: triggering automated precommit testing
>
> 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

Hey Nigel,

Would there be any way to add a feature where we can make some special
comment on the JIRA that would trigger a hudson retest? There are a lot of
really old patches out on the JIRA that would be worth re-testing against
trunk, and it's a pain to download and re-attach.

I'm thinking a comment with a special token like "@Hudson.Test"

Failing that, Ian, can you add me to the Hudson list?

-Todd

On Wed, Jan 12, 2011 at 4:33 PM, Nigel Daley <[EMAIL PROTECTED]> 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
>

--
Todd Lipcon
Software Engineer, Cloudera

Todd, please file a Jira in Common against test component.  FWIW, I fear the precommit integration with Jira will need some amount of work as Apache moves to Jira 4.2 in the coming weeks.

Nige

On Jan 14, 2011, at 12:57 AM, Todd Lipcon wrote:

> Hey Nigel,
>
> Would there be any way to add a feature where we can make some special
> comment on the JIRA that would trigger a hudson retest? There are a lot of
> really old patches out on the JIRA that would be worth re-testing against
> trunk, and it's a pain to download and re-attach.
>
> I'm thinking a comment with a special token like "@Hudson.Test"
>
> Failing that, Ian, can you add me to the Hudson list?
>
> -Todd
>
> On Wed, Jan 12, 2011 at 4:33 PM, Nigel Daley <[EMAIL PROTECTED]> 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
>>
>
>
>
> --
> Todd Lipcon
> Software Engineer, Cloudera

It may not be as simple as triggering retest, as Some of the patches could be old and may not apply.
On 1/14/11 8:44 AM, "Nigel Daley" <[EMAIL PROTECTED]> wrote:

Todd, please file a Jira in Common against test component.  FWIW, I fear the precommit integration with Jira will need some amount of work as Apache moves to Jira 4.2 in the coming weeks.

Nige

On Jan 14, 2011, at 12:57 AM, Todd Lipcon wrote:

> Hey Nigel,
>
> Would there be any way to add a feature where we can make some special
> comment on the JIRA that would trigger a hudson retest? There are a lot of
> really old patches out on the JIRA that would be worth re-testing against
> trunk, and it's a pain to download and re-attach.
>
> I'm thinking a comment with a special token like "@Hudson.Test"
>
> Failing that, Ian, can you add me to the Hudson list?
>
> -Todd
>
> On Wed, Jan 12, 2011 at 4:33 PM, Nigel Daley <[EMAIL PROTECTED]> 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
>>
>
>
>
> --
> Todd Lipcon
> Software Engineer, Cloudera

Suresh, FWIW the precommit build fails fast in such cases (by design).

nige

On Jan 14, 2011, at 10:12 AM, Suresh Srinivas wrote:

> It may not be as simple as triggering retest, as Some of the patches could be old and may not apply.
>
>
> On 1/14/11 8:44 AM, "Nigel Daley" <[EMAIL PROTECTED]> wrote:
>
> Todd, please file a Jira in Common against test component.  FWIW, I fear the precommit integration with Jira will need some amount of work as Apache moves to Jira 4.2 in the coming weeks.
>
> Nige
>
> On Jan 14, 2011, at 12:57 AM, Todd Lipcon wrote:
>
>> Hey Nigel,
>>
>> Would there be any way to add a feature where we can make some special
>> comment on the JIRA that would trigger a hudson retest? There are a lot of
>> really old patches out on the JIRA that would be worth re-testing against
>> trunk, and it's a pain to download and re-attach.
>>
>> I'm thinking a comment with a special token like "@Hudson.Test"
>>
>> Failing that, Ian, can you add me to the Hudson list?
>>
>> -Todd
>>
>> On Wed, Jan 12, 2011 at 4:33 PM, Nigel Daley <[EMAIL PROTECTED]> 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
>>>
>>
>>
>>
>> --
>> Todd Lipcon
>> Software Engineer, Cloudera
>
>