You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cloudstack.apache.org by Apache Jenkins Server <je...@builds.apache.org> on 2013/04/22 20:20:47 UTC

Build failed in Jenkins: cloudstack-marvin-41 #262

See <https://builds.apache.org/job/cloudstack-marvin-41/262/changes>

Changes:

[chipchilders] Moving default release build dir to /tmp

[chipchilders] Removing unused keyid variable, in favor of consolidating it into the certid var for the release prep build script

[chipchilders] Adding svn upload to dev dist dir to release build script

[chipchilders] Fixing build script variable comparisons to include quotes

[chipchilders] More build script fixes

[chipchilders] Fixing getopts for build script

[chipchilders] Correcting getopts option-string

[chipchilders] Fixing path error in release dist checkin script

[chipchilders] Updating pom.xml version numbers for release 4.1.0

[chipchilders] Updating pom.xml version numbers for release 4.1.1-SNAPSHOT

[chipchilders] Adding a version folder location for the svn dev dist commit

[chipchilders] Adding additional profiles and properties to mvn version scripts

[chipchilders] Revert "Updating pom.xml version numbers for release 4.1.1-SNAPSHOT"

[chipchilders] Revert "Updating pom.xml version numbers for release 4.1.0"

[chipchilders] Updating pom.xml version numbers for release 4.1.0

[chipchilders] Updating pom.xml version numbers for release 4.1.1-SNAPSHOT

[chipchilders] Fixing version scripts to deal with tools/apidoc/pom.xml

[chipchilders] Revert "Updating pom.xml version numbers for release 4.1.1-SNAPSHOT"

[chipchilders] Revert "Updating pom.xml version numbers for release 4.1.0"

[chipchilders] Updating pom.xml version numbers for release 4.1.0

[chipchilders] Updating pom.xml version numbers for release 4.1.1-SNAPSHOT

------------------------------------------
Started by upstream project "cloudstack-build-41" build number 381
originally caused by: 
 Started by an SCM change
 Started by an SCM change
 Started by an SCM change
 Started by an SCM change
 Started by an SCM change
 Started by an SCM change
 Started by an SCM change
 Started by an SCM change
 Started by an SCM change
 Started by an SCM change
 Started by an SCM change
 Started by an SCM change
 Started by an SCM change
 Started by an SCM change
 Started by an SCM change
 Started by an SCM change
 Started by an SCM change
 Started by an SCM change
 Started by an SCM change
 Started by an SCM change
 Started by an SCM change
 Started by an SCM change
 Started by an SCM change
 Started by an SCM change
 Started by an SCM change
 Started by an SCM change
 Started by an SCM change
 Started by an SCM change
 Started by an SCM change
 Started by an SCM change
 Started by an SCM change
 Started by an SCM change
 Started by an SCM change
 Started by an SCM change
 Started by an SCM change
 Started by an SCM change
 Started by an SCM change
 Started by an SCM change
 Started by an SCM change
 Started by an SCM change
 Started by an SCM change
 Started by an SCM change
 Started by an SCM change
 Started by an SCM change
 Started by an SCM change
 Started by an SCM change
 Started by an SCM change
 Started by an SCM change
 Started by an SCM change
 Started by an SCM change
 Started by an SCM change
 Started by an SCM change
 Started by an SCM change
 Started by an SCM change
 Started by an SCM change
 Started by an SCM change
 Started by an SCM change
 Started by an SCM change
 Started by an SCM change
 Started by an SCM change
 Started by an SCM change
 Started by an SCM change
 Started by an SCM change
 Started by an SCM change
 Started by an SCM change
 Started by an SCM change
 Started by an SCM change
 Started by an SCM change
 Started by an SCM change
 Started by an SCM change
 Started by an SCM change
 Started by an SCM change
 Started by an SCM change
 Started by an SCM change
 Started by an SCM change
 Started by an SCM change
 Started by an SCM change
 Started by an SCM change
 Started by an SCM change
 Started by an SCM change
 Started by an SCM change
