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

Elek, Marton commented on HDDS-891:
-----------------------------------

bq. and for reasons which have yet to be justified as to why that is desirable. 

Sorry if it was not clear enough from my last paragraph, my fault. The reason 
is the simplicity and maintainability. I believe that one project could be 
built with two separated personalities: 1) if it's more easy to maintain 2) 
there are two separated build paths.

I agree with you: we need to rethink the whole build process when we will 
deliver ozone together with the main hadoop release.  

> Create customized yetus personality for ozone
> ---------------------------------------------
>
>                 Key: HDDS-891
>                 URL: https://issues.apache.org/jira/browse/HDDS-891
>             Project: Hadoop Distributed Data Store
>          Issue Type: Improvement
>            Reporter: Elek, Marton
>            Assignee: Elek, Marton
>            Priority: Major
>
> Ozone pre commit builds (such as 
> https://builds.apache.org/job/PreCommit-HDDS-Build/) use the official hadoop 
> personality from the yetus personality.
> Yetus personalities are bash scripts which contain personalization for 
> specific builds.
> The hadoop personality tries to identify which project should be built and 
> use partial build to build only the required subprojects because the full 
> build is very time consuming.
> But in Ozone:
> 1.) The build + unit tests are very fast
> 2.) We don't need all the checks (for example the hadoop specific shading 
> test)
> 3.) We prefer to do a full build and full unit test for hadoop-ozone and 
> hadoop-hdds subrojects (for example the hadoop-ozone integration test always 
> should be executed as it contains many generic unit test)



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

---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org

Reply via email to