cayenne-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Jenkins Server <jenk...@builds.apache.org>
Subject Build failed in Jenkins: cayenne-master » derby,latest1.8,Ubuntu #327
Date Wed, 27 Apr 2016 14:26:58 GMT
See <https://builds.apache.org/job/cayenne-master/cayenneTestConnection=derby,jdk=latest1.8,label=Ubuntu/327/changes>

Changes:

[s.kolbachev] limit bug

[s.kolbachev] CAY-2068 ObjectSelect limit bug

------------------------------------------
Started by upstream project "cayenne-master" build number 327
originally caused by:
 Started by an SCM change
[EnvInject] - Loading node environment variables.
Building remotely on jenkins-test-ad5 (jenkins-cloud-4GB cloud-slave Ubuntu ubuntu jenkins-cloud-8GB)
in workspace <https://builds.apache.org/job/cayenne-master/cayenneTestConnection=derby,jdk=latest1.8,label=Ubuntu/ws/>
Cloning the remote Git repository
Cloning repository https://git-wip-us.apache.org/repos/asf/cayenne.git
 > git init <https://builds.apache.org/job/cayenne-master/cayenneTestConnection=derby,jdk=latest1.8,label=Ubuntu/ws/>
# timeout=10
Fetching upstream changes from https://git-wip-us.apache.org/repos/asf/cayenne.git
 > git --version # timeout=10
 > git -c core.askpass=true fetch --tags --progress https://git-wip-us.apache.org/repos/asf/cayenne.git
+refs/heads/*:refs/remotes/origin/*
 > git config remote.origin.url https://git-wip-us.apache.org/repos/asf/cayenne.git # timeout=10
 > git config --add remote.origin.fetch +refs/heads/*:refs/remotes/origin/* # timeout=10
 > git config remote.origin.url https://git-wip-us.apache.org/repos/asf/cayenne.git # timeout=10
Fetching upstream changes from https://git-wip-us.apache.org/repos/asf/cayenne.git
 > git -c core.askpass=true fetch --tags --progress https://git-wip-us.apache.org/repos/asf/cayenne.git
+refs/heads/*:refs/remotes/origin/*
Checking out Revision d31b0146637733a21e37c079c254f3388c5ee17e (refs/remotes/origin/master)
 > git config core.sparsecheckout # timeout=10
 > git checkout -f d31b0146637733a21e37c079c254f3388c5ee17e
 > git rev-list 1223c54239d57f761ff9225ef4b9adcea687dd74 # timeout=10
Cleaning workspace
 > git rev-parse --verify HEAD # timeout=10
Resetting working tree
 > git reset --hard # timeout=10
 > git clean -fdx # timeout=10
Unpacking https://repo.maven.apache.org/maven2/org/apache/maven/apache-maven/3.0.4/apache-maven-3.0.4-bin.zip
to /home/jenkins/tools/maven/apache-maven-3.0.4 on jenkins-test-ad5
[Ubuntu] $ /home/jenkins/tools/maven/apache-maven-3.0.4/bin/mvn -Dlabel=Ubuntu -Djdk=latest1.8
-DcayenneTestConnection=derby -e clean verify
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=128m; support was removed
in 8.0
[INFO] Error stacktraces are turned on.
[ERROR] Error executing Maven.
org.apache.maven.settings.building.SettingsBuildingException: 1 problem was encountered while
building the effective settings
[FATAL] Non-parseable settings /home/jenkins/.m2/settings.xml: unexpected character in markup
% (position: START_TAG seen ...</username>\n     <password><%... @14:18)  @
/home/jenkins/.m2/settings.xml, line 14, column 18

	at org.apache.maven.settings.building.DefaultSettingsBuilder.build(DefaultSettingsBuilder.java:116)
	at org.apache.maven.cli.MavenCli.settings(MavenCli.java:725)
	at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:193)
	at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:498)
	at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
	at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
	at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
	at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
Build step 'Invoke top-level Maven targets' marked build as failure
Recording test results
ERROR: Step ‘Publish JUnit test result report’ failed: No test report files were found.
Configuration error?

Mime
View raw message