This is an automated email from the ASF dual-hosted git repository.
zhangduo pushed a change to branch HBASE-29930
in repository https://gitbox.apache.org/repos/asf/hbase.git
discard 752b5c26ba8 add license
discard 57b3e9f3540 fix
discard a2874203f56 fiox
discard 9b2984f5aed fix
discard 702568dcf2d fix
discard 190cd67ada9 fix
discard 16403887826 fix
discard d8528cc04ea fix
discard efcd396d93f fix
discard 37cee28dff7 fix
discard d97eb9e50e6 fix
discard 90a37ef641f fix
discard 6115dca5734 fix
discard e7ef80c92c4 fix
discard 1bdccbfddf6 HBASE-29930 Separate packaging and integration check in
nightly job to new jenkins job
new a98a59cdc36 HBASE-29930 Separate packaging and integration check in
nightly job to new jenkins job
new e27494bd774 add comment
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 (752b5c26ba8)
\
N -- N -- N refs/heads/HBASE-29930 (e27494bd774)
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:
.../integration-test/integration-test.Jenkinsfile | 22 ++++++++++++----------
1 file changed, 12 insertions(+), 10 deletions(-)
