You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@hbase.apache.org by "Sean Busbey (JIRA)" <ji...@apache.org> on 2019/07/25 17:43:00 UTC

[jira] [Resolved] (HBASE-17188) Improve precommit handling of modules to run against so that when top level is changed, only the top level is run

     [ https://issues.apache.org/jira/browse/HBASE-17188?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Sean Busbey resolved HBASE-17188.
---------------------------------
    Resolution: Duplicate

this got fixed at some point, but I don't know when.

> Improve precommit handling of modules to run against so that when top level is changed, only the top level is run
> -----------------------------------------------------------------------------------------------------------------
>
>                 Key: HBASE-17188
>                 URL: https://issues.apache.org/jira/browse/HBASE-17188
>             Project: HBase
>          Issue Type: Task
>          Components: build, community
>            Reporter: Sean Busbey
>            Priority: Minor
>              Labels: beginner
>
> Our personality's definition of which modules to run (called "personality_modules") should make the optimization to only run the top level build when the "changed modules" includes the top-level (indicated with ".").
> An example of this can be found in the way the example Apache Yetus personality for Apache Hadoop handles the "unit" test type : [ref github|https://github.com/apache/yetus/blob/master/precommit/personality/hadoop.sh#L279]. We should do this for all test types.



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)