Mailing-List: contact common-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: common-issues@hadoop.apache.org
Date: Thu, 14 May 2015 22:18:13 +0000 (UTC)
From: "Chris Nauroth (JIRA)" <jira@apache.org>
To: common-issues@hadoop.apache.org
Message-ID: <JIRA.12749972.1414033744000.119839.1431641893298@Atlassian.JIRA>
In-Reply-To: <JIRA.12749972.1414033744000@Atlassian.JIRA>
References: <JIRA.12749972.1414033744000@Atlassian.JIRA>
 <JIRA.12749972.1414033744150@arcas>
Subject: [jira] [Commented] (HADOOP-11220) Jenkins should verify "mvn site"
 if the patch contains *.apt.vm changes
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Chris Nauroth commented on HADOOP-11220:
----------------------------------------

[~aw], I think we can close this issue now that the new test-patch.sh does this.  Do you agree?

> Jenkins should verify "mvn site" if the patch contains *.apt.vm changes
> -----------------------------------------------------------------------
>
>                 Key: HADOOP-11220
>                 URL: https://issues.apache.org/jira/browse/HADOOP-11220
>             Project: Hadoop Common
>          Issue Type: Improvement
>            Reporter: Zhijie Shen
>
> It's should be good to make Jenkins verify "mvn site" if the patch contains *.apt.vm changes to avoid some obvious build failure, such as YARN-2732.
> It's not the first time that the similar issues have been raised. Having an automative verification can inform us an alert before us encounter an actual build failure which involves "site" lifecycle.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)