ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-18937) Allow generic Service Upgrade Packs for all targets
Date Fri, 18 Nov 2016 21:44:58 GMT

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

Hadoop QA commented on AMBARI-18937:
------------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12839617/AMBARI-18937.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 2 new or modified
test files.

    {color:red}-1 javac{color:red}.  The patch appears to cause the build to fail.

Console output: https://builds.apache.org/job/Ambari-trunk-test-patch/9328//console

This message is automatically generated.

> Allow generic Service Upgrade Packs for all targets
> ---------------------------------------------------
>
>                 Key: AMBARI-18937
>                 URL: https://issues.apache.org/jira/browse/AMBARI-18937
>             Project: Ambari
>          Issue Type: Task
>          Components: ambari-server
>            Reporter: Nate Cole
>            Assignee: Nate Cole
>            Priority: Critical
>             Fix For: 2.5.0
>
>         Attachments: AMBARI-18937.patch
>
>
> Currently, a custom service can participate in RU/EU only if it adds an Upgrade Pack
for every target of a stack.  If there is a case of the Upgrade Pack ALWAYS being the same
no matter the version, then only one file should be sufficient.



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

Mime
View raw message