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

Hadoop QA commented on AMBARI-18355:
------------------------------------

{color:green}+1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12828336/AMBARI-18355_v2.patch
  against trunk revision .

    {color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

    {color:green}+1 tests included{color}.  The patch appears to include 1 new 
or modified test files.

    {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-server.

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

This message is automatically generated.

> Introduce conditional dependencies in stack defition to handle blueprint 
> validation gracefully
> ----------------------------------------------------------------------------------------------
>
>                 Key: AMBARI-18355
>                 URL: https://issues.apache.org/jira/browse/AMBARI-18355
>             Project: Ambari
>          Issue Type: Improvement
>          Components: ambari-server
>    Affects Versions: trunk
>            Reporter: Amruta Borkar
>            Assignee: Amruta Borkar
>             Fix For: trunk
>
>         Attachments: AMBARI-18355.patch, AMBARI-18355_v1.patch, 
> AMBARI-18355_v2.patch, Adding Conditional Dependencies.pdf
>
>
> Currently stack definitions do not list conditional dependencies, adding 
> those to the stack definitions would make it easy to validate errors in case 
> of blueprint deployment. 



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

Reply via email to