[ 
https://issues.apache.org/jira/browse/HBASE-30133?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18078370#comment-18078370
 ] 

Hudson commented on HBASE-30133:
--------------------------------

Results for branch branch-2
        [build #50 on 
builds.a.o|https://ci-hbase.apache.org/job/HBase-Integration-Test/job/branch-2/50/]:
 (/) *{color:green}+1 overall{color}*
----
details (if available):



(/) {color:green}+1 client integration test for 2.10.2 {color}


(/) {color:green}+1 client integration test for 3.3.5 {color}
(/) {color:green}+1 client integration test for 3.3.5 with shaded hadoop 
client{color}


(/) {color:green}+1 client integration test for 3.3.6 {color}
(/) {color:green}+1 client integration test for 3.3.6 with shaded hadoop 
client{color}


(/) {color:green}+1 client integration test for 3.4.0 {color}
(/) {color:green}+1 client integration test for 3.4.0 with shaded hadoop 
client{color}


(/) {color:green}+1 client integration test for 3.4.1 {color}
(/) {color:green}+1 client integration test for 3.4.1 with shaded hadoop 
client{color}


(/) {color:green}+1 client integration test for 3.4.2 {color}
(/) {color:green}+1 client integration test for 3.4.2 with shaded hadoop 
client{color}


(/) {color:green}+1 client integration test for 3.4.3 {color}
(/) {color:green}+1 client integration test for 3.4.3 with shaded hadoop 
client{color}


> 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)

Reply via email to