Building remotely on ubuntu4 in workspace <https://builds.apache.org/job/cloudstack-marvin-41/ws/>
Checkout:cloudstack-marvin-41 / <https://builds.apache.org/job/cloudstack-marvin-41/ws/> - hudson.remoting.Channel@34549c46:ubuntu4
Using strategy: Default
Last Built Revision: Revision be9b22caae21f4d40cda1e2191e9fea51645ec14 (origin/4.1)
Fetching changes from 1 remote Git repository
Fetching upstream changes from https://git-wip-us.apache.org/repos/asf/cloudstack.git
Commencing build of Revision 8fe99e64539947ff4645c5ca6addab0593f02c3d (origin/4.1)
Checking out Revision 8fe99e64539947ff4645c5ca6addab0593f02c3d (origin/4.1)
Parsing POMs
[cloudstack-marvin-41] $ /bin/bash -xe /tmp/hudson4851818630837062596.sh
+ mvn -P developer -pl :cloud-apidoc -pl :cloud-marvin
[INFO] Scanning for projects...
[ERROR] The build could not read 1 project -> [Help 1]
[ERROR]   
[ERROR]   The project org.apache.cloudstack:xapi:5.6.100-1-SNAPSHOT (<https://builds.apache.org/job/cloudstack-marvin-41/ws/deps/XenServerJava/pom.xml)> has 1 error
[ERROR]     Non-resolvable parent POM: Failure to find org.apache.cloudstack:cloudstack:pom:4.1.0 in http://repo.maven.apache.org/maven2 was cached in the local repository, resolution will not be reattempted until the update interval of central has elapsed or updates are forced and 'parent.relativePath' points at wrong local POM @ line 21, column 11 -> [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 'Execute shell' marked build as failure
ERROR: Failed to parse POMs
hudson.util.IOException2: remote file operation failed: <https://builds.apache.org/job/cloudstack-marvin-41/ws/> at hudson.remoting.Channel@34549c46:ubuntu4
	at hudson.FilePath.act(FilePath.java:861)
	at hudson.FilePath.act(FilePath.java:838)
	at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.parsePoms(MavenModuleSetBuild.java:862)
	at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.doRun(MavenModuleSetBuild.java:620)
	at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:592)
	at hudson.model.Run.execute(Run.java:1568)
	at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:477)
	at hudson.model.ResourceController.execute(ResourceController.java:88)
	at hudson.model.Executor.run(Executor.java:236)
Caused by: hudson.remoting.ProxyException: hudson.maven.MavenModuleSetBuild$MavenExecutionException: org.apache.maven.project.ProjectBuildingException: Some problems were encountered while processing the POMs:
[FATAL] Non-resolvable parent POM: Failure to find org.apache.cloudstack:cloudstack:pom:4.1.0 in http://repo.maven.apache.org/maven2 was cached in the local repository, resolution will not be reattempted until the update interval of central has elapsed or updates are forced and 'parent.relativePath' points at wrong local POM @ line 21, column 11

	at hudson.maven.MavenModuleSetBuild$PomParser.invoke(MavenModuleSetBuild.java:1229)
	at hudson.maven.MavenModuleSetBuild$PomParser.invoke(MavenModuleSetBuild.java:997)
	at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2348)
	at hudson.remoting.UserRequest.perform(UserRequest.java:118)
	at hudson.remoting.UserRequest.perform(UserRequest.java:48)
	at hudson.remoting.Request$2.run(Request.java:326)
	at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72)
	at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
	at java.util.concurrent.FutureTask.run(FutureTask.java:166)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
	at java.lang.Thread.run(Thread.java:679)
Caused by: hudson.remoting.ProxyException: org.apache.maven.project.ProjectBuildingException: Some problems were encountered while processing the POMs:
[FATAL] Non-resolvable parent POM: Failure to find org.apache.cloudstack:cloudstack:pom:4.1.0 in http://repo.maven.apache.org/maven2 was cached in the local repository, resolution will not be reattempted until the update interval of central has elapsed or updates are forced and 'parent.relativePath' points at wrong local POM @ line 21, column 11

	at org.apache.maven.project.DefaultProjectBuilder.build(DefaultProjectBuilder.java:363)
	at hudson.maven.MavenEmbedder.buildProjects(MavenEmbedder.java:361)
	at hudson.maven.MavenEmbedder.readProjects(MavenEmbedder.java:331)
	at hudson.maven.MavenModuleSetBuild$PomParser.invoke(MavenModuleSetBuild.java:1179)
	... 11 more
Archiving artifacts