This is an automated email from the ASF dual-hosted git repository.
zhangduo pushed a change to branch HBASE-28678-branch-2
in repository https://gitbox.apache.org/repos/asf/hbase.git
discard 1221d452dde HBASE-28678 Make nightly builds for 3.x java 17 only and
add java 17 test for 2.x
add d06604571e3 HBASE-28656 Optimize the verifyCopyResult logic in
ExportSnapshot (#5996)
add 8fd1ecab8e5 HBASE-28677 Add jdk 17 task for pre commit build for 2.x
(#6002)
add 5e2d66d2121 Revert "HBASE-28677 Add jdk 17 task for pre commit build
for 2.x (#6002)"
add 30013067216 HBASE-28677 Add jdk 17 task for pre commit build for 2.x
(#6002)
new 1fd1c5e1203 HBASE-28678 Make nightly builds for 3.x java 17 only and
add java 17 test for 2.x
This update added new revisions after undoing existing revisions.
That is to say, some revisions that were in the old version of the
branch are not in the new version. This situation occurs
when a user --force pushes a change and generates a repository
containing something like this:
* -- * -- B -- O -- O -- O (1221d452dde)
\
N -- N -- N refs/heads/HBASE-28678-branch-2 (1fd1c5e1203)
You should already have received notification emails for all of the O
revisions, and so the following emails describe only the N revisions
from the common base, B.
Any revisions marked "omit" are not gone; other references still
refer to them. Any revisions marked "discard" are gone forever.
The 1 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails. The revisions
listed as "add" were already present in the repository and have only
been added to this reference.
Summary of changes:
dev-support/Jenkinsfile_GitHub | 138 +++++++++++++++++++++
dev-support/docker/Dockerfile | 15 +++
.../hadoop/hbase/snapshot/ExportSnapshot.java | 76 ++++++++++--
.../hadoop/hbase/snapshot/TestExportSnapshot.java | 26 +++-
.../hbase/snapshot/TestExportSnapshotAdjunct.java | 4 +-
.../snapshot/TestExportSnapshotV1NoCluster.java | 2 +-
6 files changed, 245 insertions(+), 16 deletions(-)
