Uploaded image for project: 'Hadoop HDFS'
  1. Hadoop HDFS
  2. HDFS-7240 Scaling HDFS
  3. HDFS-13510

Ozone: Fix precommit hook for Ozone/Hdds on trunk

VotersWatch issueWatchersLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Sub-task
    • Status: Resolved
    • Major
    • Resolution: Won't Fix
    • None
    • None
    • None
    • None

    Description

      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)

      Attachments

        Issue Links

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            elek Marton Elek
            elek Marton Elek
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment