Skip to content
Success

Console Output

Started by upstream project "publish-release" build number 14
originally caused by:
 Started by user Laurent Goubet
Running as Laurent Goubet
Agent centos-7-mtjps is provisioned from template centos-7
---
apiVersion: "v1"
kind: "Pod"
metadata:
  annotations: {}
  labels:
    jenkins: "slave"
    jenkins/label-digest: "55a177a28a71a1957f582df488f25d8c2f70df30"
    jenkins/label: "migration_jipp-migration_centos-7"
  name: "centos-7-mtjps"
  namespace: "emfcompare"
spec:
  containers:
  - env:
    - name: "JENKINS_SECRET"
      value: "********"
    - name: "JENKINS_TUNNEL"
      value: "jenkins-discovery.emfcompare.svc.cluster.local:50000"
    - name: "JENKINS_AGENT_NAME"
      value: "centos-7-mtjps"
    - name: "JENKINS_REMOTING_JAVA_OPTS"
      value: "-showversion -XshowSettings:vm -Xmx256m -Dorg.jenkinsci.remoting.engine.JnlpProtocol3.disabled=true\
        \ -Dorg.jenkinsci.plugins.gitclient.CliGitAPIImpl.useSETSID=true"
    - name: "JAVA_TOOL_OPTIONS"
      value: ""
    - name: "_JAVA_OPTIONS"
      value: ""
    - name: "OPENJ9_JAVA_OPTIONS"
      value: "-XX:+IgnoreUnrecognizedVMOptions -XX:+IdleTuningCompactOnIdle -XX:+IdleTuningGcOnIdle"
    - name: "JENKINS_NAME"
      value: "centos-7-mtjps"
    - name: "JENKINS_AGENT_WORKDIR"
      value: "/home/jenkins/agent"
    - name: "JENKINS_URL"
      value: "http://jenkins-ui.emfcompare.svc.cluster.local/emfcompare/"
    image: "docker.io/eclipsecbi/jiro-agent-centos-7:remoting-4.13.3"
    imagePullPolicy: "Always"
    name: "jnlp"
    resources:
      limits:
        cpu: "2000m"
        memory: "4096Mi"
      requests:
        cpu: "1000m"
        memory: "4096Mi"
    tty: true
    volumeMounts:
    - mountPath: "/home/jenkins/.m2/toolchains.xml"
      name: "m2-dir"
      readOnly: true
      subPath: "toolchains.xml"
    - mountPath: "/home/jenkins/.mavenrc"
      name: "m2-dir"
      readOnly: true
      subPath: ".mavenrc"
    - mountPath: "/opt/tools"
      name: "volume-0"
      readOnly: false
    - mountPath: "/home/jenkins"
      name: "volume-2"
      readOnly: false
    - mountPath: "/home/jenkins/.m2/repository"
      name: "volume-3"
      readOnly: false
    - mountPath: "/home/jenkins/.m2/settings-security.xml"
      name: "m2-secret-dir"
      readOnly: true
      subPath: "settings-security.xml"
    - mountPath: "/home/jenkins/.m2/wrapper"
      name: "volume-4"
      readOnly: false
    - mountPath: "/home/jenkins/.m2/settings.xml"
      name: "m2-secret-dir"
      readOnly: true
      subPath: "settings.xml"
    - mountPath: "/home/jenkins/.ssh"
      name: "volume-1"
      readOnly: false
      subPath: ""
    - mountPath: "/home/jenkins/agent"
      name: "workspace-volume"
      readOnly: false
    workingDir: "/home/jenkins/agent"
  nodeSelector:
    kubernetes.io/os: "linux"
  restartPolicy: "Never"
  volumes:
  - name: "volume-0"
    persistentVolumeClaim:
      claimName: "tools-claim-jiro-emfcompare"
      readOnly: true
  - name: "m2-secret-dir"
    secret:
      secretName: "m2-secret-dir"
  - emptyDir:
      medium: ""
    name: "volume-2"
  - configMap:
      name: "m2-dir"
    name: "m2-dir"
  - configMap:
      name: "known-hosts"
    name: "volume-1"
  - emptyDir:
      medium: ""
    name: "workspace-volume"
  - emptyDir:
      medium: ""
    name: "volume-4"
  - emptyDir:
      medium: ""
    name: "volume-3"

