ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-21831) Allow Hiding of PATCH Repository
Date Tue, 29 Aug 2017 09:40:00 GMT

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

Hadoop QA commented on AMBARI-21831:
------------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12884079/AMBARI-21831_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 3 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:red}-1 core tests{color}.  The test build failed in [ambari-web|https://builds.apache.org/job/Ambari-trunk-test-patch/12083//artifact/patch-work/testrun_ambari-web.txt]


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

This message is automatically generated.

> Allow Hiding of PATCH Repository
> --------------------------------
>
>                 Key: AMBARI-21831
>                 URL: https://issues.apache.org/jira/browse/AMBARI-21831
>             Project: Ambari
>          Issue Type: Task
>          Components: ambari-web
>    Affects Versions: 2.6.0
>            Reporter: Andrii Tkach
>            Assignee: Andrii Tkach
>            Priority: Critical
>             Fix For: 2.6.0
>
>         Attachments: AMBARI-21831.patch, AMBARI-21831_trunk.patch
>
>
> When patches are reverted and no longer desired, there should be a way to remove them
directly from the Stacks and Versions page. Removal of a repository should only be allowed
if:
> - The repository type is {{PATCH}} and is in the {{INSTALLED}} or {{INSTALL_FAILED}}
state
> - The repository is {{NOT_REQUIRED}} (not distributed) regardless of type
> In the dropdown of actions for the repository, we should add a "Discard" action which
does this by executing a {{PUT}} against the {{\{stackName\}/versions/\{stackVersion\}/repository_versions}}
endpoint.
> A new property will be exposed, {{RepositoryVersions/hidden}} which will be set to a
value of {{true}} by the web client. When the web client queries for compatible repositories,
any which expose {{RepositoryVersions/hidden}} as {{true}} should not be shown.



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

Mime
View raw message