You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Hadoop QA (JIRA)" <ji...@apache.org> on 2016/01/26 23:52:39 UTC

[jira] [Commented] (AMBARI-14804) Move Version Definition to its own endpoint

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

Hadoop QA commented on AMBARI-14804:
------------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12784494/AMBARI-14804.patch
  against trunk revision .

    {color:red}-1 patch{color}.  The patch command could not apply the patch.

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

This message is automatically generated.

> Move Version Definition to its own endpoint
> -------------------------------------------
>
>                 Key: AMBARI-14804
>                 URL: https://issues.apache.org/jira/browse/AMBARI-14804
>             Project: Ambari
>          Issue Type: Task
>          Components: ambari-server
>            Reporter: Nate Cole
>            Assignee: Nate Cole
>            Priority: Critical
>             Fix For: 2.4.0
>
>         Attachments: AMBARI-14804.patch
>
>
> The creation of a repository using a Version Definition file should have its own endpoint.  This is because using the Repository Version endpoint implies that the stack is known, whereas that information is in the Version Definition file



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