Started by user Frederic Gurr Rebuilds build #95 Running as Frederic Gurr Agent basic-l4nf0 is provisioned from template basic --- apiVersion: "v1" kind: "Pod" metadata: annotations: {} labels: jenkins: "slave" jenkins/label: "" name: "basic-l4nf0" spec: containers: - env: - name: "JENKINS_SECRET" value: "********" - name: "JENKINS_TUNNEL" value: "jenkins-discovery.milo.svc.cluster.local:50000" - name: "JENKINS_AGENT_NAME" value: "basic-l4nf0" - 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: "basic-l4nf0" - name: "JENKINS_AGENT_WORKDIR" value: "/home/jenkins/agent" - name: "JENKINS_URL" value: "http://jenkins-ui.milo.svc.cluster.local/milo/" image: "docker.io/eclipsecbi/jiro-agent-basic:remoting-4.5" imagePullPolicy: "Always" name: "jnlp" resources: limits: memory: "4096Mi" cpu: "2000m" requests: memory: "4096Mi" cpu: "1000m" securityContext: privileged: false 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 - mountPath: "/home/jenkins/agent" name: "workspace-volume" readOnly: false workingDir: "/home/jenkins/agent" nodeSelector: beta.kubernetes.io/os: "linux" restartPolicy: "Never" securityContext: {} volumes: - name: "volume-0" persistentVolumeClaim: claimName: "tools-claim-jiro-milo" 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 basic-l4nf0 in workspace /home/jenkins/agent/workspace/Milo_Release [WS-CLEANUP] Deleting project workspace... [WS-CLEANUP] Deferred wipeout is used... [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-LPFlFAJtoUoV/agent.59 SSH_AGENT_PID=61 [ssh-agent] Started. Running ssh-add (command line suppressed) Identity added: /home/jenkins/agent/workspace/Milo_Release@tmp/private_key_15135971123655203445.key (/home/jenkins/agent/workspace/Milo_Release@tmp/private_key_15135971123655203445.key) [ssh-agent] Using credentials eclipse-milo-bot (GitHub bot (SSH)) The recommended git tool is: NONE using credential github-bot-ssh Cloning the remote Git repository Cloning repository ssh://git@github.com/eclipse/milo.git > git init /home/jenkins/agent/workspace/Milo_Release # timeout=10 Fetching upstream changes from ssh://git@github.com/eclipse/milo.git > git --version # timeout=10 > git --version # 'git version 2.26.2' using GIT_SSH to set credentials GitHub bot (SSH) > git fetch --tags --force --progress -- ssh://git@github.com/eclipse/milo.git +refs/heads/*:refs/remotes/origin/* # timeout=10 > git config remote.origin.url ssh://git@github.com/eclipse/milo.git # timeout=10 > git config --add remote.origin.fetch +refs/heads/*:refs/remotes/origin/* # timeout=10 Avoid second fetch > git rev-parse refs/remotes/origin/release/0.5.4^{commit} # timeout=10 Checking out Revision 74b6196dd9e8049806d7aa7aafa6d8bc37bb4fc4 (refs/remotes/origin/release/0.5.4) > git config core.sparsecheckout # timeout=10 > git checkout -f 74b6196dd9e8049806d7aa7aafa6d8bc37bb4fc4 # timeout=10 > git branch -a -v --no-abbrev # timeout=10 > git checkout -b release/0.5.4 74b6196dd9e8049806d7aa7aafa6d8bc37bb4fc4 # timeout=10 Commit message: "[maven-release-plugin] prepare release v0.5.4" > git rev-list --no-walk 31974c8edd35a3f494989e54de1625c4607cd517 # timeout=10 [Milo_Release] $ /bin/sh -xe /tmp/jenkins15898803912262520393.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 207D2B80C80462B0: public key "Eclipse Milo Project " imported gpg: To migrate 'secring.gpg', with each smartcard, run: gpg --card-status gpg: key 207D2B80C80462B0: 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 + echo -e '5\ny\n' + gpg --batch --command-fd 0 --expert --edit-key 1BA64A87761C1DD26C1CC828207D2B80C80462B0 trust Secret subkeys are available. pub rsa4096/207D2B80C80462B0 created: 2016-07-19 expires: 2021-07-18 usage: SC trust: unknown validity: unknown ssb rsa4096/00DD9B054294B3E8 created: 2016-07-19 expires: 2021-07-18 usage: S [ unknown] (1). Eclipse Milo Project pub rsa4096/207D2B80C80462B0 created: 2016-07-19 expires: 2021-07-18 usage: SC trust: unknown validity: unknown ssb rsa4096/00DD9B054294B3E8 created: 2016-07-19 expires: 2021-07-18 usage: S [ unknown] (1). Eclipse Milo 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/207D2B80C80462B0 created: 2016-07-19 expires: 2021-07-18 usage: SC trust: ultimate validity: unknown ssb rsa4096/00DD9B054294B3E8 created: 2016-07-19 expires: 2021-07-18 usage: S [ unknown] (1). Eclipse Milo Project Please note that the shown key validity is not necessarily correct unless you restart the program. + echo -e '5\ny\n' + gpg --batch --command-fd 0 --expert --edit-key 66EF282B0C98D31E9F0DC14D00DD9B054294B3E8 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 2021-07-18 pub rsa4096/207D2B80C80462B0 created: 2016-07-19 expires: 2021-07-18 usage: SC trust: ultimate validity: ultimate ssb rsa4096/00DD9B054294B3E8 created: 2016-07-19 expires: 2021-07-18 usage: S [ultimate] (1). Eclipse Milo Project pub rsa4096/207D2B80C80462B0 created: 2016-07-19 expires: 2021-07-18 usage: SC trust: ultimate validity: ultimate ssb rsa4096/00DD9B054294B3E8 created: 2016-07-19 expires: 2021-07-18 usage: S [ultimate] (1). Eclipse Milo 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/207D2B80C80462B0 created: 2016-07-19 expires: 2021-07-18 usage: SC trust: ultimate validity: ultimate ssb rsa4096/00DD9B054294B3E8 created: 2016-07-19 expires: 2021-07-18 usage: S [ultimate] (1). Eclipse Milo Project [Milo_Release] $ /bin/sh -xe /tmp/jenkins15570269827988078534.sh + git config user.email milo-bot@eclipse.org + git config user.name eclipse-milo-bot [Milo_Release] $ /opt/tools/apache-maven/latest/bin/mvn -f pom.xml -DdevelopmentVersion=0.5.5-SNAPSHOT -DreleaseVersion=0.5.4 -DreleaseBranch=release/0.5.4 -DdevelopmentVersion=0.5.5-SNAPSHOT -DreleaseVersion=0.5.4 -DtagNameFormat=v@{version} -Dmaven.repo.local=/home/jenkins/agent/workspace/Milo_Release/.repository release:clean release:prepare release:perform -B Apache Maven 3.6.3 (cecedd343002696d0abb50b32b541b8a6ba2883f) Maven home: /opt/tools/apache-maven/latest Java version: 1.8.0_202, vendor: Oracle Corporation, runtime: /opt/tools/java/oracle/jdk-8/1.8.0_202/jre Default locale: en_US, platform encoding: UTF-8 OS name: "linux", version: "5.9.16-200.fc33.x86_64", arch: "amd64", family: "unix" [INFO] Scanning for projects... [INFO] ------------------------------------------------------------------------ [INFO] Reactor Build Order: [INFO] [INFO] Eclipse Milo Build Tools [jar] [INFO] Eclipse Milo - OPC UA (IEC 62541) [pom] [INFO] opc-ua-stack [pom] [INFO] stack-core [jar] [INFO] stack-client [jar] [INFO] opc-ua-sdk [pom] [INFO] sdk-core [jar] [INFO] sdk-client [jar] [INFO] bsd-core [jar] [INFO] bsd-parser [jar] [INFO] dictionary-reader [jar] [INFO] stack-server [jar] [INFO] bsd-generator [jar] [INFO] sdk-server [jar] [INFO] dictionary-manager [jar] [INFO] milo-examples [pom] [INFO] server-examples [jar] [INFO] client-examples [jar] [INFO] bsd-parser-gson [jar] [INFO] stack-tests [jar] [INFO] sdk-tests [jar] [INFO] integration-tests [jar] [INFO] [INFO] -----------------------< org.eclipse.milo:milo >------------------------ [INFO] Building Eclipse Milo - OPC UA (IEC 62541) 0.5.4 [1/22] [INFO] --------------------------------[ pom ]--------------------------------- [INFO] [INFO] --- maven-release-plugin:3.0.0-M1:clean (default-cli) @ milo --- [INFO] phase cleanup [INFO] Cleaning up after release... [INFO] [INFO] --- maven-release-plugin:3.0.0-M1:prepare (default-cli) @ milo --- [INFO] phase verify-release-configuration [INFO] starting prepare goal, composed of 17 phases: check-poms, scm-check-modifications, check-dependency-snapshots, create-backup-poms, map-release-versions, input-variables, map-development-versions, rewrite-poms-for-release, generate-release-poms, run-preparation-goals, scm-commit-release, scm-tag, rewrite-poms-for-development, remove-release-poms, run-completion-goals, scm-commit-development, end-release [INFO] [prepare] 1/17 check-poms [INFO] ------------------------------------------------------------------------ [INFO] Reactor Summary for Eclipse Milo - OPC UA (IEC 62541) 0.5.4: [INFO] [INFO] Eclipse Milo Build Tools ........................... SKIPPED [INFO] Eclipse Milo - OPC UA (IEC 62541) .................. FAILURE [ 9.454 s] [INFO] opc-ua-stack ....................................... SKIPPED [INFO] stack-core ......................................... SKIPPED [INFO] stack-client ....................................... SKIPPED [INFO] opc-ua-sdk ......................................... SKIPPED [INFO] sdk-core ........................................... SKIPPED [INFO] sdk-client ......................................... SKIPPED [INFO] bsd-core ........................................... SKIPPED [INFO] bsd-parser ......................................... SKIPPED [INFO] dictionary-reader .................................. SKIPPED [INFO] stack-server ....................................... SKIPPED [INFO] bsd-generator ...................................... SKIPPED [INFO] sdk-server ......................................... SKIPPED [INFO] dictionary-manager ................................. SKIPPED [INFO] milo-examples ...................................... SKIPPED [INFO] server-examples .................................... SKIPPED [INFO] client-examples .................................... SKIPPED [INFO] bsd-parser-gson .................................... SKIPPED [INFO] stack-tests ........................................ SKIPPED [INFO] sdk-tests .......................................... SKIPPED [INFO] integration-tests .................................. SKIPPED [INFO] ------------------------------------------------------------------------ [INFO] BUILD FAILURE [INFO] ------------------------------------------------------------------------ [INFO] Total time: 14.464 s [INFO] Finished at: 2021-02-18T21:53:59Z [INFO] ------------------------------------------------------------------------ [ERROR] Failed to execute goal org.apache.maven.plugins:maven-release-plugin:3.0.0-M1:prepare (default-cli) on project milo: You don't have a SNAPSHOT project in the reactor projects list. -> [Help 1] [ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. [ERROR] Re-run Maven using the -X switch to enable full debug logging. [ERROR] [ERROR] For more information about the errors and possible solutions, please read the following articles: [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException [ERROR] [ERROR] After correcting the problems, you can resume the build with the command [ERROR] mvn -rf :milo Build step 'Invoke top-level Maven targets' marked build as failure $ ssh-agent -k unset SSH_AUTH_SOCK; unset SSH_AGENT_PID; echo Agent pid 61 killed; [ssh-agent] Stopped. Finished: FAILURE