Mailing-List: contact issues-help@ambari.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ambari.apache.org
Date: Wed, 22 Nov 2017 19:52:00 +0000 (UTC)
From: "Doroszlai, Attila (JIRA)" <jira@apache.org>
To: issues@ambari.apache.org
Message-ID: <JIRA.13120316.1511380318000.303302.1511380320313@Atlassian.JIRA>
In-Reply-To: <JIRA.13120316.1511380318000@Atlassian.JIRA>
References: <JIRA.13120316.1511380318000@Atlassian.JIRA> <JIRA.13120316.1511380318468@jira-lw-us.apache.org>
Subject: [jira] [Created] (AMBARI-22504) Replace test-patch.sh with Yetus
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Wed, 22 Nov 2017 19:52:05 -0000

Doroszlai, Attila created AMBARI-22504:
------------------------------------------

             Summary: 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


Most of Ambari 3.0 development is taking place in various feature branches, but {{test-patch.sh}} can 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.  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)