[
https://issues.apache.org/jira/browse/AMBARI-12078?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14596497#comment-14596497
]
Hadoop QA commented on AMBARI-12078:
------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12741092/AMBARI-12078.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
contrib/views/files.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/3230//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/3230//console
This message is automatically generated.
> Add build number to view.xml for files view
> -------------------------------------------
>
> Key: AMBARI-12078
> URL: https://issues.apache.org/jira/browse/AMBARI-12078
> Project: Ambari
> Issue Type: Bug
> Components: ambari-views
> Affects Versions: 2.1.0
> Reporter: Erik Bergenholtz
> Assignee: Erik Bergenholtz
> Fix For: 2.1.0
>
> Attachments: AMBARI-12078.patch
>
>
> Just like the other views, files view should have build number it its
> view.xml to be be able to distinguish one build from another.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
