[jira] [Comment Edited] (INFRA-6218) Jenkis - Bunch of Apache Camel builds end up with some wired Jenkins/Maven exceptions/errors.

["Babak Vahdat (JIRA)" <ji...@apache.org>]

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

Babak Vahdat edited comment on INFRA-6218 at 5/1/13 5:06 AM:
-------------------------------------------------------------

Sorry I don't get the point. That option is NOT selected by the "Camel.trunk.notest" profile, that's true. Actually I verified that it is NOT selected by ALL of the Apache Camel profiles.

If I understand it right, when this option is NOT selected then Archiving is ENABLED which is fine for us because we want JENKINS to archive. And then with this setting in place there should be no "[JENKINS] Archiving disabled" errors at all as we've got Archiving ENABLED.
                
      was (Author: bvahdat):
    Sorry I don't get the point. That option is NOT selected by the "Camel.trunk.notest" profile, that's true. Actually I verified that it is NOT selected by ALL of the Apache Camel profiles.

If I understand it right, when then option is NOT selected then Archiving is ENABLED which is fine for us because we want JENKINS to archive. And then with this setting in place there should be no "[JENKINS] Archiving disabled" errors at all as we've got Archiving ENABLED.
                  
> Jenkis - Bunch of Apache Camel builds end up with some wired Jenkins/Maven exceptions/errors.
> ---------------------------------------------------------------------------------------------
>
>                 Key: INFRA-6218
>                 URL: https://issues.apache.org/jira/browse/INFRA-6218
>             Project: Infrastructure
>          Issue Type: Task
>      Security Level: public(Regular issues) 
>          Components: Jenkins
>            Reporter: Babak Vahdat
>            Assignee: Jake Farrell
>
> Recently we're extremely suffering from different wired errors of Apache Camel builds. In many cases Jenkins says "Ping time out" and gives up the build process so we end up again & again with broken and incomplete builds shown with read bubbles, following two examples:
> https://builds.apache.org/job/Camel.trunk.fulltest/1324/console
> https://builds.apache.org/job/Camel.trunk.fulltest.java7/591/console
> And the corresponding Jenkins output in console:
> U camel-core/pom.xml
> U tooling/apt/src/main/java/org/apache/camel/tools/apt/EndpointAnnotationProcessor.java
> FATAL: hudson.remoting.RequestAbortedException: hudson.remoting.Channel$OrderlyShutdown
> hudson.remoting.RequestAbortedException: hudson.remoting.RequestAbortedException: hudson.remoting.Channel$OrderlyShutdown
> at hudson.remoting.Request.call(Request.java:174)
> at hudson.remoting.Channel.call(Channel.java:672)
> at hudson.FilePath.act(FilePath.java:854)
> at hudson.FilePath.act(FilePath.java:838)
> at hudson.scm.SubversionSCM.checkout(SubversionSCM.java:743)
> ...
> Or sometimes the build ends up with some wired Jenkins internal errors as you see here:
> https://builds.apache.org/job/Camel.trunk.fulltest.java7/582/console
> And the corresponding Jenkins output in console:
> [JENKINS] Archiving disabled
> [JENKINS] Archiving disabled
> Waiting for Jenkins to finish collecting data
> mavenExecutionResult exceptions not empty
> message : Internal error: java.lang.reflect.UndeclaredThrowableException
> cause : null
> Stack trace : 
> org.apache.maven.InternalErrorException: Internal error: java.lang.reflect.UndeclaredThrowableException
> at org.apache.maven.lifecycle.internal.BuilderCommon.handleBuildError(BuilderCommon.java:128)
> at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:95)
> at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
> at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
> at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
> No idea if all these has to do with the recent Jenkins upgrades @ INFRA. In all cases this is really annoying and currently almost all our builds end up with red bubbles.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira