Does 1.418 need a new swarm jar file?

[Mark Waite]

I upgraded my experiments machine to Jenkins 1.418.  It has several slave nodes which are connecting with the swarm plugin (java -jar swarm-client-1.4-jar-with-dependencies.jar).

Now that I've upgraded to 1.418, my jobs that use the Warnings plugin all fail with the message:

Failed to deserialize the Callable object. Perhaps you needed to implement DelegatingCallable?

Later in the stack trace there is a "Class not found" exception as well.

That failure message is mentioned in an earlier e-mail thread.  The earlier mail thread suggests that I may need to use a later version of slave.jar.  Unfortunately, as far as I can tell, there is no later version of the swarm client jar with dependencies.  

I'm using the 1.4 version of the swarm client jar file, which seems to be the latest available from http://maven.dyndns.org/2/org/jvnet/hudson/plugins/swarm-client/ (as referenced by the Swarm plugin wiki page - https://wiki.jenkins-ci.org/display/JENKINS/Swarm+Plugin).

I can switch from using the swarm plugin to defining the slaves myself at the central server, but I prefer the swarm technique for defining clients, since it allows clients to come and go without me having to make changes on the server.

Am I diagnosing the problem correctly, or is there something different needed?

Thanks,
Mark Waite

[Mark Waite]

In case it helps, the specific class not found exception was:

Caused by: java.lang.ClassNotFoundException: hudson.plugins.warnings.parser.Warning

I am unable to duplicate the problem on the LTS version (1.409.1), and I had not seen the problem on the earlier version running on that machine, which I believe was 1.414.

Mark Waite

---

From: Mark Waite <[hidden email]>
To: Jenkins-CI Users <[hidden email]>
Sent: Friday, July 1, 2011 5:55 PM
Subject: Does 1.418 need a new swarm jar file?

I upgraded my experiments machine to Jenkins 1.418.  It has several slave nodes which are connecting with the swarm plugin (java -jar swarm-client-1.4-jar-with-dependencies.jar).

Now that I've upgraded to 1.418, my jobs that use the Warnings plugin all fail with the message:

Failed to deserialize the Callable object. Perhaps you needed to implement DelegatingCallable?

Later in the stack trace there is a "Class not found" exception as well.

That failure message is mentioned in an earlier e-mail thread.  The earlier mail thread suggests that I may need to use a later version of slave.jar.  Unfortunately, as far as I can tell, there is no later version of the swarm client jar with dependencies.  

I'm using the 1.4 version of the swarm client jar file, which seems to be the latest available from http://maven.dyndns.org/2/org/jvnet/hudson/plugins/swarm-client/ (as referenced by the Swarm plugin wiki page - https://wiki.jenkins-ci.org/display/JENKINS/Swarm+Plugin).

I can switch from using the swarm plugin to defining the slaves myself at the central server, but I prefer the swarm technique for defining clients, since it allows clients to come and go without me having to make changes on the server.

Am I diagnosing the problem correctly, or is there something different needed?

Thanks,
Mark Waite

[Ulli Hafner]

On 07/02/2011 01:55 AM, Mark Waite wrote:

I upgraded my experiments machine to Jenkins 1.418.  It has several slave nodes which are connecting with the swarm plugin (java -jar swarm-client-1.4-jar-with-dependencies.jar).

Now that I've upgraded to 1.418, my jobs that use the Warnings plugin all fail with the message:

Failed to deserialize the Callable object. Perhaps you needed to implement DelegatingCallable?

Later in the stack trace there is a "Class not found" exception as well.

That failure message is mentioned in an earlier e-mail thread.  The earlier mail thread suggests that I may need to use a later version of slave.jar.  Unfortunately, as far as I can tell, there is no later version of the swarm client jar with dependencies.  

I'm using the 1.4 version of the swarm client jar file, which seems to be the latest available from http://maven.dyndns.org/2/org/jvnet/hudson/plugins/swarm-client/ (as referenced by the Swarm plugin wiki page - https://wiki.jenkins-ci.org/display/JENKINS/Swarm+Plugin).

