[
https://issues.apache.org/jira/browse/HBASE-23873?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17079566#comment-17079566
]
Nick Dimiduk commented on HBASE-23873:
--------------------------------------
Looking around the Yetus project, looks like devs there make the same
assumption, for example the GitHub actions scripts. Maybe this isn't so bad
after all?
[~busbey] ^^^
> Update test-patch.sh path for git-checkout use-cases to account for the new
> module layout in Yetus
> --------------------------------------------------------------------------------------------------
>
> Key: HBASE-23873
> URL: https://issues.apache.org/jira/browse/HBASE-23873
> Project: HBase
> Issue Type: Task
> Components: build
> Reporter: Nick Dimiduk
> Priority: Major
>
> It was noticed over on HBASE-23779 that we support running Yetus
> pre-commit/test-patch.sh directly out of a git checkout/source tarball.
> However, not all usages of this form of Yetus have been upgraded to the new
> maven layout. It appears we make this assumption in:
> * The Jenkins job configuration on
> [PreCommit-HBASE-Build|https://builds.apache.org/view/H-L/view/HBase/job/PreCommit-HBASE-Build/configure]
> * {{dev-support/Jenkinsfile_GitHub}}
> * {{dev-support/hbase_nightly_yetus.sh}}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
