You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Nick Dimiduk (Jira)" <ji...@apache.org> on 2026/05/04 14:57:00 UTC

[jira] [Resolved] (HBASE-30133) Add opt-in yetus prerelease testing to GitHub Actions precommit

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

Nick Dimiduk resolved HBASE-30133.
----------------------------------
    Resolution: Fixed

Pushed to branch-2.5+. Thanks [~charlesconnell] for the review.

> Add opt-in yetus prerelease testing to GitHub Actions precommit
> ---------------------------------------------------------------
>
>                 Key: HBASE-30133
>                 URL: https://issues.apache.org/jira/browse/HBASE-30133
>             Project: HBase
>          Issue Type: Task
>          Components: build
>            Reporter: Nick Dimiduk
>            Assignee: Nick Dimiduk
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 4.0.0-alpha-1, 3.0.0-beta-2, 2.5.15, 2.6.6
>
>
> The yetus precommit workflows in GitHub Actions all pin a specific released Apache Yetus version. With Jenkins PR builds retired, the community has no way to validate an unreleased Yetus revision against a real HBase PR before bumping the pinned version. There's a new Yetus release coming and it would be good to get ahead of it. Add an opt-in toggle that switches the Yetus checks to a development revision of apache/yetus, logging the resolved revision so runs are reproducible.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)