hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Elek, Marton (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-16092) Move the source of hadoop/ozone containers to the same repository
Date Tue, 14 May 2019 09:16:00 GMT

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

Elek, Marton commented on HADOOP-16092:
---------------------------------------

I am confused a little as this issue is suggested by you originally but If I understood well
you don't like it any more.

bq. Any concerns [~elek]?

Thank you very much your question [~eyang]. Yes, I have concerns and wrote down the concerns
on  the mailing list 

https://mail-archives.apache.org/mod_mbox/hadoop-hdfs-dev/201903.mbox/%3CF26192BF-45F3-4A64-9758-F4BD3EA6FDB4%40hortonworks.com%3E

and I mentioned multiple times at HDDS-1495 and HDDS-1458.

If they are not clear I am happy to repeat them again and I will try to make it more clear
but I prefer to continue the discussion there to make it easier to follow.

> Move the source of hadoop/ozone containers to the same repository
> -----------------------------------------------------------------
>
>                 Key: HADOOP-16092
>                 URL: https://issues.apache.org/jira/browse/HADOOP-16092
>             Project: Hadoop Common
>          Issue Type: Improvement
>            Reporter: Elek, Marton
>            Assignee: Gabor Bota
>            Priority: Major
>
> This is proposed by [~eyang] in [this|https://lists.apache.org/thread.html/33ac54bdeacb4beb023ebd452464603aaffa095bd104cb43c22f484e@%3Chdfs-dev.hadoop.apache.org%3E]
mailing thread.
> bq. Hadoop community can decide what is best for Hadoop.  My preference is to remove
ozone from source tree naming, if Ozone is intended to be subproject of Hadoop for long period
of time.  This enables Hadoop community to host docker images for various subproject without
having to check out several source tree to trigger a grand build
> As of now the source of  hadoop docker images are stored in the hadoop git repository
(docker-* branches) for hadoop and in hadoop-docker-ozone git repository for ozone (all branches).
> As it's discussed in HDDS-851 the biggest challenge to solve here is the mapping between
git branches and dockerhub tags. It's not possible to use the captured part of a github branch.
> For example it's not possible to define a rule to build all the ozone-(.*) branches and
use a tag $1 for it. Without this support we need to create a new mapping for all the releases
manually (with the help of the INFRA).
> Note: HADOOP-16091 can solve this problem as it doesn't require branch mapping any more.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org


Mime
View raw message