[
https://issues.apache.org/jira/browse/AMBARI-14837?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15124760#comment-15124760
]
Hadoop QA commented on AMBARI-14837:
------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12785316/AMBARI-14837.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/5125//console
This message is automatically generated.
> Versions: display all versions as tabs on left side, version details on
> selecting
> ---------------------------------------------------------------------------------
>
> Key: AMBARI-14837
> URL: https://issues.apache.org/jira/browse/AMBARI-14837
> Project: Ambari
> Issue Type: Task
> Components: ambari-web
> Affects Versions: 2.4.0
> Reporter: Xi Wang
> Assignee: Xi Wang
> Priority: Critical
> Fix For: 2.4.0
>
> Attachments: AMBARI-14837.patch, Screen Shot 2016-01-29 at 5.59.13
> PM.png, Screen Shot 2016-01-29 at 5.59.28 PM.png
>
>
> This one is to implement" Manage Ambari > Versions" page.
> 1. All versions show be displayed as tabs on the left side, each patch
> version should be a child of its parent stack version.
> 2. On selecting a version (either patch version or original stack version),
> all the version definition info show up on the right side.
> This look should be the same as register version page. "Details" and
> "Contents" are un-editable, "Repos" is editable and addable.
> 3. Add a mark/icon to the patch versions to differentiate them from original
> stack versions.
> Related API:
> {code}
> GET /api/v1/stacks/HDP/versions/2.3/repository_versions
> PUT /api/v1/stacks/HDP/versions/2.3/repository_versions // for editing repo
> urls
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
