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

Hudson commented on AMBARI-12259:
---------------------------------

SUCCESS: Integrated in Ambari-branch-2.1 #165 (See 
[https://builds.apache.org/job/Ambari-branch-2.1/165/])
AMBARI-12259 - Configs: making strange recommendations + changes on upgrade 
(abaranchuk: 
http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=54df4ff580c242bad2afc6fa2418388cfaf9a471)
* 
ambari-server/src/main/java/org/apache/ambari/server/upgrade/UpgradeCatalog210.java
* 
ambari-server/src/test/java/org/apache/ambari/server/upgrade/UpgradeCatalog210Test.java
AMBARI-12259 - Configs: making strange recommendations + changes on 
upgrade(advisor changes) (abaranchuk: 
http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=89b0c0a4b24a6f4797e60e1a57d35b34a95327e7)
* 
ambari-server/src/main/java/org/apache/ambari/server/upgrade/UpgradeCatalog210.java
* ambari-server/src/main/resources/stacks/HDP/2.2/services/stack_advisor.py
AMBARI-12259 - Configs: making strange recommendations + changes on 
upgrade(tests) (abaranchuk: 
http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=ad0b1380604acca5eff3844edcd276e8af73190a)
* ambari-server/src/test/python/stacks/2.3/common/test_stack_advisor.py
* ambari-server/src/test/python/stacks/2.2/common/test_stack_advisor.py
* ambari-server/src/main/resources/stacks/HDP/2.2/services/stack_advisor.py


> Configs: making strange recommendations + changes on upgrade
> ------------------------------------------------------------
>
>                 Key: AMBARI-12259
>                 URL: https://issues.apache.org/jira/browse/AMBARI-12259
>             Project: Ambari
>          Issue Type: Task
>          Components: ambari-server
>    Affects Versions: 2.1.0
>            Reporter: Artem Baranchuk
>            Assignee: Artem Baranchuk
>             Fix For: 2.1.0
>
>




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

Reply via email to