ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-19039) In stack version, build number should not be mandatory
Date Mon, 05 Dec 2016 21:54:59 GMT

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

Hudson commented on AMBARI-19039:
---------------------------------

FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #6159 (See [https://builds.apache.org/job/Ambari-trunk-Commit/6159/])
AMBARI-19039: In stack version, build number should not be mandatory (dili: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=b5122e258bfe5a2e56511eb9dd29a70cf1260a9c])
* (edit) ambari-common/src/main/python/resource_management/libraries/functions/copy_tarball.py
* (edit) ambari-common/src/main/python/resource_management/libraries/functions/dynamic_variable_interpretation.py


> In stack version, build number should not be mandatory
> ------------------------------------------------------
>
>                 Key: AMBARI-19039
>                 URL: https://issues.apache.org/jira/browse/AMBARI-19039
>             Project: Ambari
>          Issue Type: Bug
>    Affects Versions: trunk
>            Reporter: Amruta Borkar
>            Assignee: Amruta Borkar
>             Fix For: trunk, 2.5.0
>
>         Attachments: AMBARI-19039.patch, AMBARI-19039_v1.patch, AMBARI-19039_v1.patch
>
>
> In stack version, build number should not be mandatory.  mapreduce.tar.gz file does not
get copied during blueprint deployment when stack version does not have build version.



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

Mime
View raw message