SuccessConsole Output

Started by user Frederic Gurr
Running in Durability level: PERFORMANCE_OPTIMIZED
[Pipeline] Start of Pipeline
[Pipeline] podTemplate
[Pipeline] {
[Pipeline] node
Still waiting to schedule task
There are no nodes with the label ‘my-agent-pod’
Agent my-agent-pod-d0fh0-jm9bt 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 my-agent-pod-d0fh0-jm9bt in /home/jenkins/workspace/jiro_containerLog_test
[Pipeline] {
[Pipeline] stage
[Pipeline] { (Run maven)
[Pipeline] container
[Pipeline] {
[Pipeline] sh
+ 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"
[Pipeline] containerLog
> 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 <init>
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 [http://jenkins-ui.cbi.svc.cluster.local/cbi/]
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
> end log of container 'jnlp' in pod 'my-agent-pod-d0fh0-jm9bt'
[Pipeline] containerLog
> start log of container 'maven' in pod 'my-agent-pod-d0fh0-jm9bt'
> end log of container 'maven' in pod 'my-agent-pod-d0fh0-jm9bt'
[Pipeline] }
[Pipeline] // container
[Pipeline] }
[Pipeline] // stage
[Pipeline] }
[Pipeline] // node
[Pipeline] }
[Pipeline] // podTemplate
[Pipeline] End of Pipeline
Finished: SUCCESS