Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 85B49200CDF for ; Thu, 17 Aug 2017 21:41:09 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 842E916BA3D; Thu, 17 Aug 2017 19:41:09 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 3D59816BA3F for ; Thu, 17 Aug 2017 21:41:08 +0200 (CEST) Received: (qmail 59556 invoked by uid 500); 17 Aug 2017 19:41:07 -0000 Mailing-List: contact issues-help@ambari.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@ambari.apache.org Delivered-To: mailing list issues@ambari.apache.org Received: (qmail 59164 invoked by uid 99); 17 Aug 2017 19:41:06 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 17 Aug 2017 19:41:06 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id BA19D180815 for ; Thu, 17 Aug 2017 19:41:05 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -100.002 X-Spam-Level: X-Spam-Status: No, score=-100.002 tagged_above=-999 required=6.31 tests=[RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id WbAzBfQ7jxFa for ; Thu, 17 Aug 2017 19:41:05 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id 7239162445 for ; Thu, 17 Aug 2017 19:41:03 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 32204E0ED3 for ; Thu, 17 Aug 2017 19:41:02 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 24B86253A2 for ; Thu, 17 Aug 2017 19:41:01 +0000 (UTC) Date: Thu, 17 Aug 2017 19:41:01 +0000 (UTC) From: "Hudson (JIRA)" To: issues@ambari.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (AMBARI-21725) Web Client Doesn't Display MAINT Repos Correctly MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Thu, 17 Aug 2017 19:41:09 -0000 [ https://issues.apache.org/jira/browse/AMBARI-21725?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16131184#comment-16131184 ] Hudson commented on AMBARI-21725: --------------------------------- FAILURE: Integrated in Jenkins build Ambari-branch-2.6 #24 (See [https://builds.apache.org/job/Ambari-branch-2.6/24/]) AMBARI-21725. Web Client Doesn't Display MAINT Repos Correctly (hiveww: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=086e368a98dac1a40f5cd6d9da2d8456089d9d22]) * (edit) ambari-admin/src/main/resources/ui/admin-web/app/scripts/controllers/stackVersions/StackVersionsCreateCtrl.js * (edit) ambari-web/app/models/stack_version/repository_version.js * (edit) ambari-admin/src/main/resources/ui/admin-web/app/views/stackVersions/stackVersionPage.html * (edit) ambari-web/app/views/main/admin/stack_upgrade/upgrade_version_box_view.js * (edit) ambari-admin/src/main/resources/ui/admin-web/app/scripts/services/Stack.js * (edit) ambari-admin/src/main/resources/ui/admin-web/app/scripts/i18n.config.js * (edit) ambari-web/app/views/main/admin/stack_upgrade/versions_view.js * (edit) ambari-web/app/messages.js * (edit) ambari-web/test/views/main/admin/stack_upgrade/version_view_test.js * (edit) ambari-admin/src/main/resources/ui/admin-web/app/views/stackVersions/list.html * (edit) ambari-web/app/templates/main/admin/stack_upgrade/upgrade_version_column.hbs * (edit) ambari-web/app/controllers/main/admin/stack_and_upgrade_controller.js * (edit) ambari-admin/src/main/resources/ui/admin-web/app/scripts/controllers/stackVersions/StackVersionsEditCtrl.js * (edit) ambari-web/test/controllers/main/admin/stack_and_upgrade_controller_test.js * (edit) ambari-web/app/templates/main/admin/stack_upgrade/upgrade_version_box.hbs * (edit) ambari-web/app/templates/common/modal_popups/install_repo_confirmation.hbs > Web Client Doesn't Display MAINT Repos Correctly > ------------------------------------------------ > > Key: AMBARI-21725 > URL: https://issues.apache.org/jira/browse/AMBARI-21725 > Project: Ambari > Issue Type: Bug > Components: ambari-web > Affects Versions: 2.5.3 > Reporter: Antonenko Alexander > Fix For: 2.5.3 > > Attachments: AMBARI-21725.patch > > > The web client currently doesn't understand {{MAINT}} repositories. When you register one it doesn't show the repo differently or identify it as a {{MAINT}} repo. > After applying an upgrade which is a {{MAINT}} upgrade, the upgrade history also should indicate that it was a {{MAINT}} style. > {{MAINT}} is a peer to {{PATCH}} upgrades, so anywhere we have special display/text for patches, we should also have the same for maintenance repos/upgrades. -- This message was sent by Atlassian JIRA (v6.4.14#64029)