This is an automated email from the ASF dual-hosted git repository.

taybou pushed a change to branch update-jenkinsfile
in repository https://gitbox.apache.org/repos/asf/unomi.git.


 discard 1d86eaf  update Jenkinsfile & Jenkinsfile-jdk11
 discard 42f82a8  update Jenkinsfile & Jenkinsfile-jdk11
 discard b9bc836  update Jenkinsfile & Jenkinsfile-jdk11
 discard 347e2c1  update Jenkinsfile & Jenkinsfile-jdk11
 discard ba3228d  update Jenkinsfile & Jenkinsfile-jdk11
 discard 35cc916  Skip tests in jenkins deploy stage
     add b0d10d2  Skip tests in jenkins deploy stage

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   (1d86eaf)
            \
             N -- N -- N   refs/heads/update-jenkinsfile (b0d10d2)

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:
 Jenkinsfile                      | 42 ++++++++++++++++++--------------------
 Jenkinsfile => Jenkinsfile-jdk11 | 44 +++++++++++++++++++---------------------
 2 files changed, 41 insertions(+), 45 deletions(-)
 copy Jenkinsfile => Jenkinsfile-jdk11 (88%)

Reply via email to