Started by user <a href='/cbi/user/frederic.gurr@eclipse-foundation.org' class='jenkins-table__link model-link model-link--float'>Frederic Gurr</a>
Running in Durability level: PERFORMANCE_OPTIMIZED
<span class="pipeline-new-node" nodeId="2" startId="2">[Pipeline] Start of Pipeline
</span><span class="pipeline-new-node" nodeId="3" startId="3" enclosingId="2">[Pipeline] podTemplate
</span><span class="pipeline-new-node" nodeId="4" startId="4" enclosingId="3">[Pipeline] {
</span><span class="pipeline-new-node" nodeId="5" startId="5" enclosingId="4">[Pipeline] node
</span><span class="pipeline-node-5">Still waiting to schedule task
There are no nodes with the label ‘my-agent-pod’
Agent <a href='/cbi/computer/my-agent-pod-d0fh0-jm9bt' class='jenkins-table__link model-link model-link--float'>my-agent-pod-d0fh0-jm9bt</a> is provisioned from template Kubernetes Pod Template
Agent specification [Kubernetes Pod Template] (my-agent-pod): 
yaml:

apiVersion: v1
kind: Pod
spec:
  containers:
  - name: maven
    image: maven:alpine
    command:
    - cat
    tty: true


Running on <a href='/cbi/computer/my-agent-pod-d0fh0-jm9bt/' class='jenkins-table__link model-link model-link--float'>my-agent-pod-d0fh0-jm9bt</a> in /home/jenkins/workspace/jiro_containerLog_test
</span><span class="pipeline-new-node" nodeId="6" startId="6" enclosingId="5">[Pipeline] {
</span><span class="pipeline-new-node" nodeId="7" startId="7" enclosingId="6">[Pipeline] stage
</span><span class="pipeline-new-node" nodeId="8" startId="8" enclosingId="7" label="Run maven">[Pipeline] { (Run maven)
</span><span class="pipeline-new-node" nodeId="9" startId="9" enclosingId="8">[Pipeline] container
</span><span class="pipeline-new-node" nodeId="10" startId="10" enclosingId="9">[Pipeline] {
</span><span class="pipeline-new-node" nodeId="11" enclosingId="10">[Pipeline] sh
</span><span class="pipeline-node-11">+ mvn -version
Apache Maven 3.6.1 (d66c9c0b3152b2e69ee9bac180bb8fcc8e6af555; 2019-04-04T19:00:29Z)
Maven home: /usr/share/maven
Java version: 1.8.0_212, vendor: IcedTea, runtime: /usr/lib/jvm/java-1.8-openjdk/jre
Default locale: en_US, platform encoding: UTF-8
OS name: "linux", version: "3.10.0-957.10.1.el7.x86_64", arch: "amd64", family: "unix"
</span><span class="pipeline-new-node" nodeId="12" enclosingId="10">[Pipeline] containerLog
</span><span class="pipeline-node-12">&gt; start log of container 'jnlp' in pod 'my-agent-pod-d0fh0-jm9bt'
VM settings:
    Max. Heap Size: 256.00M
    Ergonomics Machine Class: server
    Using VM: Eclipse OpenJ9 VM

Jun 14, 2019 11:27:26 AM hudson.remoting.jnlp.Main createEngine
INFO: Setting up agent: my-agent-pod-d0fh0-jm9bt
Jun 14, 2019 11:27:26 AM hudson.remoting.jnlp.Main$CuiListener &lt;init&gt;
INFO: Jenkins agent is running in headless mode.
Jun 14, 2019 11:27:26 AM hudson.remoting.Engine startEngine
INFO: Using Remoting version: 3.27
Jun 14, 2019 11:27:26 AM org.jenkinsci.remoting.engine.WorkDirManager initializeWorkDir
INFO: Using /home/jenkins/agent/remoting as a remoting work directory
Both error and output logs will be printed to /home/jenkins/agent/remoting
Jun 14, 2019 11:27:27 AM hudson.remoting.jnlp.Main$CuiListener status
INFO: Locating server among [<a href='http://jenkins-ui.cbi.svc.cluster.local/cbi/'>http://jenkins-ui.cbi.svc.cluster.local/cbi/</a>]
Jun 14, 2019 11:27:32 AM org.jenkinsci.remoting.engine.JnlpAgentEndpointResolver resolve
INFO: Remoting server accepts the following protocols: [JNLP4-connect, Ping]
Jun 14, 2019 11:27:32 AM org.jenkinsci.remoting.engine.JnlpAgentEndpointResolver resolve
INFO: Remoting TCP connection tunneling is enabled. Skipping the TCP Agent Listener Port availability check
Jun 14, 2019 11:27:32 AM hudson.remoting.jnlp.Main$CuiListener status
INFO: Agent discovery successful
  Agent address: jenkins-discovery.cbi.svc.cluster.local
  Agent port:    50000
  Identity:      ff:27:d5:22:a3:69:5c:83:db:b2:47:4b:67:7b:72:17
Jun 14, 2019 11:27:32 AM hudson.remoting.jnlp.Main$CuiListener status
INFO: Handshaking
Jun 14, 2019 11:27:32 AM hudson.remoting.jnlp.Main$CuiListener status
INFO: Connecting to jenkins-discovery.cbi.svc.cluster.local:50000
Jun 14, 2019 11:27:32 AM hudson.remoting.jnlp.Main$CuiListener status
INFO: Trying protocol: JNLP4-connect
Jun 14, 2019 11:27:33 AM hudson.remoting.jnlp.Main$CuiListener status
INFO: Remote identity confirmed: ff:27:d5:22:a3:69:5c:83:db:b2:47:4b:67:7b:72:17
Jun 14, 2019 11:27:37 AM hudson.remoting.jnlp.Main$CuiListener status
INFO: Connected
&gt; end log of container 'jnlp' in pod 'my-agent-pod-d0fh0-jm9bt'
</span><span class="pipeline-new-node" nodeId="13" enclosingId="10">[Pipeline] containerLog
</span><span class="pipeline-node-13">&gt; start log of container 'maven' in pod 'my-agent-pod-d0fh0-jm9bt'
&gt; end log of container 'maven' in pod 'my-agent-pod-d0fh0-jm9bt'
</span><span class="pipeline-new-node" nodeId="14" startId="10">[Pipeline] }
</span><span class="pipeline-new-node" nodeId="15" startId="9">[Pipeline] // container
</span><span class="pipeline-new-node" nodeId="16" startId="8">[Pipeline] }
</span><span class="pipeline-new-node" nodeId="17" startId="7">[Pipeline] // stage
</span><span class="pipeline-new-node" nodeId="18" startId="6">[Pipeline] }
</span><span class="pipeline-new-node" nodeId="19" startId="5">[Pipeline] // node
</span><span class="pipeline-new-node" nodeId="20" startId="4">[Pipeline] }
</span><span class="pipeline-new-node" nodeId="21" startId="3">[Pipeline] // podTemplate
</span><span class="pipeline-new-node" nodeId="22" startId="2">[Pipeline] End of Pipeline
</span>Finished: SUCCESS