Elek, Marton created HADOOP-16092:
-------------------------------------
Summary: 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
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-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-dev-h...@hadoop.apache.org
