Build failed in Jenkins: xmlsectool-v3-multi » Amazon-11,Windows2016 #352
Shibboleth Jenkins
noreply at shibboleth.net
Tue Jan 21 21:19:36 EST 2020
See <http://127.0.0.1:1583/jenkins/job/xmlsectool-v3-multi/jdk=Amazon-11,label=Windows2016/352/display/redirect>
Changes:
------------------------------------------
Started by upstream project "xmlsectool-v3-multi" build number 352
originally caused by:
Started by upstream project "trigger-multi-v11" build number 192
originally caused by:
Started by upstream project "java-idp-oidc-nightly" build number 6
originally caused by:
Started by upstream project "java-identity-provider-v4-nightly" build number 448
originally caused by:
Started by upstream project "idwsfconsumer-v2-nightly" build number 16
originally caused by:
Started by upstream project "java-opensaml-v4-nightly" build number 447
originally caused by:
Started by upstream project "spring-extensions-v6-nightly" build number 840
originally caused by:
Started by upstream project "java-support-v8-nightly" build number 842
originally caused by:
Started by upstream project "java-parent-project-v11-nightly" build number 351
originally caused by:
Started by upstream project "trigger-nightly-v11" build number 348
originally caused by:
Started by timer
Running as SYSTEM
Building remotely on EC2 (WindowsServer2016) - WindowsServer2016 (i-01f870da70d023fda) (Windows2016) in workspace <http://127.0.0.1:1583/jenkins/job/xmlsectool-v3-multi/jdk=Amazon-11,label=Windows2016/ws/>
No credentials specified
Cloning the remote Git repository
Cloning repository http://git.shibboleth.net/git/xmlsectool
> git init <http://127.0.0.1:1583/jenkins/job/xmlsectool-v3-multi/jdk=Amazon-11,label=Windows2016/ws/> # timeout=10
Fetching upstream changes from http://git.shibboleth.net/git/xmlsectool
> git --version # timeout=10
> git fetch --tags --force --progress -- http://git.shibboleth.net/git/xmlsectool +refs/heads/*:refs/remotes/origin/* # timeout=10
> git config remote.origin.url http://git.shibboleth.net/git/xmlsectool # timeout=10
> git config --add remote.origin.fetch +refs/heads/*:refs/remotes/origin/* # timeout=10
> git config remote.origin.url http://git.shibboleth.net/git/xmlsectool # timeout=10
Fetching upstream changes from http://git.shibboleth.net/git/xmlsectool
> git fetch --tags --force --progress -- http://git.shibboleth.net/git/xmlsectool +refs/heads/*:refs/remotes/origin/* # timeout=10
Checking out Revision e22cc3fd3b4cded8a6f3f62dfd32591f2233df20 (refs/remotes/origin/master)
> git config core.sparsecheckout # timeout=10
> git checkout -f e22cc3fd3b4cded8a6f3f62dfd32591f2233df20 # timeout=10
Commit message: "JPAR-131 - Fix doclint issues"
> git rev-list --no-walk e22cc3fd3b4cded8a6f3f62dfd32591f2233df20 # timeout=10
[Windows2016] $ cmd.exe /C "\opt\maven_home\bin\mvn.cmd -Djdk=Amazon-11 -Dmatrix-combinations= -Dlabel=Windows2016 -B clean test -Prelease --update-snapshots --fail-at-end && exit %%ERRORLEVEL%%"
[INFO] Scanning for projects...
[INFO] Downloading from shib-snapshot: https://build.shibboleth.net/nexus/content/repositories/snapshots/net/shibboleth/parent/11.0.0-SNAPSHOT/maven-metadata.xml
[WARNING] Could not transfer metadata net.shibboleth:parent:11.0.0-SNAPSHOT/maven-metadata.xml from/to shib-snapshot (https://build.shibboleth.net/nexus/content/repositories/snapshots): Transfer failed for https://build.shibboleth.net/nexus/content/repositories/snapshots/net/shibboleth/parent/11.0.0-SNAPSHOT/maven-metadata.xml
[INFO] Downloading from shib-snapshot: https://build.shibboleth.net/nexus/content/repositories/snapshots/net/shibboleth/parent/11.0.0-SNAPSHOT/parent-11.0.0-SNAPSHOT.pom
[ERROR] [ERROR] Some problems were encountered while processing the POMs:
[FATAL] Non-resolvable parent POM for net.shibboleth.tool:xmlsectool:3.0.0-SNAPSHOT: Could not transfer artifact net.shibboleth:parent:pom:11.0.0-SNAPSHOT from/to shib-snapshot (https://build.shibboleth.net/nexus/content/repositories/snapshots): Transfer failed for https://build.shibboleth.net/nexus/content/repositories/snapshots/net/shibboleth/parent/11.0.0-SNAPSHOT/parent-11.0.0-SNAPSHOT.pom and 'parent.relativePath' points at wrong local POM @ line 7, column 13
@
[ERROR] The build could not read 1 project -> [Help 1]
[ERROR]
[ERROR] The project net.shibboleth.tool:xmlsectool:3.0.0-SNAPSHOT (<http://127.0.0.1:1583/jenkins/job/xmlsectool-v3-multi/jdk=Amazon-11,label=Windows2016/ws/pom.xml)> has 1 error
[ERROR] Non-resolvable parent POM for net.shibboleth.tool:xmlsectool:3.0.0-SNAPSHOT: Could not transfer artifact net.shibboleth:parent:pom:11.0.0-SNAPSHOT from/to shib-snapshot (https://build.shibboleth.net/nexus/content/repositories/snapshots): Transfer failed for https://build.shibboleth.net/nexus/content/repositories/snapshots/net/shibboleth/parent/11.0.0-SNAPSHOT/parent-11.0.0-SNAPSHOT.pom and 'parent.relativePath' points at wrong local POM @ line 7, column 13: Unexpected error: java.security.InvalidAlgorithmParameterException: the trustAnchors parameter must be non-empty -> [Help 2]
[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/ProjectBuildingException
[ERROR] [Help 2] http://cwiki.apache.org/confluence/display/MAVEN/UnresolvableModelException
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