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

sergehuber pushed a change to branch server-tests-features
in repository https://gitbox.apache.org/repos/asf/unomi-tracker.git


 discard 29eb99c  Merge remote-tracking branch 'origin/ci-server-tests' into 
server-tests-features
    omit 9215cea  Wait for the Unomi 4 health check before setting it up
 discard d3d8d4e  Test personalization, fallbacks, clicks and forms against 
each Unomi server
 discard e322804  UNOMI-1037, UNOMI-1038: Track every click, and fix 
sourceLocalIdentifierMap
    omit d5255f4  Wait until Unomi answers steadily before the server tests
    omit 5fe2a07  Run only Unomi 3 and Unomi 4 on pull requests
    omit 2253404  Run the tracker tests against each Unomi server on every pull 
request
     add 92f19dd  Run the tracker tests against Unomi 3 and Unomi 4 on every 
pull request (#37)
     add 12c6dec  UNOMI-1037, UNOMI-1038: Track every click, and fix 
sourceLocalIdentifierMap
     add a599f11  Test personalization, fallbacks, clicks and forms against 
each Unomi server

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   (29eb99c)
            \
             N -- N -- N   refs/heads/server-tests-features (a599f11)

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:

Reply via email to