hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aaron T. Myers (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-7435) Make pre-commit checks run against the correct branch
Date Thu, 30 Jun 2011 17:32:28 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-7435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13057941#comment-13057941

Aaron T. Myers commented on HADOOP-7435:

I'm envisioning something like this:

# If there's only a single "fix version" set on the relevant JIRA, try to apply the patch/test
against that branch.
# If there's multiple "fix versions" set on the relevant JIRA, we could have a convention
for naming the patch to indicate which branch it should be tested against, e.g. "*-22.patch"
for 0.22.
# If there's no fix version set, default to testing the patch against trunk.

> Make pre-commit checks run against the correct branch
> -----------------------------------------------------
>                 Key: HADOOP-7435
>                 URL: https://issues.apache.org/jira/browse/HADOOP-7435
>             Project: Hadoop Common
>          Issue Type: Improvement
>          Components: test
>    Affects Versions: 0.23.0
>            Reporter: Aaron T. Myers
>             Fix For: 0.23.0
> The Hudson pre-commit tests are presently only capable of testing a patch against trunk.
It'd be nice if this could be extended to automatically run against the correct branch.

This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message