> On 12. Dec 2019, at 21:51, Paul Davis wrote:
>
> Hey all,
>
> I was poking around at Jenkins the other day trying to get a good idea
> of how much time we're spending in various parts of the build. It
> occurred to me that one good way to at least investigate our eunit
> test suite is to pa
Cool beans. I'll take a crack at removing some of the ick around
displaying along with adding some command line arguments for
controlling output.
For long term storage I think it'd be better to store the raw XML
files rather than the formatted output which should be an easy
addition.
On Thu, Dec
+1. I think this is useful information to collect on every CI run and
store alongside the run, though keeping in mind we only keep the last
7-10 runs in Jenkins nowadays.
If we need it longer, we should stash the output with the log stasher.
This could allow graphing if someone wants to build
Hey all,
I was poking around at Jenkins the other day trying to get a good idea
of how much time we're spending in various parts of the build. It
occurred to me that one good way to at least investigate our eunit
test suite is to parse all of the generated surefire reports. I spent
an hour or so y
