This is an automated email from the ASF dual-hosted git repository.
tibordigana pushed a change to branch sync-logs
in repository https://gitbox.apache.org/repos/asf/maven-surefire.git.
discard f60936e fixed checkstyle
discard 4e1bb6e investigating jenkins attachments
discard a045569 Javadoc fix and renamed field.
discard 37c1a32 [SUREFIRE-1926] Console logs should be synchronized
add 4ef0be9 [SUREFIRE-1926] Console logs should be synchronized
add a88a285 [jenkins] MVN 3.2 for branches, 3.2+3.6 for master [jenkins]
Using 'errorStatus' instead of checking the status of 'currentBuild.result'
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 (f60936e)
\
N -- N -- N refs/heads/sync-logs (a88a285)
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 | 11 ++---------
1 file changed, 2 insertions(+), 9 deletions(-)
