Build failed in Jenkins: java-parent-project-v11-multi » OpenJDK-21,Windows2022 #1362

Shibboleth Jenkins noreply at shibboleth.net
Sat Nov 11 05:07:43 UTC 2023


See <http://127.0.0.1:1583/jenkins/job/java-parent-project-v11-multi/jdk=OpenJDK-21,label=Windows2022/1362/display/redirect>

Changes:


------------------------------------------
Started by upstream project "java-parent-project-v11-multi" build number 1362
originally caused by:
 Started by upstream project "trigger-multi-v11" build number 1351
 originally caused by:
  Started by upstream project "completed-nightly-v11" build number 463
  originally caused by:
   Started by upstream project "java-idp-plugin-totp-v1-nightly-java11" build number 1279
   originally caused by:
    Started by upstream project "java-plugin-storage-jdbc-v1-nightly-java11" build number 124
    originally caused by:
     Started by upstream project "java-idp-plugin-scripting-v1-nightly-java11" build number 125
     originally caused by:
      Started by upstream project "java-idp-plugin-duo-v1-nightly-java11" build number 680
      originally caused by:
       Started by upstream project "java-idp-plugin-oidc-rp-v1-nightly-java11" build number 268
       originally caused by:
        Started by upstream project "java-idp-oidc-v3-nightly-java11" build number 123
        originally caused by:
         Started by upstream project "java-oidc-common-v2-nightly-java11" build number 123
         originally caused by:
          Started by upstream project "java-idp-plugin-oidc-config-v1-nightly-java11" build number 270
          originally caused by:
           Started by upstream project "java-idp-testbed-v4-nightly" build number 1328
           originally caused by:
            (deeply nested causes)
Running as SYSTEM
[EnvInject] - Loading node environment variables.
Building remotely on EC2 (ec2-I2) - WindowsServer2022 (i-0c56b10a116e8459e) (Windows2022) in workspace <http://127.0.0.1:1583/jenkins/job/java-parent-project-v11-multi/jdk=OpenJDK-21,label=Windows2022/ws/>
The recommended git tool is: NONE
No credentials specified
Cloning the remote Git repository
Cloning repository https://git.shibboleth.net/git/java-parent-project
 > git init <http://127.0.0.1:1583/jenkins/job/java-parent-project-v11-multi/jdk=OpenJDK-21,label=Windows2022/ws/> # timeout=10
Fetching upstream changes from https://git.shibboleth.net/git/java-parent-project
 > git --version # timeout=10
 > git --version # 'git version 2.42.0.windows.2'
 > git fetch --tags --force --progress -- https://git.shibboleth.net/git/java-parent-project +refs/heads/*:refs/remotes/origin/* # timeout=10
 > git config remote.origin.url https://git.shibboleth.net/git/java-parent-project # timeout=10
 > git config --add remote.origin.fetch +refs/heads/*:refs/remotes/origin/* # timeout=10
Avoid second fetch
Checking out Revision c7a57d55a317e0d9f41ec2cf082606d465cf1d90 (refs/remotes/origin/maint-11)
 > git config core.sparsecheckout # timeout=10
 > git checkout -f c7a57d55a317e0d9f41ec2cf082606d465cf1d90 # timeout=10
Commit message: "Align release profile to match main branch."
 > git rev-list --no-walk c7a57d55a317e0d9f41ec2cf082606d465cf1d90 # timeout=10
[Windows2022] $ cmd.exe /C "\opt\maven_home\bin\mvn.cmd -V-version && exit %%ERRORLEVEL%%"
The JAVA_HOME environment variable is not defined correctly, 
this environment variable is needed to run this program. 
Build step 'Invoke top-level Maven targets' marked build as failure
TestNG Reports Processing: START
Looking for TestNG results report in workspace using pattern: **/target/surefire-reports/testng-results.xml
Did not find any matching files.


More information about the commits mailing list