Bug 430200 - support Jenkins 1.532.2
Summary: support Jenkins 1.532.2
Status: RESOLVED FIXED
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: Mylyn (show other bugs)
Version: unspecified   Edit
Hardware: Macintosh Mac OS X
: P3 enhancement (vote)
Target Milestone: 1.4   Edit
Assignee: Tim Cheung CLA
QA Contact:
URL:
Whiteboard:
Keywords: contributed
: 430483 (view as bug list)
Depends on:
Blocks:
 
Reported: 2014-03-12 11:34 EDT by Steffen Pingel CLA
Modified: 2014-04-22 18:40 EDT (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Steffen Pingel CLA 2014-03-12 11:34:58 EDT
2 tests against Jenkins 1.532.2 are failing. We should check if any code changes are needed to support 1.532.2.

Unexpected response from Hudson server for '/jenkins-1.532.2/job/test-succeeding/build': Created
Stacktrace

org.eclipse.mylyn.internal.hudson.core.client.HudsonException: Unexpected response from Hudson server for '/jenkins-1.532.2/job/test-succeeding/build': Created
	at org.eclipse.mylyn.internal.hudson.core.client.HudsonOperation.validate(HudsonOperation.java:235)
	at org.eclipse.mylyn.internal.hudson.core.client.RestfulHudsonClient$7.doValidate(RestfulHudsonClient.java:359)
	at org.eclipse.mylyn.internal.hudson.core.client.HudsonOperation.processAndRelease(HudsonOperation.java:220)
	at org.eclipse.mylyn.internal.hudson.core.client.RestfulHudsonClient$7.execute(RestfulHudsonClient.java:353)
	at org.eclipse.mylyn.internal.hudson.core.client.HudsonOperation.run(HudsonOperation.java:167)
	at org.eclipse.mylyn.internal.hudson.core.client.RestfulHudsonClient.runBuild(RestfulHudsonClient.java:361)
Comment 1 Sam Davis CLA 2014-03-12 18:35:24 EDT
The fixture was aded on bug 428030. Does the gerrit build not run all fixtures? If not we should run them manually when adding new versions.
Comment 2 Steffen Pingel CLA 2014-03-13 05:05:46 EDT
(In reply to comment #1)
> The fixture was aded on bug 428030. Does the gerrit build not run all fixtures?

It runs the default fixtures.

> If not we should run them manually when adding new versions.

It's a chicken and egg problem. Unless you provision the new fixtures you can't run tests unless you provision everything locally first. Often it's more efficient to re-provision the server, let Hudson run tests and fix problems then and revert if it's a bigger deal.
Comment 3 Sam Davis CLA 2014-03-13 16:02:22 EDT
I see. That makes sense.
Comment 4 Steffen Pingel CLA 2014-03-17 08:04:34 EDT
*** Bug 430483 has been marked as a duplicate of this bug. ***
Comment 5 Sam Davis CLA 2014-04-22 18:40:10 EDT
Thanks very much, Tim, for the contribution!