Started by an SCM change
Running as SYSTEM
Building on master in workspace /var/jenkins/workspace/websocket-api-master
No credentials specified
> git rev-parse --is-inside-work-tree # 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 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
> git rev-parse refs/remotes/origin/origin/master^{commit} # timeout=10
Checking out Revision 9f948684421687903a703f6b5a99f1b92413f958 (refs/remotes/origin/master)
> git config core.sparsecheckout # timeout=10
> git checkout -f 9f948684421687903a703f6b5a99f1b92413f958 # timeout=10
Commit message: "Align execution ID with parent POM to avoid duplicate executions"
> git rev-list --no-walk 43593d66425c9671015b3cf3587ca850ac996fdf # timeout=10
Triggering websocket-api-master » openjdk-latest
Triggering websocket-api-master » adoptopenjdk-openj9-latest
Triggering websocket-api-master » oracle-latest
Triggering websocket-api-master » adoptopenjdk-hotspot-latest
Triggering websocket-api-master » adoptopenjdk-hotspot-jdk11-latest
Triggering websocket-api-master » adoptopenjdk-hotspot-jdk8-latest
Triggering websocket-api-master » adoptopenjdk-openj9-jdk11-latest
Triggering websocket-api-master » adoptopenjdk-openj9-jdk8-latest
Triggering websocket-api-master » ibm-jdk8-latest
Triggering websocket-api-master » oracle-jdk8-latest
Triggering websocket-api-master » openjdk-jdk11-latest
Triggering websocket-api-master » ibm-latest
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
websocket-api-master » oracle-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
websocket-api-master » adoptopenjdk-hotspot-jdk11-latest completed with result SUCCESS
websocket-api-master » adoptopenjdk-hotspot-jdk8-latest completed with result SUCCESS
websocket-api-master » adoptopenjdk-openj9-jdk11-latest completed with result SUCCESS
websocket-api-master » adoptopenjdk-openj9-jdk8-latest completed with result SUCCESS
Configuration websocket-api-master » ibm-jdk8-latest is still in the queue: Waiting for next available executor
websocket-api-master » ibm-jdk8-latest completed with result SUCCESS
websocket-api-master » oracle-jdk8-latest completed with result SUCCESS
Configuration websocket-api-master » openjdk-jdk11-latest is still in the queue: Waiting for next available executor
websocket-api-master » openjdk-jdk11-latest completed with result SUCCESS
websocket-api-master » ibm-latest completed with result SUCCESS
Triggering a new build of WebSocket copyright and style check
Finished: SUCCESS