This is an automated email from the ASF dual-hosted git repository.
zhangduo pushed a change to branch HBASE-28694-branch-2
in repository https://gitbox.apache.org/repos/asf/hbase.git
discard 843db2fdbac only run integration test
discard 2ae19fc4a81 HBASE-28694 Make client integration and packaging test
work with java 17
add 4cf8c5b5ec2 HBASE-28678 Addendum add jdk17 result path env
add 4c882ecf4f0 HBASE-28678 Addendum align the nightly jenkinsfile with
master branch
new 586376490ab HBASE-28694 Make client integration and packaging test
work with java 17
new ba6ce5e26e5 only run integration test
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 (843db2fdbac)
\
N -- N -- N refs/heads/HBASE-28694-branch-2 (ba6ce5e26e5)
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 2 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 | 1 +
1 file changed, 1 insertion(+)
