> On 20. Aug 2017, at 21:45, Slide wrote:
>
> Just so you are aware, you can release snapshots and they will show up in the
> experimental plugin site
To clarify, these aren't snapshots, just releases with a magic version number
(containing 'alpha' or 'beta').
--
You
This is great. Just so you are aware, you can release snapshots and they
will show up in the experimental plugin site, but then you don't have to
host the hpi on your own server, it's available on the jenkins infra. Just
make the release version have alpha or beta or something in the version
The hpi present at the address http://nilleb.com/pub/mstest-0.20-snapshot/
Exposes the mstest plugin to a pipeline (jenkinsfile) with the "mstest"
symbol.
I have linted a little a part of the plugin code, as described in the
pipeline devguide. I will eventually continue on the next days. The lint
Great! Thanks a lot Slide, I'll add the @Symbol this afternoon (and I think
that I have implemented the right method yesterday, hooray )
Le sam. 19 août 2017 à 20:21, Slide a écrit :
> SimpleBuildStep is one part, you'll want to change your perform method to
> override
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
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 <
ivo.bellinsala...@gmail.com> a écrit :
> Is it sufficient to inherit from SimpleBuildStep to enable the pipeline?
> Should I expose attributes via some
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
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
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: jer...@bodycad.com
Sent: 16 August 2017 13:24
To: Jenkins Users
Subject: Re: Does anyone know if the