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

Hadoop QA commented on AMBARI-21052:
------------------------------------

{color:green}+1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12868684/AMBARI-21052.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-admin.

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

This message is automatically generated.

> Regex pattern for version number in Register Version UI should depend on 
> stack's version dir
> --------------------------------------------------------------------------------------------
>
>                 Key: AMBARI-21052
>                 URL: https://issues.apache.org/jira/browse/AMBARI-21052
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-admin
>    Affects Versions: trunk
>            Reporter: Sangeeta Ravindran
>            Assignee: Sangeeta Ravindran
>             Fix For: trunk
>
>         Attachments: AMBARI-21052.patch
>
>
> My custom stack version dir has three digits. In the Register Version UI, the 
> regex pattern for Version Number forces me to enter two digits, although one 
> digit would make it a valid 4 digit stack version.
> The regex pattern should be based on the number of digits  supplied by the 
> stack's version dir and should not be harcoded.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Reply via email to