[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
[jpa-dev] Build failed in Jenkins: JPA API master build #104
|
See <https://ci.eclipse.org/jpa/job/jpa-api-master-build/104/display/redirect?page=changes>
Changes:
[Lukas Jungmann] update gh action build
[Lukas Jungmann] Update cprights
[Lukas Jungmann] #458: update orm.xsd/persistence.xsd to reflect annotation changes in 3.2
[Lukas Jungmann] update changelog
[Lukas Jungmann] update build plugins
[Lukas Jungmann] Update spec/src/main/asciidoc/appendixes.adoc
[Lukas Jungmann] Update spec/src/main/asciidoc/appendixes.adoc
[Lukas Jungmann] Update spec/src/main/asciidoc/appendixes.adoc
[Lukas Jungmann] add a note about timeout to the changelog
------------------------------------------
[...truncated 1.65 KB...]
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-jpa"
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-r8n26 (basic) in workspace <https://ci.eclipse.org/jpa/job/jpa-api-master-build/ws/>
[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-s5iCncB8YoPL/agent.49
SSH_AGENT_PID=51
[ssh-agent] Started.
Running ssh-add (command line suppressed)
Identity added: <https://ci.eclipse.org/jpa/job/jpa-api-master-build/ws/@tmp/private_key_8013729844044808018.key> (<https://ci.eclipse.org/jpa/job/jpa-api-master-build/ws/@tmp/private_key_8013729844044808018.key)>
[ssh-agent] Using credentials jpa-bot (GitHub bot SSH)
The recommended git tool is: NONE
using credential github-bot-ssh
Cloning the remote Git repository
Cloning repository git@xxxxxxxxxx:jakartaee/persistence.git
> git init <https://ci.eclipse.org/jpa/job/jpa-api-master-build/ws/> # timeout=10
Fetching upstream changes from git@xxxxxxxxxx:jakartaee/persistence.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 <https://ci.eclipse.org/jpa/job/jpa-api-master-build/ws/@tmp/jenkins-gitclient-ssh9904779326149240122.key>
Verifying host key using manually-configured host key entries
> git fetch --tags --force --progress -- git@xxxxxxxxxx:jakartaee/persistence.git +refs/heads/*:refs/remotes/origin/* # timeout=10
> git config remote.origin.url git@xxxxxxxxxx:jakartaee/persistence.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 8327bbeb3179b721da93dfb498c84d007aa4f925 (refs/remotes/origin/master)
> git config core.sparsecheckout # timeout=10
> git checkout -f 8327bbeb3179b721da93dfb498c84d007aa4f925 # timeout=10
Commit message: "add a note about timeout to the changelog"
> git rev-list --no-walk 2840bd86127dbef1bebf2d21ce37654f9fe3b301 # timeout=10
[jpa-api-master-build] $ /bin/sh -ex /tmp/jenkins4820510418632039302.sh
+ TOOLS_PREFIX=/opt/tools
+ MVN_HOME=/opt/tools/apache-maven/latest
+ PATH=/opt/tools/apache-maven/latest/bin:/opt/tools/java/openjdk/jdk-18/latest/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
+ gpg --batch --import ****
gpg: directory '/home/jenkins/.gnupg' created
gpg: keybox '/home/jenkins/.gnupg/pubring.kbx' created
gpg: key 252C7B8E879559E2: 1 signature not checked due to a missing key
gpg: /home/jenkins/.gnupg/trustdb.gpg: trustdb created
gpg: key 252C7B8E879559E2: public key "Eclipse Project for JPA <jpa-dev@xxxxxxxxxxx>" imported
gpg: To migrate 'secring.gpg', with each smartcard, run: gpg --card-status
gpg: key 252C7B8E879559E2: 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)
+ echo -e '5\ny\n'
+ gpg --batch --command-fd 0 --expert --edit-key 71EBF1CA4125B10AAB1E17CDB7DC526C17E3608B trust
Secret subkeys are available.
pub rsa4096/252C7B8E879559E2
created: 2018-10-03 expires: 2028-10-02 usage: SCEA
trust: unknown validity: unknown
ssb rsa4096/B7DC526C17E3608B
created: 2018-10-03 expires: 2028-10-02 usage: S
[ unknown] (1). Eclipse Project for JPA <jpa-dev@xxxxxxxxxxx>
pub rsa4096/252C7B8E879559E2
created: 2018-10-03 expires: 2028-10-02 usage: SCEA
trust: unknown validity: unknown
ssb rsa4096/B7DC526C17E3608B
created: 2018-10-03 expires: 2028-10-02 usage: S
[ unknown] (1). Eclipse Project for JPA <jpa-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/252C7B8E879559E2
created: 2018-10-03 expires: 2028-10-02 usage: SCEA
trust: ultimate validity: unknown
ssb rsa4096/B7DC526C17E3608B
created: 2018-10-03 expires: 2028-10-02 usage: S
[ unknown] (1). Eclipse Project for JPA <jpa-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 8814C0CC279AD91D93903DE8252C7B8E879559E2 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/252C7B8E879559E2
created: 2018-10-03 expires: 2028-10-02 usage: SCEA
trust: ultimate validity: ultimate
ssb rsa4096/B7DC526C17E3608B
created: 2018-10-03 expires: 2028-10-02 usage: S
[ultimate] (1). Eclipse Project for JPA <jpa-dev@xxxxxxxxxxx>
pub rsa4096/252C7B8E879559E2
created: 2018-10-03 expires: 2028-10-02 usage: SCEA
trust: ultimate validity: ultimate
ssb rsa4096/B7DC526C17E3608B
created: 2018-10-03 expires: 2028-10-02 usage: S
[ultimate] (1). Eclipse Project for JPA <jpa-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/252C7B8E879559E2
created: 2018-10-03 expires: 2028-10-02 usage: SCEA
trust: ultimate validity: ultimate
ssb rsa4096/B7DC526C17E3608B
created: 2018-10-03 expires: 2028-10-02 usage: S
[ultimate] (1). Eclipse Project for JPA <jpa-dev@xxxxxxxxxxx>
+ echo '-[ JPA API Build ]-----------------------------------------------------------'
-[ JPA API Build ]-----------------------------------------------------------
+ cd api
+ mvn -Pstaging,oss-release clean deploy
[INFO] Scanning for projects...
[INFO] Inspecting build with total of 1 modules...
[INFO] Installing Nexus Staging features:
[INFO] ... total of 1 executions of maven-deploy-plugin replaced with nexus-staging-maven-plugin
[INFO]
[INFO] ------------< jakarta.persistence:jakarta.persistence-api >-------------
[INFO] Building Jakarta Persistence API 3.2.1-SNAPSHOT
[INFO] from pom.xml
[INFO] --------------------------------[ jar ]---------------------------------
[INFO]
[INFO] --- clean:3.2.0:clean (default-clean) @ jakarta.persistence-api ---
[INFO]
[INFO] --- build-helper:3.5.0:timestamp-property (currentyear-property) @ jakarta.persistence-api ---
[INFO]
[INFO] --- enforcer:3.4.1:enforce (enforce-maven) @ jakarta.persistence-api ---
[INFO] Rule 0: org.apache.maven.enforcer.rules.version.RequireMavenVersion passed
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 12.396 s
[INFO] Finished at: 2024-02-28T16:02:45Z
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-enforcer-plugin:3.4.1:enforce (enforce-maven) on project jakarta.persistence-api:
[ERROR] Rule 1: org.apache.maven.enforcer.rules.version.RequireJavaVersion failed with message:
[ERROR] The build requires Java SE 21 or newer
[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 51 killed;
[ssh-agent] Stopped.
Skipped archiving because build is not successful
Recording test results
No test report files were found. Configuration error?
[Checks API] No suitable checks publisher found.
[Java CompilerJavaDocSpotBugs] Skipping execution of recorder since overall result is 'FAILURE'
