You are viewing a plain text version of this content. The canonical link for it is here.
Posted to infrastructure-issues@apache.org by "Daniel Takamori (JIRA)" <ji...@apache.org> on 2016/06/14 20:32:30 UTC

[jira] [Commented] (INFRA-12098) Build jobs failing with java.lang.ClassNotFoundException: hudson.remoting.Launcher

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

Daniel Takamori commented on INFRA-12098:
-----------------------------------------

Queued new jobs and waiting to see results after making changes to new puppetized agents.

> Build jobs failing with java.lang.ClassNotFoundException: hudson.remoting.Launcher
> ----------------------------------------------------------------------------------
>
>                 Key: INFRA-12098
>                 URL: https://issues.apache.org/jira/browse/INFRA-12098
>             Project: Infrastructure
>          Issue Type: Bug
>          Components: Jenkins
>            Reporter: Benedikt Ritter
>
> Hello,
> some of the build jobs of the Apache Commons project fail with {{{java.lang.ClassNotFoundException: hudson.remoting.Launcher}}}. Take for example the build job for Apache Commons FileUpload [1]. It doesn't look like it is related to the project, but to the way the build infrastructure is set up. See also:
> - Commons Validator [2]
> - Commons BCEL [3] (note that job #4 failed, but #5 was successful again)
> [1] https://builds.apache.org/view/Apache%20Commons/job/commons-fileupload/11/console
> [2] https://builds.apache.org/view/Apache%20Commons/job/commons-validator/4/console
> [3] https://builds.apache.org/view/Apache%20Commons/job/commons-bcel/4/console



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