Building remotely on centos-7-mtjps (centos-7 jipp-migration migration) in workspace /home/jenkins/agent/workspace/publish-release/label/migration
[ssh-agent] Looking for ssh-agent implementation...
[ssh-agent]   Exec ssh-agent (binary ssh-agent on a remote machine)
$ ssh-agent
SSH_AUTH_SOCK=/tmp/ssh-WNpHGSYvVNdO/agent.57
SSH_AGENT_PID=59
[ssh-agent] Started.
Running ssh-add (command line suppressed)
Identity added: /home/jenkins/agent/workspace/publish-release/label/migration@tmp/private_key_10310537786184491918.key (/home/jenkins/agent/workspace/publish-release/label/migration@tmp/private_key_10310537786184491918.key)
[ssh-agent] Using credentials genie.emfcompare (ssh://genie.emfcompare@projects-storage.eclipse.org)
The recommended git tool is: NONE
No credentials specified
Cloning the remote Git repository
Cloning repository https://github.com/eclipse-emf-compare/emf-compare
 > git init /home/jenkins/agent/workspace/publish-release/label/migration # timeout=10
Fetching upstream changes from https://github.com/eclipse-emf-compare/emf-compare
 > git --version # timeout=10
 > git --version # 'git version 2.36.1'
 > git fetch --tags --force --progress -- https://github.com/eclipse-emf-compare/emf-compare +refs/heads/*:refs/remotes/origin/* # timeout=10
 > git config remote.origin.url https://github.com/eclipse-emf-compare/emf-compare # timeout=10
 > git config --add remote.origin.fetch +refs/heads/*:refs/remotes/origin/* # timeout=10
Avoid second fetch
Checking out Revision eca583fc34e24a3139a8cd93d901e6f546a324d0 (refs/remotes/origin/master)
 > git config core.sparsecheckout # timeout=10
 > git checkout -f eca583fc34e24a3139a8cd93d901e6f546a324d0 # timeout=10
Commit message: "Bump EMF Compare to 3.3.20"
 > git rev-list --no-walk eca583fc34e24a3139a8cd93d901e6f546a324d0 # timeout=10
[migration] $ /bin/sh -xe /tmp/jenkins17309002565259266954.sh
+ export SSH_ACCOUNT=genie.emfcompare@projects-storage.eclipse.org
+ SSH_ACCOUNT=genie.emfcompare@projects-storage.eclipse.org
+ ssh genie.emfcompare@projects-storage.eclipse.org
++ pwd
Pseudo-terminal will not be allocated because stdin is not a terminal.
Welcome to Ubuntu 21.10 (GNU/Linux 5.13.0-37-generic x86_64)

 * Documentation:  https://help.ubuntu.com
 * Management:     https://landscape.canonical.com
 * Support:        https://ubuntu.com/advantage

  System information as of Fri Nov 25 09:16:06 EST 2022

  System load:  1.96              Users logged in:       1
  Usage of /:   9.2% of 57.98GB   IPv4 address for ens2: 172.30.206.150
  Memory usage: 14%               IPv4 address for ens2: 198.41.30.204
  Swap usage:   0%                IPv4 address for ens3: 172.25.25.150
  Processes:    145

 * Strictly confined Kubernetes makes edge and IoT secure. Learn how MicroK8s
   just raised the bar for easy, resilient and secure K8s cluster deployment.

   https://ubuntu.com/engage/secure-kubernetes-at-the-edge

0 updates can be applied immediately.


The list of available updates is more than a week old.
To check for new updates run: sudo apt update
Your Ubuntu release is not supported anymore.
For upgrade information, please visit:
http://www.ubuntu.com/releaseendoflife

New release '22.04.1 LTS' available.
Run 'do-release-upgrade' to upgrade to it.


/home/jenkins/agent/workspace/publish-release/label/migration
Buildfile: /shared/modeling/tools/promotion/manage-composite.xml

add:

-call.operation:

-locate.framework.launcher:

-call.operation.indirectly:
     [java] Buildfile: /shared/modeling/tools/promotion/manage-composite.xml
     [java] 
     [java] add:
     [java] 
     [java] -call.operation:
     [java] 
     [java] -add.named:
     [java] 
     [java] -add:
     [java] BUILD SUCCESSFUL
     [java] 
     [java] BUILD SUCCESSFUL
     [java] Total time: 1 second

BUILD SUCCESSFUL
Total time: 7 seconds
$ ssh-agent -k
unset SSH_AUTH_SOCK;
unset SSH_AGENT_PID;
echo Agent pid 59 killed;
[ssh-agent] Stopped.
Finished: SUCCESS