ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Doroszlai, Attila (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (AMBARI-22504) Replace test-patch.sh with Yetus
Date Thu, 23 Nov 2017 18:14:00 GMT

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

Doroszlai, Attila updated AMBARI-22504:
---------------------------------------
    Attachment: AMBARI-22504.branch-feature-AMBARI-14714-blueprintv2.002.patch

002: testing "private" feature branch

> Replace test-patch.sh with Yetus
> --------------------------------
>
>                 Key: AMBARI-22504
>                 URL: https://issues.apache.org/jira/browse/AMBARI-22504
>             Project: Ambari
>          Issue Type: Improvement
>            Reporter: Doroszlai, Attila
>            Assignee: Doroszlai, Attila
>             Fix For: 3.0.0
>
>         Attachments: AMBARI-22504.000.patch, AMBARI-22504.branch-2.6.patch, AMBARI-22504.branch-feature-AMBARI-14714-blueprintv2.002.patch
>
>
> Most of Ambari 3.0 development is taking place in various feature branches, but {{test-patch.sh}}
only tries patches on trunk.  This makes "Hadoop QA" largely useless for Ambari, since in
most cases the only feedback we get is that it could not apply the patch.
> {{test-patch.sh}} was originally copied from Hadoop.  The Hadoop version has evolved
and was extracted to [Apache Yetus|http://yetus.apache.org/].  Instead of adding configurable
branch support to the current script, we should replace it with one that utilizes Yetus. 
See for example [Hadoop|https://github.com/apache/hadoop/blob/trunk/dev-support/bin/test-patch],
[Hive|https://github.com/apache/hive/blob/master/dev-support/test-patch.sh] and [Ratis|https://github.com/apache/incubator-ratis/blob/master/dev-support/test-patch].



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message