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 192358c63b2 values
discard 878cb6dbdee add
discard ee8cdb8e7fb remove
discard 2faadff7fb9 fix
discard 12622d65ffc fix
discard b26c47d818c fix
discard f3189a6a6df add more steps
discard e27494bd774 add comment
discard a98a59cdc36 HBASE-29930 Separate packaging and integration check in
nightly job to new jenkins job
new a2f5783aee7 HBASE-29930 Separate packaging and integration check in
nightly job to new jenkins job
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 (192358c63b2)
\
N -- N -- N refs/heads/HBASE-29930 (a2f5783aee7)
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:
.../integration-test/integration-test.Jenkinsfile | 46 +++++++++++++++++++++-
1 file changed, 45 insertions(+), 1 deletion(-)
