[
https://issues.apache.org/jira/browse/HBASE-30316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18105146#comment-18105146
]
Hudson commented on HBASE-30316:
--------------------------------
Results for branch master
[build #1487 on
builds.a.o|https://ci-hbase.apache.org/job/HBase%20Nightly/job/master/1487/]:
(x) *{color:red}-1 overall{color}*
----
details (if available):
(/) {color:green}+1 general checks{color}
-- For more information [see general
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/master/1487/General_20Nightly_20Build_20Report/]
(x) {color:red}-1 jdk17 hadoop3 checks{color}
-- For more information [see jdk17
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/master/1487/JDK17_20Nightly_20Build_20Report_20_28Hadoop3_29/]
> Enhance hbase_docker to support RC tarball and local source input modes, and
> add automated vote verification workflow
> ---------------------------------------------------------------------------------------------------------------------
>
> Key: HBASE-30316
> URL: https://issues.apache.org/jira/browse/HBASE-30316
> Project: HBase
> Issue Type: Improvement
> Reporter: Aman Poonia
> Assignee: Aman Poonia
> Priority: Minor
> Labels: pull-request-available
> Fix For: 4.0.0-alpha-1
>
>
> The existing dev-support/hbase_docker/Dockerfile only supports building from
> a remote git branch or tag. This makes it unusable for testing unpushed
> local
> branches or verifying release candidate artifacts directly from the signed
> source tarball.
>
> This improvement adds an INPUT_MODE build argument (default: tag, preserving
> existing behavior) with two additional modes:
> - tarball: build from a local signed source tarball (e.g.
> hbase-2.6.7-src.tar.gz)
> - source-dir: build from a local directory (uncommitted changes included)
> Optionally in a subsequent Jira we can add a RUN_SMOKE_TESTS flag (default:
> false) that runs basic
> DDL/CRUD operations on startup and reports pass/fail instead of dropping
> to hbase shell.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
