[
https://issues.apache.org/jira/browse/AMBARI-15388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15292039#comment-15292039
]
Hadoop QA commented on AMBARI-15388:
------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12804960/AMBARI-15388.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 13 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:red}-1 core tests{color}. The patch failed these unit tests in
ambari-server:
org.apache.ambari.server.controller.internal.HostResourceProviderTest
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/6903//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/6903//console
This message is automatically generated.
> Custom services need a way to integrate in the upgrade process
> --------------------------------------------------------------
>
> Key: AMBARI-15388
> URL: https://issues.apache.org/jira/browse/AMBARI-15388
> Project: Ambari
> Issue Type: Improvement
> Components: ambari-server
> Affects Versions: trunk
> Reporter: Tim Thorpe
> Assignee: Tim Thorpe
> Fix For: trunk
>
> Attachments: AMBARI-15388 Design.pdf, AMBARI-15388.patch
>
> Original Estimate: 336h
> Remaining Estimate: 336h
>
> Currently the upgrade is defined as a series of xml files specific to the
> current stack version and the target stack version. Each upgrade xml defines
> the overall sequence of the upgrade and what needs to be done for each
> service. Custom services need to be able to specify their upgrade process
> and how those steps fit into the upgrade process.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)