[
https://issues.apache.org/jira/browse/HDFS-13510?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marton Elek resolved HDFS-13510.
--------------------------------
Resolution: Won't Fix
> Ozone: Fix precommit hook for Ozone/Hdds on trunk
> -------------------------------------------------
>
> Key: HDFS-13510
> URL: https://issues.apache.org/jira/browse/HDFS-13510
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Reporter: Marton Elek
> Assignee: Marton Elek
> Priority: Major
>
> Current precommit doesn't work with the ozone projects as they are in an
> optional profile.
> This jira may not have any code change but I opened it to track the required
> changes on builds.apache.org and make the changes more transparent.
> I think we need the following changes:
> 1. Separated jira subproject, as planned
> 2. After that we can create new Precommit-OZONE-Build job which will be
> triggered by the PreCommit-Admin (jira filter should be modified)
> 3. In the Precommit-OZONE-Build we need to enable the hdds profile. It could
> be done by modifying the yetus personality or the create a .mvn/mvn.config
> 4. We need the ozone/hdds snapshot artifacts in apache nexus:
> a.) One option is adding -P hdds to the Hadoop-trunk-Commit. This is the
> simplified but Hdds/Ozone build failure will cause missing artifacts on nexus
> (low chance as the merge will be guarded by PreCommit hook)
> b.) Other options is to create a Hadoop-Ozone-trunk-Commit which do a full
> compilation but only hdds and ozone artifacts will be deployed (some sync
> problem maybe here if different core artifacts are uploaded...)
> 5. And we also need a daily unit test run. (qbt)
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-dev-h...@hadoop.apache.org