I can switch from using the swarm plugin to defining the slaves myself at the central server, but I prefer the swarm technique for defining clients, since it allows clients to come and go without me having to make changes on the server.

Am I diagnosing the problem correctly, or is there something different needed?

Thanks,
Mark Waite

I'm not sure if this is related to a change in core or in my plug-ins. See JENKINS-10183 and JENKINS-10153 for the corresponding Jira issues. Does the error disappear if you are reverting to your previous Jenkins version (without changing the warnings plug-in?).

Ulli

[manandbytes]

On 07/02/2011 03:13 AM, Mark Waite wrote:
> In case it helps, the specific class not found exception was:
>
> Caused by: java.lang.ClassNotFoundException:
> hudson.plugins.warnings.parser.Warning

The full stacktrace will help to find the source of this problem. Could
you post it?

--
Mykola

[Manuel Doninger]

On Sat, Jul 2, 2011 at 11:40, Mykola Nikishov <[hidden email]> wrote:

> On 07/02/2011 03:13 AM, Mark Waite wrote:
>> In case it helps, the specific class not found exception was:
>>
>> Caused by: java.lang.ClassNotFoundException:
>> hudson.plugins.warnings.parser.Warning
>
> The full stacktrace will help to find the source of this problem. Could
> you post it?
>
> --
> Mykola
>

The Swarm client with dependencies has the classes from the slave.jar
in it. With 1.418 the slave.jar has to be upgraded. So either you
contact the maintainer of the swarm plugin to release a new version
with updated dependencies, or you use the swarm client without
dependencies and add the slave.jar to the classpath if you execute the
swarm client.

Manuel

[Mark Waite]

Thanks for the clarification.  I have several choices, and they all seem reasonable to me.

