we actually do publish the results (using xUnit). But specifically for any
failed test, wewant to easily access the detailed (and quite large) log files
to analyze what went wrong.We could also publish all those log files as
artifacts, but there are a lot of them.As such, our current idea is still to
find those files within the workspace.
On Friday, April 5, 2019, 3:18:10 PM GMT+2, Lukas Resch
<[email protected]> wrote:
Hi,
Am 05.04.2019 um 14:57 schrieb 'monger_39' via Jenkins Users:
> I have a scripted parallel pipeline job. Within each of the stages test steps
> are run (under NUnit)
> that generate detailed logs per step, and a summary in the console. To make
> life easier for us we,
> when a test fail generates an assert, wish to insert a workspace link to that
> detailed file.
> With that it would be very easy to navigate to the details from the
> TestResult page.
Why are you not just publishing the test results on Jenkins? Thereby you
would get access to all test details via the web interface rather than
on the console.
I haven't used NUnit, but the JUnit plugin provides excatly what you
describe.
HTH
--
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/bc3f55bc-c265-2d3e-2346-00446002ec60%40ngworx.ag.
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/1180254799.141475.1554473189711%40mail.yahoo.com.
For more options, visit https://groups.google.com/d/optout.
