[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
[metro-dev] Build failed in Jenkins: Mimepull master build #43
|
See <https://ci.eclipse.org/metro/job/mimepull-master-build/43/display/redirect?page=changes>
Changes:
[David Matějček] Updated pom
[David Matějček] Updated .gitignore
[David Matějček] Moving to 1.11.0-SNAPSHOT and Java 17 as a minimum
[David Matějček] Mimepull requires JDK 17 to compile, but still can be used with JDK 11.
[Genie metro] [maven-release-plugin] prepare release 1.11.0
[Genie metro] [maven-release-plugin] prepare for next development iteration
------------------------------------------
[...truncated 1.91 KiB...]
cpu: "1000m"
tty: true
volumeMounts:
- mountPath: "/home/jenkins/.m2/mvnd"
name: "volume-5"
readOnly: false
- 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
nodeSelector:
kubernetes.io/os: "linux"
restartPolicy: "Never"
volumes:
- name: "volume-0"
persistentVolumeClaim:
claimName: "tools-claim-jiro-metro"
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"
- emptyDir:
medium: ""
name: "volume-5"
Building remotely on basic-gzxq7 (basic basic-ubuntu) in workspace <https://ci.eclipse.org/metro/job/mimepull-master-build/ws/>
[ssh-agent] Looking for ssh-agent implementation...
$ ssh-agent
SSH_AUTH_SOCK=/tmp/ssh-BCJK04cHAbx0/agent.45
SSH_AGENT_PID=46
[ssh-agent] Started.
Running ssh-add (command line suppressed)
Identity added: <https://ci.eclipse.org/metro/job/mimepull-master-build/ws/@tmp/private_key_12342866174767151685.key> (<https://ci.eclipse.org/metro/job/mimepull-master-build/ws/@tmp/private_key_12342866174767151685.key)>
[ssh-agent] Using credentials eclipse-metro-bot (GitHub bot SSH)
The recommended git tool is: NONE
No credentials specified
Cloning the remote Git repository
Cloning repository https://github.com/eclipse-ee4j/metro-mimepull.git
> git init <https://ci.eclipse.org/metro/job/mimepull-master-build/ws/> # timeout=10
Fetching upstream changes from https://github.com/eclipse-ee4j/metro-mimepull.git
> git --version # timeout=10
> git --version # 'git version 2.54.0'
> git fetch --tags --force --progress -- https://github.com/eclipse-ee4j/metro-mimepull.git +refs/heads/*:refs/remotes/origin/* # timeout=10
> git config remote.origin.url https://github.com/eclipse-ee4j/metro-mimepull.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/master^{commit} # timeout=10
Checking out Revision 7624bad156a07ac08fe1df090c56890342d35d1c (refs/remotes/origin/master)
> git config core.sparsecheckout # timeout=10
> git checkout -f 7624bad156a07ac08fe1df090c56890342d35d1c # timeout=10
Commit message: "Merge pull request #71 from eclipse-ee4j/RELEASE_1110"
> git rev-list --no-walk e08ea5b4789599625ccfc1cb6b64415e766680cf # timeout=10
[mimepull-master-build] $ /bin/sh -ex /tmp/jenkins2332165624476164440.sh
+ TOOLS_PREFIX=/opt/tools
+ JAVA_PREFIX=/opt/tools/java/openjdk
+ MVN_HOME=/opt/tools/apache-maven/latest
+ JAVA_HOME=/opt/tools/java/openjdk/jdk-11/latest
+ PATH=/opt/tools/apache-maven/latest/bin:/opt/tools/java/openjdk/jdk-11/latest/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
+ echo '-[ GPG Initialization ]---------------------------------------------------------'
-[ GPG Initialization ]---------------------------------------------------------
+ gpg --batch --import ****
gpg: directory '/home/jenkins/.gnupg' created
gpg: keybox '/home/jenkins/.gnupg/pubring.kbx' created
gpg: key A7C6AFD280CA7CF0: 1 signature not checked due to a missing key
gpg: /home/jenkins/.gnupg/trustdb.gpg: trustdb created
gpg: key A7C6AFD280CA7CF0: public key "Eclipse Metro <metro-dev@xxxxxxxxxxx>" imported
gpg: To migrate 'secring.gpg', with each smartcard, run: gpg --card-status
gpg: key A7C6AFD280CA7CF0: secret key imported
gpg: Total number processed: 1
gpg: imported: 1
gpg: secret keys read: 1
gpg: secret keys imported: 1
gpg: no ultimately trusted keys found
++ 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)
+ gpg --batch --command-fd 0 --expert --edit-key B506C29E4B7EF88CE0F0E6D3A7C6AFD280CA7CF0 trust
+ echo -e '5\ny\n'
Secret subkeys are available.
pub rsa4096/A7C6AFD280CA7CF0
created: 2018-10-03 expires: 2028-10-02 usage: SCEA
trust: unknown validity: unknown
ssb rsa4096/B6D3FC494798E478
created: 2018-10-03 expires: 2028-10-02 usage: S
[ unknown] (1). Eclipse Metro <metro-dev@xxxxxxxxxxx>
pub rsa4096/A7C6AFD280CA7CF0
created: 2018-10-03 expires: 2028-10-02 usage: SCEA
trust: unknown validity: unknown
ssb rsa4096/B6D3FC494798E478
created: 2018-10-03 expires: 2028-10-02 usage: S
[ unknown] (1). Eclipse Metro <metro-dev@xxxxxxxxxxx>
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/A7C6AFD280CA7CF0
created: 2018-10-03 expires: 2028-10-02 usage: SCEA
trust: ultimate validity: unknown
ssb rsa4096/B6D3FC494798E478
created: 2018-10-03 expires: 2028-10-02 usage: S
[ unknown] (1). Eclipse Metro <metro-dev@xxxxxxxxxxx>
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 E725C3877939E8FFEA7E3C44B6D3FC494798E478 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 2028-10-02
pub rsa4096/A7C6AFD280CA7CF0
created: 2018-10-03 expires: 2028-10-02 usage: SCEA
trust: ultimate validity: ultimate
ssb rsa4096/B6D3FC494798E478
created: 2018-10-03 expires: 2028-10-02 usage: S
[ultimate] (1). Eclipse Metro <metro-dev@xxxxxxxxxxx>
pub rsa4096/A7C6AFD280CA7CF0
created: 2018-10-03 expires: 2028-10-02 usage: SCEA
trust: ultimate validity: ultimate
ssb rsa4096/B6D3FC494798E478
created: 2018-10-03 expires: 2028-10-02 usage: S
[ultimate] (1). Eclipse Metro <metro-dev@xxxxxxxxxxx>
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/A7C6AFD280CA7CF0
created: 2018-10-03 expires: 2028-10-02 usage: SCEA
trust: ultimate validity: ultimate
ssb rsa4096/B6D3FC494798E478
created: 2018-10-03 expires: 2028-10-02 usage: S
[ultimate] (1). Eclipse Metro <metro-dev@xxxxxxxxxxx>
+ echo '-[ Mimepull Build ]-------------------------------------------------------------'
-[ Mimepull Build ]-------------------------------------------------------------
+ mvn -U -C -B clean install spotbugs:spotbugs deploy -Pstaging -Psnapshots -Pcoverage -Poss-release
[INFO] Scanning for projects...
[INFO] Inspecting build with total of 1 modules
[INFO] Installing Central Publishing features
[WARNING] The requested profile "staging" could not be activated because it does not exist.
[INFO]
[INFO] --------------------< org.jvnet.mimepull:mimepull >---------------------
[INFO] Building MIME Streaming Extension 1.11.1-SNAPSHOT
[INFO] from pom.xml
[INFO] --------------------------------[ jar ]---------------------------------
[INFO]
[INFO] --- clean:3.2.0:clean (default-clean) @ mimepull ---
[INFO]
[INFO] --- enforcer:3.6.2:enforce (enforce-maven) @ mimepull ---
[INFO] Rule 1: org.apache.maven.enforcer.rules.version.RequireMavenVersion passed
[INFO] Rule 2: org.apache.maven.enforcer.rules.dependency.DependencyConvergence passed
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 8.784 s
[INFO] Finished at: 2026-05-02T16:52:28Z
[INFO] ------------------------------------------------------------------------
[WARNING] The requested profile "staging" could not be activated because it does not exist.
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-enforcer-plugin:3.6.2:enforce (enforce-maven) on project mimepull:
[ERROR] Rule 0: org.apache.maven.enforcer.rules.version.RequireJavaVersion failed with message:
[ERROR] Detected JDK /opt/tools/java/openjdk/jdk-11/11.0.2+9 is version 11.0.2 which is not in the allowed range [17,).
[ERROR] -> [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/MojoExecutionException
Build step 'Execute shell' marked build as failure
$ ssh-agent -k
unset SSH_AUTH_SOCK;
unset SSH_AGENT_PID;
echo Agent pid 46 killed;
[ssh-agent] Stopped.
Recording test results
ERROR: Step ‘Publish JUnit test result report’ failed: No test report files were found. Configuration error?
[analysis] Skipping execution of recorder since overall result is 'FAILURE'