This is an automated email from the ASF dual-hosted git repository.
dacort pushed a change to branch fix/log4j-reload4j
in repository https://gitbox.apache.org/repos/asf/incubator-livy.git
discard 7ff3ec14 Trigger CI
discard cb38bec9 Exclude log4j from apacheds-server-integ
discard 1f1eaf56 Also bump slf4j
discard 92693774 initial attempt at reload4j and excluding transitive
dependencies
add da246ff3 [LIVY-972] Add GitHub Action for CI image (#393)
add 0f220060 initial attempt at reload4j and excluding transitive
dependencies
add 16ff9100 Also bump slf4j
add 58a2c2db Exclude log4j from apacheds-server-integ
add a59259c7 Trigger CI
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 (7ff3ec14)
\
N -- N -- N refs/heads/fix/log4j-reload4j (a59259c7)
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.
No new revisions were added by this update.
Summary of changes:
.github/workflows/build-ci-image.yaml | 48 ++++++++++++++++++++++++++++
.github/workflows/integration-tests.yaml | 54 ++++++++++++++++++++++++++++++++
.github/workflows/unit-tests.yaml | 52 ++++++++++++++++++++++++++++++
3 files changed, 154 insertions(+)
create mode 100644 .github/workflows/build-ci-image.yaml
create mode 100644 .github/workflows/integration-tests.yaml
create mode 100644 .github/workflows/unit-tests.yaml
