Hi, I've dug a bit more, perhaps that will help find a solution. It appears the "step" groovy function wants a class that implements SimpleBuildStep, but the plugins I'm looking at implements/extends hudson.tasks.Recorder. I'm confused about the issue. If I look at the javadoc:
http://javadoc.jenkins-ci.org/hudson/tasks/Recorder.html I see that Recorder implements BuildStep, but not SimpleBuildStep. But (and my java is rusty, so forgive the terminology), since BuildStep is a superinterface of SimpleBuild step, shouldn't it "count" for when step() searches for a class implementing the interface? Thanks Andrew On Sunday, April 17, 2016 at 8:24:43 PM UTC-5, Andrew Melo wrote: > > Hi again, > > I poked at it some more and it appears I'll have to explicitly change the > plugins I want to use in a pipeline. The following: > > step([$class: 'TapPublisher', testResults: 'tap.log']) > > yields the following error: > > no known implementation of interface jenkins.tasks.SimpleBuildStep is > named TapPublisher > > Or, perhaps a new groovy step that consumes classes of type 'Recorder' is > the better idea? > > Thanks again! > Andrew > > On Sunday, April 17, 2016 at 1:40:28 PM UTC-5, Andrew Melo wrote: >> >> Hello all, >> >> I would like to trigger build/post-build steps that don't appear in the >> snippet viewer (e.g. publish TAP results) from a pipeline. Is there a way >> to trigger arbitrary build/post-build steps that don't appear in the >> snippet browser, or will the plugin need to be updated to explicitly >> support being triggered from pipelines? >> >> Thanks! >> Andrew >> > -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/cc9add83-2b68-4e4c-9a13-cc0b1920bb3f%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
