[jira] [Commented] (AMBARI-21715) Upgrade History Is too Verbose

2017-08-31 Thread Hadoop QA (JIRA) 

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

Hadoop QA commented on AMBARI-21715:


{color:green}+1 overall{color}.  Here are the results of testing the latest 
attachment 
  
http://issues.apache.org/jira/secure/attachment/12884691/AMBARI-21715_trunk.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 release audit{color}.  The applied patch does not increase 
the total number of release audit warnings.

{color:green}+1 javac{color}.  The applied patch does not increase the 
total number of javac compiler warnings.

{color:green}+1 core tests{color}.  The patch passed unit tests in 
ambari-web.

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

This message is automatically generated.

> Upgrade History Is too Verbose
> --
>
> Key: AMBARI-21715
> URL: https://issues.apache.org/jira/browse/AMBARI-21715
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.5.3
>Reporter: Antonenko Alexander
>Assignee: Antonenko Alexander
> Fix For: 2.5.3
>
> Attachments: AMBARI-21715.patch, AMBARI-21715_trunk.patch, 
> BUG-85441.gif, Screen Shot 2017-08-03 at 4.30.46 PM.png
>
>
> It looks like the Upgrade History page is displaying a row for every service 
> in a particular upgrade. I had thought we had mockups which kept the upgrade 
> history to a single row-per-upgrade and when you clicked on the that upgrade, 
> you were told more information about it (such as the to/from per-service).



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (AMBARI-21715) Upgrade History Is too Verbose

2017-08-17 Thread Hudson (JIRA) 

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

Hudson commented on AMBARI-21715:
-

FAILURE: Integrated in Jenkins build Ambari-branch-2.6 #24 (See 
[https://builds.apache.org/job/Ambari-branch-2.6/24/])
AMBARI-21715. Upgrade History Is too Verbose (alexantonenko) (hiveww: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=272e1ce18f66e4ed9b2546b77ad5c50a2bf8d743])
* (edit) ambari-web/app/messages.js
* (edit) ambari-web/app/templates/main/admin/stack_upgrade/upgrade_history.hbs
* (edit) 
ambari-web/test/views/main/admin/stack_upgrade/upgrade_history_view_test.js
* (edit) ambari-web/app/styles/stack_versions.less
* (edit) ambari-web/app/views/main/admin/stack_upgrade/upgrade_history_view.js


> Upgrade History Is too Verbose
> --
>
> Key: AMBARI-21715
> URL: https://issues.apache.org/jira/browse/AMBARI-21715
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.5.3
>Reporter: Antonenko Alexander
>Assignee: Antonenko Alexander
> Fix For: 2.5.3
>
> Attachments: AMBARI-21715.patch, BUG-85441.gif, Screen Shot 
> 2017-08-03 at 4.30.46 PM.png
>
>
> It looks like the Upgrade History page is displaying a row for every service 
> in a particular upgrade. I had thought we had mockups which kept the upgrade 
> history to a single row-per-upgrade and when you clicked on the that upgrade, 
> you were told more information about it (such as the to/from per-service).



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (AMBARI-21715) Upgrade History Is too Verbose

2017-08-14 Thread Antonenko Alexander (JIRA) 

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

Antonenko Alexander commented on AMBARI-21715:
--

PATCH APPLICATION FAILED
as it was applied against trunk.
manually tested.

> Upgrade History Is too Verbose
> --
>
> Key: AMBARI-21715
> URL: https://issues.apache.org/jira/browse/AMBARI-21715
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.5.3
>Reporter: Antonenko Alexander
>Assignee: Antonenko Alexander
> Fix For: 2.5.3
>
> Attachments: AMBARI-21715.patch, BUG-85441.gif, Screen Shot 
> 2017-08-03 at 4.30.46 PM.png
>
>
> It looks like the Upgrade History page is displaying a row for every service 
> in a particular upgrade. I had thought we had mockups which kept the upgrade 
> history to a single row-per-upgrade and when you clicked on the that upgrade, 
> you were told more information about it (such as the to/from per-service).



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (AMBARI-21715) Upgrade History Is too Verbose

2017-08-14 Thread Andrii Tkach (JIRA) 

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

Andrii Tkach commented on AMBARI-21715:
---

+1 for the patch

> Upgrade History Is too Verbose
> --
>
> Key: AMBARI-21715
> URL: https://issues.apache.org/jira/browse/AMBARI-21715
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.6.0
>Reporter: Antonenko Alexander
>Assignee: Antonenko Alexander
> Fix For: 2.6.0
>
> Attachments: AMBARI-21715.patch, BUG-85441.gif, Screen Shot 
> 2017-08-03 at 4.30.46 PM.png
>
>
> It looks like the Upgrade History page is displaying a row for every service 
> in a particular upgrade. I had thought we had mockups which kept the upgrade 
> history to a single row-per-upgrade and when you clicked on the that upgrade, 
> you were told more information about it (such as the to/from per-service).



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (AMBARI-21715) Upgrade History Is too Verbose

2017-08-14 Thread Hadoop QA (JIRA) 

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

Hadoop QA commented on AMBARI-21715:


{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12881719/AMBARI-21715.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/11986//console

This message is automatically generated.

> Upgrade History Is too Verbose
> --
>
> Key: AMBARI-21715
> URL: https://issues.apache.org/jira/browse/AMBARI-21715
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.6.0
>Reporter: Antonenko Alexander
>Assignee: Antonenko Alexander
> Fix For: 2.6.0
>
> Attachments: AMBARI-21715.patch, BUG-85441.gif, Screen Shot 
> 2017-08-03 at 4.30.46 PM.png
>
>
> It looks like the Upgrade History page is displaying a row for every service 
> in a particular upgrade. I had thought we had mockups which kept the upgrade 
> history to a single row-per-upgrade and when you clicked on the that upgrade, 
> you were told more information about it (such as the to/from per-service).



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)