Started by an SCM change
Running as SYSTEM
Building in workspace /var/jenkins/workspace/websocket-api-master
The recommended git tool is: NONE
No credentials specified
 > git rev-parse --resolve-git-dir /var/jenkins/workspace/websocket-api-master/.git # timeout=10
Fetching changes from the remote Git repository
 > git config remote.origin.url https://github.com/eclipse-ee4j/websocket-api.git # timeout=10
Fetching upstream changes from https://github.com/eclipse-ee4j/websocket-api.git
 > git --version # timeout=10
 > git --version # 'git version 2.20.1'
 > git fetch --tags --force --progress -- https://github.com/eclipse-ee4j/websocket-api.git +refs/heads/*:refs/remotes/origin/* # timeout=10
 > git rev-parse refs/remotes/origin/master^{commit} # timeout=10
Checking out Revision 7f996bdddc2a9ad1f710bd08ca36737c9e556728 (refs/remotes/origin/master)
 > git config core.sparsecheckout # timeout=10
 > git checkout -f 7f996bdddc2a9ad1f710bd08ca36737c9e556728 # timeout=10
Commit message: "fix 405 The WebSocket.adoc chpater A.3 Pull Request 315 link wrong url"
 > git rev-list --no-walk fccf2387662c5da6db3a2e66fac7e3450ea3cbed # timeout=10
Triggering websocket-api-master » openjdk-latest
Triggering websocket-api-master » adoptopenjdk-openj9-latest
Triggering websocket-api-master » adoptopenjdk-hotspot-jdk11-latest
Triggering websocket-api-master » adoptopenjdk-openj9-jdk11-latest
Triggering websocket-api-master » openjdk-jdk17-latest
Triggering websocket-api-master » openjdk-jdk11-latest
Triggering websocket-api-master » temurin-latest
Triggering websocket-api-master » temurin-jdk11-latest
Triggering websocket-api-master » adoptopenjdk-hotspot-latest
Triggering websocket-api-master » temurin-jdk17-latest
Triggering websocket-api-master » adoptopenjdk-hotspot-latest-lts
Triggering websocket-api-master » adoptopenjdk-openj9-latest-lts
Configuration websocket-api-master » openjdk-latest is still in the queue: Waiting for next available executor
websocket-api-master » openjdk-latest completed with result SUCCESS
Configuration websocket-api-master » adoptopenjdk-openj9-latest is still in the queue: Waiting for next available executor
websocket-api-master » adoptopenjdk-openj9-latest completed with result SUCCESS
Configuration websocket-api-master » adoptopenjdk-hotspot-jdk11-latest is still in the queue: Waiting for next available executor
websocket-api-master » adoptopenjdk-hotspot-jdk11-latest completed with result SUCCESS
Configuration websocket-api-master » adoptopenjdk-openj9-jdk11-latest is still in the queue: Waiting for next available executor
websocket-api-master » adoptopenjdk-openj9-jdk11-latest completed with result SUCCESS
Configuration websocket-api-master » openjdk-jdk17-latest is still in the queue: Waiting for next available executor
websocket-api-master » openjdk-jdk17-latest completed with result SUCCESS
websocket-api-master » openjdk-jdk11-latest completed with result SUCCESS
Configuration websocket-api-master » temurin-latest is still in the queue: Waiting for next available executor
websocket-api-master » temurin-latest completed with result SUCCESS
Configuration websocket-api-master » temurin-jdk11-latest is still in the queue: Waiting for next available executor
websocket-api-master » temurin-jdk11-latest completed with result SUCCESS
Configuration websocket-api-master » adoptopenjdk-hotspot-latest is still in the queue: Waiting for next available executor
websocket-api-master » adoptopenjdk-hotspot-latest completed with result SUCCESS
Configuration websocket-api-master » temurin-jdk17-latest is still in the queue: Waiting for next available executor
websocket-api-master » temurin-jdk17-latest completed with result SUCCESS
websocket-api-master » adoptopenjdk-hotspot-latest-lts completed with result SUCCESS
websocket-api-master » adoptopenjdk-openj9-latest-lts completed with result SUCCESS
[Static Analysis] Reference build recorder is not configured
[Static Analysis] Obtaining reference build from same job (websocket-api-master)
[Static Analysis] Using reference build 'websocket-api-master #51' to compute new, fixed, and outstanding issues
[Static Analysis] Issues delta (vs. reference build): outstanding: 4, new: 3, fixed: 0
[Static Analysis] No quality gates have been set - skipping
[Static Analysis] Health report is disabled - skipping
[Static Analysis] Created analysis result for 7 issues (found 3 new issues, fixed 0 issues)
[Static Analysis] Attaching ResultAction with ID 'java' to build 'websocket-api-master #52'.
[Checks API] No suitable checks publisher found.
[Static Analysis] Reference build recorder is not configured
[Static Analysis] Obtaining reference build from same job (websocket-api-master)
[Static Analysis] Using reference build 'websocket-api-master #51' to compute new, fixed, and outstanding issues
[Static Analysis] Issues delta (vs. reference build): outstanding: 0, new: 0, fixed: 0
[Static Analysis] No quality gates have been set - skipping
[Static Analysis] Health report is disabled - skipping
[Static Analysis] Created analysis result for 0 issues (found 0 new issues, fixed 0 issues)
[Static Analysis] Attaching ResultAction with ID 'spotbugs' to build 'websocket-api-master #52'.
[Checks API] No suitable checks publisher found.
[Static Analysis] Reference build recorder is not configured
[Static Analysis] Obtaining reference build from same job (websocket-api-master)
[Static Analysis] Using reference build 'websocket-api-master #51' to compute new, fixed, and outstanding issues
[Static Analysis] Issues delta (vs. reference build): outstanding: 0, new: 1, fixed: 0
[Static Analysis] No quality gates have been set - skipping
[Static Analysis] Health report is disabled - skipping
[Static Analysis] Created analysis result for 1 issues (found 1 new issues, fixed 0 issues)
[Static Analysis] Attaching ResultAction with ID 'javadoc-warnings' to build 'websocket-api-master #52'.
[Checks API] No suitable checks publisher found.
Triggering a new build of WebSocket copyright and style check
Finished: SUCCESS