I can switch from the cutting edge Jenkins version to the long term support version (since it hasn't yet switched to need the new slave.jar), or I can switch to the swarm client without dependencies and satisfy the dependencies myself (including the new slave.jar), or I can wait for an updated swarm client with dependencies.  The first two are both very reasonable for me, so I'll pick one of those two and move forward.

I guess another alternative would be to attempt to package my own swarm client jar file with dependencies.  I'm not sure I'd be successful with that attempt.

Thanks again for a great application and for amazing support from the mailing list.

Mark Waite

---

From: Manuel Doninger <[hidden email]>
To: [hidden email]
Sent: Saturday, July 2, 2011 2:37 PM
Subject: Re: Does 1.418 need a new swarm jar file?

On Sat, Jul 2, 2011 at 11:40, Mykola Nikishov <[hidden email]> wrote:

> On 07/02/2011 03:13 AM, Mark Waite wrote:
>> In case it helps, the specific class not found exception was:
>>
>> Caused by: java.lang.ClassNotFoundException:
>> hudson.plugins.warnings.parser.Warning
>
> The full stacktrace will help to find the source of this problem. Could
> you post it?
>
> --
> Mykola
>

The Swarm client with dependencies has the classes from the slave.jar
in it. With 1.418 the slave.jar has to be upgraded. So either you
contact the maintainer of the swarm plugin to release a new version
with updated dependencies, or you use the swarm client without
dependencies and add the slave.jar to the classpath if you execute the
swarm client.

Manuel

[Henk van Voorthuijsen-2]

On Jul 2, 11:33 am, Ulli Hafner <[hidden email]> wrote:

> I'm not sure if this is related to a change in core or in my plug-ins.
> See JENKINS-10183 <https://issues.jenkins-ci.org/browse/JENKINS-10183>
> and JENKINS-10153 <https://issues.jenkins-ci.org/browse/JENKINS-10153>
> for the corresponding Jira issues. Does the error disappear if you are
> reverting to your previous Jenkins version (without changing the
> warnings plug-in?).
>
> Ulli

You can add <https://issues.jenkins-ci.org/browse/JENKINS-10171> to
that list.
That's FindbugsParser it cannot find on a swarm client.

Henk

[JamesRigby]

Hi

I think I have come across a bug in the perforce plugin changelist

The following output shows the problem

Started by an SCM change
Building remotely on Roadrunner
Using remote perforce client: CI_WalkaboutZombieLand-Roadrunner
[WalkaboutZombieLand] $ p4.exe workspace -o CI_WalkaboutZombieLand-Roadrunner
Saving modified client CI_WalkaboutZombieLand-Roadrunner
[WalkaboutZombieLand] $ p4.exe -s client -i
Last build changeset: 164616
[WalkaboutZombieLand] $ p4.exe counter change
[WalkaboutZombieLand] $ p4.exe -s changes //CI_WalkaboutZombieLand-Roadrunner/...@164617,@164628
[WalkaboutZombieLand] $ p4.exe describe -s 164627
[WalkaboutZombieLand] $ p4.exe describe -s 164621
[WalkaboutZombieLand] $ p4.exe describe -s 164618
[WalkaboutZombieLand] $ p4.exe describe -s 164617
Sync'ing workspace to changelist 164627.
[WalkaboutZombieLand] $ p4.exe sync //CI_WalkaboutZombieLand-Roadrunner/...@164627

It will display the changes from changelist 164617 to 164628.  However, it then syncs against changelist 164627.  Therefore the page that shows the changes in this build will show a change that is not in this build, but the next build.

Regards

James Rigby

[Mark Waite]

The 

---

From: Henk van Voorthuijsen <[hidden email]>
To: Jenkins Users <[hidden email]>
Sent: Monday, July 4, 2011 8:24 AM
Subject: Re: Does 1.418 need a new swarm jar file?

On Jul 2, 11:33 am, Ulli Hafner <[hidden email]> wrote:

> I'm not sure if this is related to a change in core or in my plug-ins.
> See JENKINS-10183 <https://issues.jenkins-ci.org/browse/JENKINS-10183>
> and JENKINS-10153 <https://issues.jenkins-ci.org/browse/JENKINS-10153>
> for the corresponding Jira issues. Does the error disappear if you are
> reverting to your previous Jenkins version (without changing the
> warnings plug-in?).
>
> Ulli

You can add <https://issues.jenkins-ci.org/browse/JENKINS-10171> to
that list.
That's FindbugsParser it cannot find on a swarm client.

I first saw the problem when I upgraded from the earlier Jenkins to 1.418.  At that time I was running an older (out of date) Warnings plugin.  Upgrading the Warnings plugin did not change the failure.  I assumed (possibly incorrectly) that the problem was likely a core Jenkins change rather than a plugin change, since I did not alter the plugin.

Mark

[vtintillier]

Hi,

from what I can see from your logs, it looks good to me. 164628 may be the last change in your server, whereas 164627 is the last change impacting your view.

Do you have 164628 showing in the web UI? If so, you're right, there is an issue. If not, I think it's OK.

Regards

Vivien

On Mon, Jul 4, 2011 at 4:55 PM, James Rigby <[hidden email]> wrote:

Hi

I think I have come across a bug in the perforce plugin changelist

The following output shows the problem

Started by an SCM change
Building remotely on Roadrunner
Using remote perforce client: CI_WalkaboutZombieLand-Roadrunner
[WalkaboutZombieLand] $ p4.exe workspace -o CI_WalkaboutZombieLand-Roadrunner
Saving modified client CI_WalkaboutZombieLand-Roadrunner
[WalkaboutZombieLand] $ p4.exe -s client -i
Last build changeset: 164616
[WalkaboutZombieLand] $ p4.exe counter change
[WalkaboutZombieLand] $ p4.exe -s changes //CI_WalkaboutZombieLand-Roadrunner/...@164617,@164628
[WalkaboutZombieLand] $ p4.exe describe -s 164627
[WalkaboutZombieLand] $ p4.exe describe -s 164621
[WalkaboutZombieLand] $ p4.exe describe -s 164618
[WalkaboutZombieLand] $ p4.exe describe -s 164617
Sync'ing workspace to changelist 164627.
[WalkaboutZombieLand] $ p4.exe sync //CI_WalkaboutZombieLand-Roadrunner/...@164627

It will display the changes from changelist 164617 to 164628.  However, it then syncs against changelist 164627.  Therefore the page that shows the changes in this build will show a change that is not in this build, but the next build.

Regards

James Rigby