www-infrastructure-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Philipp Ottlinger (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (INFRA-11968) Jenkins-Setup seems to contain codehaus.org / builds fail on Jenkins that work locally
Date Sun, 12 Jun 2016 07:29:20 GMT

    [ https://issues.apache.org/jira/browse/INFRA-11968?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15326240#comment-15326240
] 

Philipp Ottlinger commented on INFRA-11968:
-------------------------------------------

Current failures are due to "global" problems, I'm not sure if it's related to the codehaus
stuff:
{code}
maven3-interceptor-commons.jar already up to date
[Tamaya-Site-Master] $ /home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7/bin/java
-Xmx2g -Xms256m -XX:MaxPermSize=512m -cp /home/jenkins/jenkins-slave/maven32-agent.jar:/home/jenkins/jenkins-slave/tools/hudson.tasks.Maven_MavenInstallation/maven-3.3.3/boot/plexus-classworlds-2.5.2.jar:/home/jenkins/jenkins-slave/tools/hudson.tasks.Maven_MavenInstallation/maven-3.3.3/conf/logging
jenkins.maven3.agent.Maven32Main /home/jenkins/jenkins-slave/tools/hudson.tasks.Maven_MavenInstallation/maven-3.3.3
/home/jenkins/jenkins-slave/slave.jar /home/jenkins/jenkins-slave/maven32-interceptor.jar
/home/jenkins/jenkins-slave/maven3-interceptor-commons.jar 46301
Exception in thread "main" java.lang.ClassNotFoundException: hudson.remoting.Launcher
	at org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy.loadClass(SelfFirstStrategy.java:50)
	at org.codehaus.plexus.classworlds.realm.ClassRealm.unsynchronizedLoadClass(ClassRealm.java:271)
	at org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:247)
	at org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:239)
	at jenkins.maven3.agent.Maven32Main.main(Maven32Main.java:143)
	at jenkins.maven3.agent.Maven32Main.main(Maven32Main.java:74)
ERROR: Failed to parse POMs
java.io.EOFException: unexpected stream termination
	at hudson.remoting.ChannelBuilder.negotiate(ChannelBuilder.java:365)
	at hudson.remoting.ChannelBuilder.build(ChannelBuilder.java:310)
	at hudson.slaves.Channels.forProcess(Channels.java:115)
	at hudson.maven.AbstractMavenProcessFactory.newProcess(AbstractMavenProcessFactory.java:297)
	at hudson.maven.ProcessCache.get(ProcessCache.java:236)
	at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.doRun(MavenModuleSetBuild.java:778)
	at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:534)
	at hudson.model.Run.execute(Run.java:1738)
	at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:531)
	at hudson.model.ResourceController.execute(ResourceController.java:98)
	at hudson.model.Executor.run(Executor.java:410)
{code}

> Jenkins-Setup seems to contain codehaus.org / builds fail on Jenkins that work locally
> --------------------------------------------------------------------------------------
>
>                 Key: INFRA-11968
>                 URL: https://issues.apache.org/jira/browse/INFRA-11968
>             Project: Infrastructure
>          Issue Type: Bug
>          Components: Jenkins
>         Environment: https://builds.apache.org/job/Tamaya-Javadoc-Master/
> https://builds.apache.org/job/Tamaya-Site-Master/
>            Reporter: Philipp Ottlinger
>
> A Tamaya-Javadoc build - that works perfectly fine locally - fails on CI due to references
to codehaus.org.
> Since codehaus.org is down a while the question is how does this configuration come into
CI. A local build without any references to Codehaus repository works fine.
> The build runs daily and fails, please have a look on the logs:
> {code}
> [ERROR] Failed to execute goal org.apache.maven.plugins:maven-site-plugin:3.4:site (default-cli)
on project tamaya-code: failed to get report for org.codehaus.mojo:findbugs-maven-plugin:
Plugin org.codehaus.mojo:findbugs-maven-plugin:3.0.1 or one of its dependencies could not
be resolved: Could not transfer artifact org.apache.tamaya:buildconfigurations:jar:0.3-incubating-SNAPSHOT
from/to codehaus-snapshots (http://nexus.codehaus.org/snapshots/): nexus.codehaus.org: Unknown
host nexus.codehaus.org -> [Help 1]
> [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/MojoExecutionException
> [ERROR] 
> [ERROR] After correcting the problems, you can resume the build with the command
> [ERROR]   mvn <goals> -rf :tamaya-code
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message