Build failed in Jenkins: java-metadata-aggregator-0.10-multi » Amazon-11,Windows2016 #514

Shibboleth Jenkins noreply at shibboleth.net
Wed Aug 25 03:11:55 UTC 2021


See <http://127.0.0.1:1583/jenkins/job/java-metadata-aggregator-0.10-multi/jdk=Amazon-11,label=Windows2016/514/display/redirect?page=changes>

Changes:

[Rod Widdowson] Stop using the GraalVM nashorn engine and use the JDK one

[Ian Young] MDA-262 - Move Maven parent project to root


------------------------------------------
Started by upstream project "java-metadata-aggregator-0.10-multi" build number 514
originally caused by:
 Started by upstream project "trigger-multi-v11" build number 501
 originally caused by:
  Started by upstream project "java-idp-plugin-totp-v1-nightly" build number 430
  originally caused by:
   Started by upstream project "java-idp-plugin-scripting-v1-nightly" build number 457
   originally caused by:
    Started by upstream project "java-idp-oidc-v2-nightly" build number 497
    originally caused by:
     Started by upstream project "java-oidc-common-nightly" build number 323
     originally caused by:
      Started by upstream project "java-idp-testbed-nightly" build number 479
      originally caused by:
       Started by upstream project "java-identity-provider-v4.1-nightly" build number 32
       originally caused by:
        Started by upstream project "java-identity-provider-v4-nightly" build number 493
        originally caused by:
         Started by upstream project "java-idwsfconsumer-v2-nightly" build number 481
         originally caused by:
          Started by upstream project "java-opensaml-v4-nightly" build number 483
          originally caused by:
           Started by upstream project "spring-extensions-v6-nightly" build number 475
           originally caused by:
            (deeply nested causes)
Running as SYSTEM
Building remotely on EC2 (I2) - WindowsServer2016 (i-04d4c7e2d8f01a787) (Windows2016) in workspace <http://127.0.0.1:1583/jenkins/job/java-metadata-aggregator-0.10-multi/jdk=Amazon-11,label=Windows2016/ws/>
The recommended git tool is: NONE
No credentials specified
Cloning the remote Git repository
Cloning repository https://git.shibboleth.net/git/java-metadata-aggregator
 > git init <http://127.0.0.1:1583/jenkins/job/java-metadata-aggregator-0.10-multi/jdk=Amazon-11,label=Windows2016/ws/> # timeout=10
Fetching upstream changes from https://git.shibboleth.net/git/java-metadata-aggregator
 > git --version # timeout=10
 > git --version # 'git version 2.25.0.windows.1'
 > git fetch --tags --force --progress -- https://git.shibboleth.net/git/java-metadata-aggregator +refs/heads/*:refs/remotes/origin/* # timeout=10
 > git config remote.origin.url https://git.shibboleth.net/git/java-metadata-aggregator # timeout=10
 > git config --add remote.origin.fetch +refs/heads/*:refs/remotes/origin/* # timeout=10
Avoid second fetch
Checking out Revision 346c80c3664fad7d81d44fe3e8d3068823f42ce6 (refs/remotes/origin/main)
 > git config core.sparsecheckout # timeout=10
 > git checkout -f 346c80c3664fad7d81d44fe3e8d3068823f42ce6 # timeout=10
Commit message: "MDA-262 - Move Maven parent project to root"
 > git rev-list --no-walk 3f8c73dcd2803d800b4d3b32cb43726f86096c76 # timeout=10
[Windows2016] $ cmd.exe /C "\opt\maven_home\bin\mvn.cmd -f aggregator-parent/pom.xml -Djdk=Amazon-11 -Dmatrix-combinations= -Dlabel=Windows2016 -V -B clean test -Prelease --update-snapshots --fail-at-end && exit %%ERRORLEVEL%%"
POM file "aggregator-parent/pom.xml" specified the -f/--file command-line argument does not exist 
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