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

pgj pushed a change to branch jenkins-clouseau-3.0.0
in repository https://gitbox.apache.org/repos/asf/couchdb.git


 discard fc83ebdac Add timeout for the Clouseau tests for the containerized 
builders
 discard 4c63aba92 Set Erlang cookie explicitly for running Clouseau
 discard 10a13fc7b Make `CLOUSEAU_JAVA_HOME` configurable explicitly
 discard bc4dd4071 chore(`clouseau`): bump to 3.0.0
     new 1f99bbf9f chore(`clouseau`): bump to 3.0.0
     new 0c1997749 Make `CLOUSEAU_JAVA_HOME` configurable explicitly
     new bd4df7ab0 Set Erlang cookie explicitly for running Clouseau
     new 5d0f6a310 Set timeout for Clouseau tests on containerized builders

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   (fc83ebdac)
            \
             N -- N -- N   refs/heads/jenkins-clouseau-3.0.0 (5d0f6a310)

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 4 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:
 build-aux/Jenkinsfile | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

Reply via email to