[
https://issues.apache.org/jira/browse/HBASE-30133?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18079230#comment-18079230
]
Hudson commented on HBASE-30133:
--------------------------------
Results for branch master
[build #1447 on
builds.a.o|https://ci-hbase.apache.org/job/HBase%20Nightly/job/master/1447/]:
(x) *{color:red}-1 overall{color}*
----
details (if available):
(x) {color:red}-1 general checks{color}
-- For more information [see general
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/master/1447/General_20Nightly_20Build_20Report/]
(/) {color:green}+1 jdk17 hadoop3 checks{color}
-- For more information [see jdk17
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/master/1447/JDK17_20Nightly_20Build_20Report_20_28Hadoop3_29/]
> 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)
