[
https://issues.apache.org/jira/browse/HDDS-891?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16770078#comment-16770078
]
Elek, Marton commented on HDDS-891:
-----------------------------------
I did it *before* your -1: I tried to create a personality and tested with
Precommit-HDDS-Admin-nextgen and Precommit-HDDS-Admin how does it work:
[https://gist.github.com/elek/315f251b71bfb8d5f66e99eafbca7808/revisions] -->
Created on 13th of October
This issue is created ~1.5 month later to use similar personality.
The jenkins job is changed at the creation of this Jira (before your -1)
[https://builds.apache.org/job/PreCommit-HDDS-Build/jobConfigHistory/showDiffFiles?timestamp1=2018-10-07_23-04-54×tamp2=2018-12-03_09-06-15]
Now I am really stuck, and I don't know how should I go forward with Yetus. And
I would really appreciate any help (and answers)!
(ps: you are right, I didn't modify the job since then, because I didn't know
what should I do, I tried to continue the discussion. And thanks the reminder,
I removed the test personality from the job configuration.)
Can you please answer my questions and give me instructions how can we achieve
the goals which are defined above? Thanks a lot.
> 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: [email protected]
For additional commands, e-mail: [email protected]
