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

Hadoop QA commented on AMBARI-8394:
-----------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12682629/AMBARI-8394.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 
ambari-admin.

Test results: 
https://builds.apache.org/job/Ambari-trunk-test-patch/704//testReport/
Console output: 
https://builds.apache.org/job/Ambari-trunk-test-patch/704//console

This message is automatically generated.

> Ambari View > Versions > Register Version (with mock data)
> ----------------------------------------------------------
>
>                 Key: AMBARI-8394
>                 URL: https://issues.apache.org/jira/browse/AMBARI-8394
>             Project: Ambari
>          Issue Type: New Feature
>          Components: ambari-web
>    Affects Versions: 2.0.0
>            Reporter: Andrii Tkach
>            Assignee: Andrii Tkach
>             Fix For: 2.0.0
>
>         Attachments: AMBARI-8394.patch
>
>
> * Create models and routes necessary for "Register Version" page.
> * Create any necessary mock data
> * Implement Register Version page
> * This is UI only without E2E integration



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

Reply via email to