[#HUDSON-1016] NUnit: Problem with BuildStepCompatibilityLayer.perform - Hudson JIRA

Hudson

NUnit: Problem with BuildStepCompatibilityLayer.perform

Created: 16/Nov/07 04:07 AM Updated: 18/Nov/07 02:23 AM Resolved: 18/Nov/07 02:23 AM

Component/s:

plugin

Affects Version/s:

current

Fix Version/s:

None

Environment:

Platform: All, OS: All

Description

« Hide

I tried running Hudson v.156 as a Windows service, and got the following error
which I havent seen before:

java.lang.UnsupportedOperationException
at
hudson.tasks.BuildStepCompatibilityLayer.perform(BuildStepCompatibilityLayer.java:60)
at hudson.plugins.nunit.NUnitPublisher.archive(NUnitPublisher.java:84)
at hudson.plugins.nunit.NUnitArchiver.performJUnitArchiver(NUnitArchiver.java:137)
at hudson.plugins.nunit.NUnitArchiver.invoke(NUnitArchiver.java:90)
at hudson.plugins.nunit.NUnitArchiver.invoke(NUnitArchiver.java:29)
at hudson.FilePath.act(FilePath.java:291)
at hudson.plugins.nunit.NUnitPublisher.perform(NUnitPublisher.java:72)
at
hudson.tasks.BuildStepCompatibilityLayer.perform(BuildStepCompatibilityLayer.java:33)
at hudson.model.Build$RunnerImpl.performAllBuildStep(Build.java:150)
at hudson.model.Build$RunnerImpl.post2(Build.java:137)
at hudson.model.AbstractBuild$AbstractRunner.post(AbstractBuild.java:254)
at hudson.model.Run.run(Run.java:667)
at hudson.model.Build.run(Build.java:102)
at hudson.model.ResourceController.execute(ResourceController.java:70)
at hudson.model.Executor.run(Executor.java:62)

Sort Order:

[ Permalink | « Hide ]

redsolo added a comment - 16/Nov/07 06:27 AM

This problem was introduced in Hudson 150. v1.149 works fine as we were using it
in our dev env. All releases after 150 would throw the below exception.

[ Permalink | « Hide ]

redsolo added a comment - 16/Nov/07 07:49 AM

The problem is with BuildStepCompatibilityLayer.perform() which will throw the
exception. The NUnit archiver should use the correct method when accesing JUnit

[ Permalink | « Hide ]

redsolo added a comment - 18/Nov/07 02:23 AM

Fixed. The NUnit publisher now calls the correct method in JUnit archiver. This
bug was introduced with the BuildStepCompabilityLayer in 1.150.