SuccessConsole Output

Started by user Frederic Gurr
Running in Durability level: PERFORMANCE_OPTIMIZED
[Pipeline] Start of Pipeline
[Pipeline] node
Still waiting to schedule task
‘centslave1’ is reserved for jobs with matching label expression; ‘fmlw3-ubuntu1804’ is reserved for jobs with matching label expression; ‘mac-tests2’ is reserved for jobs with matching label expression
Agent default-agent-pvjzx is provisioned from template Kubernetes Pod Template
Agent specification [Kubernetes Pod Template] (null): 
* [jnlp] eclipsecbijenkins/jenkins-agent:latest@sha256:b0988972cc41814d7d9299d7c2c69858716c41afb4ba1f6a30448b6da1a0a4a4(resourceRequestCpu: 1000m, resourceRequestMemory: 4096Mi, resourceLimitCpu: 2000m, resourceLimitMemory: 4096Mi)
yaml:
apiVersion: v1
kind: Pod
spec:
  containers:
  - name: jnlp
    volumeMounts:
    - name: settings-xml
      mountPath: /home/jenkins/.m2/settings.xml
      subPath: settings.xml
      readOnly: true
    - name: toolchains-xml
      mountPath: /home/jenkins/.m2/toolchains.xml
      subPath: toolchains.xml
      readOnly: true
  volumes:
  - name: settings-xml
    configMap:
      name: m2-dir
      items:
      - key: settings.xml
        path: settings.xml
  - name: toolchains-xml
    configMap:
      name: m2-dir
      items:
      - key: toolchains.xml
        path: toolchains.xml


Running on default-agent-pvjzx in /home/jenkins/workspace/jiro_containerLog_test
[Pipeline] {
[Pipeline] echo
Hello World
[Pipeline] containerLog
> start log of container 'jnlp' in pod 'default-agent-pvjzx'
VM settings:
    Max. Heap Size: 256.00M
    Ergonomics Machine Class: server
    Using VM: Eclipse OpenJ9 VM

Jun 13, 2019 5:54:07 PM hudson.remoting.jnlp.Main createEngine
INFO: Setting up agent: default-agent-pvjzx
Jun 13, 2019 5:54:07 PM hudson.remoting.jnlp.Main$CuiListener <init>
INFO: Jenkins agent is running in headless mode.
Jun 13, 2019 5:54:07 PM hudson.remoting.Engine startEngine
INFO: Using Remoting version: 3.27
Jun 13, 2019 5:54:07 PM 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 13, 2019 5:54:07 PM hudson.remoting.jnlp.Main$CuiListener status
INFO: Locating server among [http://jenkins-ui.cbi.svc.cluster.local/cbi/]
Jun 13, 2019 5:54:12 PM org.jenkinsci.remoting.engine.JnlpAgentEndpointResolver resolve
INFO: Remoting server accepts the following protocols: [JNLP4-connect, Ping]
Jun 13, 2019 5:54:12 PM org.jenkinsci.remoting.engine.JnlpAgentEndpointResolver resolve
INFO: Remoting TCP connection tunneling is enabled. Skipping the TCP Agent Listener Port availability check
Jun 13, 2019 5:54:12 PM 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 13, 2019 5:54:12 PM hudson.remoting.jnlp.Main$CuiListener status
INFO: Handshaking
Jun 13, 2019 5:54:12 PM hudson.remoting.jnlp.Main$CuiListener status
INFO: Connecting to jenkins-discovery.cbi.svc.cluster.local:50000
Jun 13, 2019 5:54:12 PM hudson.remoting.jnlp.Main$CuiListener status
INFO: Trying protocol: JNLP4-connect
Jun 13, 2019 5:54:12 PM 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 13, 2019 5:54:13 PM hudson.remoting.jnlp.Main$CuiListener status
INFO: Connected
> end log of container 'jnlp' in pod 'default-agent-pvjzx'
[Pipeline] }
[Pipeline] // node
[Pipeline] End of Pipeline
Finished: SUCCESS