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

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


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

Changes:


------------------------------------------
Started by upstream project "java-parent-project-v17-multi" build number 559
originally caused by:
 Started by upstream project "trigger-multi-v17" build number 559
 originally caused by:
  Started by upstream project "completed-nightly-v17" build number 336
  originally caused by:
   Started by upstream project "java-idp-plugin-totp-v2-nightly-java17" build number 121
   originally caused by:
    Started by upstream project "java-plugin-storage-jdbc-v2-nightly-java17" build number 535
    originally caused by:
     Started by upstream project "java-idp-plugin-metadatagen-v2-nightly-java17" build number 124
     originally caused by:
      Started by upstream project "java-idp-plugin-scripting-v2-nightly-java17" build number 1313
      originally caused by:
       Started by upstream project "java-idp-plugin-duo-v2-nightly-java17" build number 137
       originally caused by:
        Started by upstream project "java-idp-plugin-oidc-rp-v2-nightly-java17" build number 127
        originally caused by:
         Started by upstream project "java-idp-oidc-v4-nightly-java17" build number 1357
         originally caused by:
          Started by upstream project "java-idp-plugin-oidc-config-v2-nightly-java17" build number 132
          originally caused by:
           Started by upstream project "java-oidc-common-v3-nightly-java17" build number 1191
           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-v17-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-v17-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 1b23f14c44622ffb5a2bbf3d4bae15944a2fec6e (refs/remotes/origin/main)
 > git config core.sparsecheckout # timeout=10
 > git checkout -f 1b23f14c44622ffb5a2bbf3d4bae15944a2fec6e # timeout=10
Commit message: "Add property for the version of exec-maven-plugin"
 > git rev-list --no-walk 1b23f14c44622ffb5a2bbf3d4bae15944a2fec6e # 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