Started by user Radek Felcman Rebuilds build #66 Running as Radek Felcman Obtained etc/jenkins/release.groovy from git https://github.com/eclipse-ee4j/eclipselink.git [Pipeline] Start of Pipeline [Pipeline] echo [WARNING] label option is deprecated. To use a static pod template, use the 'inheritFrom' option. [Pipeline] podTemplate [Pipeline] { [Pipeline] node Still waiting to schedule task Waiting for next available executor Created Pod: kubernetes eclipselink/el-master-agent-pod-f51nc-0jdb8 Agent el-master-agent-pod-f51nc-0jdb8 is provisioned from template el-master-agent-pod-f51nc --- apiVersion: "v1" kind: "Pod" metadata: annotations: buildUrl: "http://jenkins-ui.eclipselink.svc.cluster.local/eclipselink/job/eclipselink-promote-3.0/67/" runUrl: "job/eclipselink-promote-3.0/67/" labels: jenkins: "slave" jenkins/label-digest: "3d62520732501e7b9e0bcd1206f227b6ebd57128" jenkins/label: "el-master-agent-pod" name: "el-master-agent-pod-f51nc-0jdb8" namespace: "eclipselink" spec: containers: - env: - name: "JENKINS_SECRET" value: "********" - name: "JENKINS_TUNNEL" value: "jenkins-discovery.eclipselink.svc.cluster.local:50000" - name: "JENKINS_AGENT_NAME" value: "el-master-agent-pod-f51nc-0jdb8" - name: "JENKINS_NAME" value: "el-master-agent-pod-f51nc-0jdb8" - name: "JENKINS_AGENT_WORKDIR" value: "/home/jenkins/agent" - name: "JENKINS_URL" value: "http://jenkins-ui.eclipselink.svc.cluster.local/eclipselink/" image: "docker.io/eclipsecbi/jiro-agent-basic:remoting-4.13.3" name: "jnlp" resources: limits: memory: "2Gi" cpu: "1" requests: memory: "2Gi" cpu: "500m" volumeMounts: - mountPath: "/home/jenkins/agent" name: "workspace-volume" readOnly: false - command: - "cat" image: "tkraus/el-build:2.0.2" name: "el-build" resources: limits: memory: "4Gi" cpu: "2" requests: memory: "4Gi" cpu: "1.5" tty: true volumeMounts: - mountPath: "/opt/tools" name: "tools" - mountPath: "/home/jenkins/.ssh" name: "volume-known-hosts" - mountPath: "/home/jenkins/.m2/settings.xml" name: "settings-xml" readOnly: true subPath: "settings.xml" - mountPath: "/home/jenkins/.m2/toolchains.xml" name: "toolchains-xml" readOnly: true subPath: "toolchains.xml" - mountPath: "/home/jenkins/.m2/settings-security.xml" name: "settings-security-xml" readOnly: true subPath: "settings-security.xml" - mountPath: "/home/jenkins/.m2/repository" name: "m2-repo" - mountPath: "/home/jenkins/agent" name: "workspace-volume" readOnly: false nodeSelector: kubernetes.io/os: "linux" restartPolicy: "Never" volumes: - name: "settings-security-xml" secret: items: - key: "settings-security.xml" path: "settings-security.xml" secretName: "m2-secret-dir" - configMap: items: - key: "toolchains.xml" path: "toolchains.xml" name: "m2-dir" name: "toolchains-xml" - emptyDir: {} name: "m2-repo" - name: "settings-xml" secret: items: - key: "settings.xml" path: "settings.xml" secretName: "m2-secret-dir" - emptyDir: medium: "" name: "workspace-volume" - name: "tools" persistentVolumeClaim: claimName: "tools-claim-jiro-eclipselink" - configMap: name: "known-hosts" name: "volume-known-hosts" Running on el-master-agent-pod-f51nc-0jdb8 in /home/jenkins/agent/workspace/eclipselink-promote-3.0 [Pipeline] { [Pipeline] stage [Pipeline] { (Declarative: Checkout SCM) [Pipeline] checkout The recommended git tool is: git No credentials specified Cloning the remote Git repository Cloning repository https://github.com/eclipse-ee4j/eclipselink.git > git init /home/jenkins/agent/workspace/eclipselink-promote-3.0 # timeout=10 Fetching upstream changes from https://github.com/eclipse-ee4j/eclipselink.git > git --version # timeout=10 > git --version # 'git version 2.20.1' > git fetch --tags --force --progress -- https://github.com/eclipse-ee4j/eclipselink.git +refs/heads/*:refs/remotes/origin/* # timeout=10 Avoid second fetch Checking out Revision c2faa619b828ce02faf84e4a3262f4c6b643c7fd (refs/remotes/origin/3.0) > git config remote.origin.url https://github.com/eclipse-ee4j/eclipselink.git # timeout=10 > git config --add remote.origin.fetch +refs/heads/*:refs/remotes/origin/* # timeout=10 > git rev-parse refs/remotes/origin/3.0^{commit} # timeout=10 > git config core.sparsecheckout # timeout=10 > git checkout -f c2faa619b828ce02faf84e4a3262f4c6b643c7fd # timeout=10 Commit message: "Promotion build script fix - version qualifier and buildType property (#1658)" First time build. Skipping changelog. [Pipeline] } [Pipeline] // stage [Pipeline] withEnv [Pipeline] { [Pipeline] stage [Pipeline] { (Declarative: Tool Install) [Pipeline] tool [Pipeline] envVarsForTool [Pipeline] tool [Pipeline] envVarsForTool [Pipeline] } [Pipeline] // stage [Pipeline] withEnv [Pipeline] { [Pipeline] stage [Pipeline] { (Init) [Pipeline] tool [Pipeline] envVarsForTool [Pipeline] tool [Pipeline] envVarsForTool [Pipeline] withEnv [Pipeline] { [Pipeline] container [Pipeline] { [Pipeline] git The recommended git tool is: git using credential github-bot-ssh Warning: JENKINS-30600: special launcher org.csanchez.jenkins.plugins.kubernetes.pipeline.ContainerExecDecorator$1@4b33ef49; decorates RemoteLauncher[hudson.remoting.Channel@d4e81d12:JNLP4-connect connection from 10.40.39.33/10.40.39.33:57794] will be ignored (a typical symptom is the Git executable not being run inside a designated container) Fetching changes from the remote Git repository Checking out Revision c2faa619b828ce02faf84e4a3262f4c6b643c7fd (refs/remotes/origin/3.0) > git rev-parse --resolve-git-dir /home/jenkins/agent/workspace/eclipselink-promote-3.0/.git # timeout=10 > git config remote.origin.url https://github.com/eclipse-ee4j/eclipselink.git # timeout=10 Fetching upstream changes from https://github.com/eclipse-ee4j/eclipselink.git > git --version # timeout=10 > git --version # 'git version 2.20.1' using GIT_SSH to set credentials GitHub bot (SSH) [INFO] Currently running in a labeled security context > /usr/bin/chcon --type=ssh_home_t /home/jenkins/agent/workspace/eclipselink-promote-3.0@tmp/jenkins-gitclient-ssh3369199119169703272.key Verifying host key using known hosts file You're using 'Known hosts file' strategy to verify ssh host keys, but your known_hosts file does not exist, please go to 'Manage Jenkins' -> 'Configure Global Security' -> 'Git Host Key Verification Configuration' and configure host key verification. > git fetch --tags --force --progress -- https://github.com/eclipse-ee4j/eclipselink.git +refs/heads/*:refs/remotes/origin/* # timeout=10 > git rev-parse refs/remotes/origin/3.0^{commit} # timeout=10 > git config core.sparsecheckout # timeout=10 > git checkout -f c2faa619b828ce02faf84e4a3262f4c6b643c7fd # timeout=10 > git branch -a -v --no-abbrev # timeout=10 > git checkout -b 3.0 c2faa619b828ce02faf84e4a3262f4c6b643c7fd # timeout=10 Commit message: "Promotion build script fix - version qualifier and buildType property (#1658)" [Pipeline] sh + mkdir /home/jenkins/.eclipselinktests [Pipeline] withCredentials Masking supported pattern matches of $KEYRING [Pipeline] { [Pipeline] sh + gpg --batch --import **** gpg: directory '/home/jenkins/.gnupg' created gpg: keybox '/home/jenkins/.gnupg/pubring.kbx' created gpg: /home/jenkins/.gnupg/trustdb.gpg: trustdb created gpg: key F956DAF8F18311D3: public key "Eclipselink Project " imported gpg: To migrate 'secring.gpg', with each smartcard, run: gpg --card-status gpg: key F956DAF8F18311D3: secret key imported gpg: Total number processed: 1 gpg: imported: 1 gpg: secret keys read: 1 gpg: secret keys imported: 1 ++ gpg --list-keys --with-colons ++ awk -F: '/fpr:/ {print $10}' ++ sort -u + for fpr in $(gpg --list-keys --with-colons | awk -F: '/fpr:/ {print $10}' | sort -u) + echo -e '5\ny\n' + gpg --batch --command-fd 0 --expert --edit-key AB11759F53250EEBD92E2F85836B571D384E2887 trust Secret subkeys are available. pub rsa4096/F956DAF8F18311D3 created: 2019-05-16 expires: 2024-05-14 usage: SCEA trust: unknown validity: unknown ssb rsa4096/836B571D384E2887 created: 2019-05-16 expires: 2024-05-14 usage: S [ unknown] (1). Eclipselink Project pub rsa4096/F956DAF8F18311D3 created: 2019-05-16 expires: 2024-05-14 usage: SCEA trust: unknown validity: unknown ssb rsa4096/836B571D384E2887 created: 2019-05-16 expires: 2024-05-14 usage: S [ unknown] (1). Eclipselink Project Please decide how far you trust this user to correctly verify other users' keys (by looking at passports, checking fingerprints from different sources, etc.) 1 = I don't know or won't say 2 = I do NOT trust 3 = I trust marginally 4 = I trust fully 5 = I trust ultimately m = back to the main menu pub rsa4096/F956DAF8F18311D3 created: 2019-05-16 expires: 2024-05-14 usage: SCEA trust: ultimate validity: unknown ssb rsa4096/836B571D384E2887 created: 2019-05-16 expires: 2024-05-14 usage: S [ unknown] (1). Eclipselink Project Please note that the shown key validity is not necessarily correct unless you restart the program. + for fpr in $(gpg --list-keys --with-colons | awk -F: '/fpr:/ {print $10}' | sort -u) + echo -e '5\ny\n' + gpg --batch --command-fd 0 --expert --edit-key D8216E428324480EEA98EE26F956DAF8F18311D3 trust Secret subkeys are available. gpg: checking the trustdb gpg: marginals needed: 3 completes needed: 1 trust model: pgp gpg: depth: 0 valid: 1 signed: 0 trust: 0-, 0q, 0n, 0m, 0f, 1u gpg: next trustdb check due at 2024-05-14 pub rsa4096/F956DAF8F18311D3 created: 2019-05-16 expires: 2024-05-14 usage: SCEA trust: ultimate validity: ultimate ssb rsa4096/836B571D384E2887 created: 2019-05-16 expires: 2024-05-14 usage: S [ultimate] (1). Eclipselink Project pub rsa4096/F956DAF8F18311D3 created: 2019-05-16 expires: 2024-05-14 usage: SCEA trust: ultimate validity: ultimate ssb rsa4096/836B571D384E2887 created: 2019-05-16 expires: 2024-05-14 usage: S [ultimate] (1). Eclipselink Project Please decide how far you trust this user to correctly verify other users' keys (by looking at passports, checking fingerprints from different sources, etc.) 1 = I don't know or won't say 2 = I do NOT trust 3 = I trust marginally 4 = I trust fully 5 = I trust ultimately m = back to the main menu pub rsa4096/F956DAF8F18311D3 created: 2019-05-16 expires: 2024-05-14 usage: SCEA trust: ultimate validity: ultimate ssb rsa4096/836B571D384E2887 created: 2019-05-16 expires: 2024-05-14 usage: S [ultimate] (1). Eclipselink Project [Pipeline] } [Pipeline] // withCredentials [Pipeline] sh + git config --global user.name 'EclipseLink Bot' + git config --global user.email eclipselink-bot@eclipse.org [Pipeline] } [Pipeline] // container [Pipeline] } [Pipeline] // withEnv [Pipeline] } [Pipeline] // stage [Pipeline] stage [Pipeline] { (Build and release EclipseLink) [Pipeline] tool [Pipeline] envVarsForTool [Pipeline] tool [Pipeline] envVarsForTool [Pipeline] withEnv [Pipeline] { [Pipeline] git The recommended git tool is: git using credential github-bot-ssh Fetching changes from the remote Git repository > git rev-parse --resolve-git-dir /home/jenkins/agent/workspace/eclipselink-promote-3.0/.git # timeout=10 > git config remote.origin.url https://github.com/eclipse-ee4j/eclipselink.git # timeout=10 Fetching upstream changes from https://github.com/eclipse-ee4j/eclipselink.git > git --version # timeout=10 Checking out Revision c2faa619b828ce02faf84e4a3262f4c6b643c7fd (refs/remotes/origin/3.0) Commit message: "Promotion build script fix - version qualifier and buildType property (#1658)" > git --version # 'git version 2.20.1' using GIT_SSH to set credentials GitHub bot (SSH) [INFO] Currently running in a labeled security context > /usr/bin/chcon --type=ssh_home_t /home/jenkins/agent/workspace/eclipselink-promote-3.0@tmp/jenkins-gitclient-ssh9914883924371679551.key Verifying host key using known hosts file You're using 'Known hosts file' strategy to verify ssh host keys, but your known_hosts file does not exist, please go to 'Manage Jenkins' -> 'Configure Global Security' -> 'Git Host Key Verification Configuration' and configure host key verification. > git fetch --tags --force --progress -- https://github.com/eclipse-ee4j/eclipselink.git +refs/heads/*:refs/remotes/origin/* # timeout=10 > git rev-parse refs/remotes/origin/3.0^{commit} # timeout=10 > git config core.sparsecheckout # timeout=10 > git checkout -f c2faa619b828ce02faf84e4a3262f4c6b643c7fd # timeout=10 > git branch -a -v --no-abbrev # timeout=10 > git branch -D 3.0 # timeout=10 > git checkout -b 3.0 c2faa619b828ce02faf84e4a3262f4c6b643c7fd # timeout=10 [Pipeline] sshagent [ssh-agent] Using credentials eclipse-eclipselink-bot (GitHub bot (SSH)) [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-lIWZzBZD6uXU/agent.326 SSH_AGENT_PID=328 Running ssh-add (command line suppressed) Identity added: /home/jenkins/agent/workspace/eclipselink-promote-3.0@tmp/private_key_3757064178392974335.key (/home/jenkins/agent/workspace/eclipselink-promote-3.0@tmp/private_key_3757064178392974335.key) [ssh-agent] Started. [Pipeline] { [Pipeline] container [Pipeline] { [Pipeline] sh + etc/jenkins/release.sh 3.0.3 3.0.4-SNAPSHOT false false false -[ EclipseLink Release ]----------------------------------------------------------- ECLIPSELINK Release Version: 3.0.3 ECLIPSELINK Next Version: 3.0.4 ECLIPSELINK Next Snapshot: 3.0.4-SNAPSHOT -[ Prepare branch ]------------------------------------------------------------- -[ Release tag cleanup ]-------------------------------------------------------- Error: 3.0.3 tag already exists [Pipeline] } [Pipeline] // container [Pipeline] } $ ssh-agent -k unset SSH_AUTH_SOCK; unset SSH_AGENT_PID; echo Agent pid 328 killed; [ssh-agent] Stopped. [Pipeline] // sshagent [Pipeline] } [Pipeline] // withEnv [Pipeline] } [Pipeline] // stage [Pipeline] stage [Pipeline] { (Declarative: Post Actions) [Pipeline] emailext Not sending mail to unregistered user noreply@github.com because your SCM claimed this was associated with a user ID ‘noreply' which your security realm does not recognize; you may need changes in your SCM plugin Sending email to: eclipselink-dev@eclipse.org dazeydev.3@gmail.com fyrewyld@gmail.com lukas.jungmann@oracle.com radek.felcman@oracle.com [Pipeline] } [Pipeline] // stage [Pipeline] } [Pipeline] // withEnv [Pipeline] } [Pipeline] // withEnv [Pipeline] } [Pipeline] // node [Pipeline] } [Pipeline] // podTemplate [Pipeline] End of Pipeline ERROR: script returned exit code 1 Finished: FAILURE