hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nigel Daley (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (HADOOP-2602) Patch process should determine issue number differently
Date Mon, 28 Jan 2008 04:07:34 GMT

     [ https://issues.apache.org/jira/browse/HADOOP-2602?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Nigel Daley resolved HADOOP-2602.
---------------------------------

       Resolution: Fixed
    Fix Version/s: hudson
         Assignee: Nigel Daley

This was fixed in hudson scripts when we moved to the new build server.

> Patch process should determine issue number differently
> -------------------------------------------------------
>
>                 Key: HADOOP-2602
>                 URL: https://issues.apache.org/jira/browse/HADOOP-2602
>             Project: Hadoop Core
>          Issue Type: Improvement
>          Components: build
>            Reporter: Nigel Daley
>            Assignee: Nigel Daley
>            Priority: Minor
>             Fix For: hudson
>
>
> When an email comes in, the processHadoopPatchEmail.sh script (http://svn.apache.org/viewvc/lucene/hadoop/nightly/processHadoopPatchEmail.sh?view=markup)
determines the issue number based on the first occurance of "HADOOP-#*".  This picks the wrong
issue number when there is a different issue number in the synopsis of the issue (such as
HADOOP-2570).  Instead, the script should look for "Key: HADOOP-#*"

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message