>From a pipeline, You cannot invoke methods in other Jenkins plugins unless
those plugins have been modified to support pipelines. See:
https://github.com/jenkinsci/pipeline-plugin/blob/master/COMPATIBILITY.md
https://github.com/jenkinsci/pipeline-plugin/blob/master/DEVGUIDE.md
--
Craig
On
ping? Is the shiny new pipeline functionality simply incompatible with all
of the existing plugins?
On Thursday, April 21, 2016 at 2:34:00 PM UTC-5, Andrew Melo wrote:
>
> Hi,
>
> I've dug a bit more, perhaps that will help find a solution. It appears
> the "step" groovy function wants a class
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:
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
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
