SimpleBuildStep is one part, you'll want to change your perform method to
override the one that takes a Run<?,?>, FilePath, TaskListener and Launcher
(note, this overload does NOT return a true/false for build result, you
need to set the result on the Run object using setResult). You don't need
to override both, you can just override the one that I mention and it will
work for both pipeline and freestyle. You'll also want to add an @Symbol
annotation to your descriptor so that people can use a shorthand when using
mstest from pipeline. I'd recommend something like @Symbol("mstest"). You
may need to add a dependency on the structs plugin for the @Symbol to be
available.On Sat, Aug 19, 2017 at 6:32 AM Ivo Bellin Salarin < [email protected]> wrote: > Please accept this as the changelog of the current test binary :-) > - this version completely disables the emma coverage report... > - ...keeping the transformation steps which convert the MS coverage > reports into emma-compatible coverage reports. > - and tries to expose the MsTestPublisher as a SimpleBuildStep (in order > to use it from pipeline workflows) > > > Le sam. 19 août 2017 à 15:25, Ivo Bellin Salarin < > [email protected]> a écrit : > >> If anyone tests the plugin present on this website: >> http://nilleb.com/pub/mstest-0.20-snapshot/ >> Following the instructions present on >> https://wiki.jenkins.io/display/JENKINS/Plugin+tutorial#Plugintutorial-Deployingacustombuildofacoreplugin >> I will release it the next friday. >> >> Have a good day, >> Ivo >> >> Le sam. 19 août 2017 à 12:27, Ivo Bellin Salarin < >> [email protected]> a écrit : >> >>> BTW, is there anybody to test a alpha version of the plugin? (With the >>> pipeline enabled?) >>> >>> Le sam. 19 août 2017 à 12:20, Ivo Bellin Salarin < >>> [email protected]> a écrit : >>> >>>> Is it sufficient to inherit from SimpleBuildStep to enable the >>>> pipeline? Should I expose attributes via some kind of decorator? >>>> Where to find the documentation about that? >>>> >>>> There's some code that waits for being released. It could be a good >>>> opportunity to deliver also the pipeline, if I get to know which changes it >>>> involves. >>>> >>>> Le ven. 18 août 2017 à 03:49, red 888 <[email protected]> a >>>> écrit : >>>> >>>>> Yes the xunit plugin is great! thats what I'm using now. As you say I >>>>> still use an MS test runner exe which generates a trx and then point the >>>>> xunit plugin to that report and it does everything else. >>>>> >>>>> >>>>> On Wednesday, August 16, 2017 at 8:31:39 AM UTC-4, Daniel Butler wrote: >>>>> >>>>>> The XUnit plugin has support for MSTest output and is pipeline >>>>>> compatible. >>>>>> >>>>>> You’d still need to run MSTest from a bat/powershell command but the >>>>>> Xunit plugin will publish the test output. >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>> *From: *[email protected] >>>>>> >>>>> >>>>>> *Sent: *16 August 2017 13:24 >>>>>> *To: *Jenkins Users >>>>>> *Subject: *Re: Does anyone know if the MSTest plugin supports >>>>>> pipelines and howto use it in a pipeline (jenkinsfile)? >>>>>> >>>>> >>>>>> >>>>>> Sadly no, many puglin are still incompatible, you can see the >>>>>> compatibility list here: >>>>>> >>>>>> >>>>>> https://github.com/jenkinsci/pipeline-plugin/blob/master/COMPATIBILITY.md >>>>>> >>>>>> >>>>>> >>>>>> Since the .trx is just an xml file, you could try to do an .xslt file >>>>>> that do the convertion to junit .xml. Maybe someone already did it >>>>>> somewhere, worth googling, I known some people have done .trx to .html >>>>>> graph (which you could use and publish the html results too). >>>>>> >>>>> -- >>>>>> 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/75edf196-1d55-4bca-b0df-e0025e837f28%40googlegroups.com >>>>>> <https://groups.google.com/d/msgid/jenkinsci-users/75edf196-1d55-4bca-b0df-e0025e837f28%40googlegroups.com?utm_medium=email&utm_source=footer> >>>>>> . >>>>>> For more options, visit https://groups.google.com/d/optout. >>>>>> >>>>> -- >>>>> 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/d8cdb00e-53e2-4efa-b4d1-dab9a680aa9a%40googlegroups.com >>>>> <https://groups.google.com/d/msgid/jenkinsci-users/d8cdb00e-53e2-4efa-b4d1-dab9a680aa9a%40googlegroups.com?utm_medium=email&utm_source=footer> >>>>> . >>>>> For more options, visit https://groups.google.com/d/optout. >>>>> >>>> -- > 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/CAPc4eF8Zyb9A3cikdq83J-TH33_x1ZtPZ7%3D8jbNRz8OqCC%3DAvg%40mail.gmail.com > <https://groups.google.com/d/msgid/jenkinsci-users/CAPc4eF8Zyb9A3cikdq83J-TH33_x1ZtPZ7%3D8jbNRz8OqCC%3DAvg%40mail.gmail.com?utm_medium=email&utm_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > -- 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/CAPiUgVeR9G%3DmkxtTogaqoj8yZHmGUW4LOLV2gdH4u4FTO3d4QA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
