Thanks Gareth! (Sorry for the delay -- new list; had my mail filters set
up wrong and didn't see your reply.)
>From my perspective, one of the big advantages of Jenkins is its UI; all of
the tools are right there in one place. Having to jump back and forth
between tools would obviously lessen
The big disadvantage of storing all your test results in Jenkins is that
they are stored in XML files and the only way to analyze of visualize them
is via the Jenkins test result reporting plugins such as the Junit plugin.
Most of them graph passes and failures over time and let you drill down
Hi all,
I'm new to Jenkins; hoping someone has some thoughts or experience:
I'm looking at re-working an existing system that runs a lot (order of,
say, a million) of automated tests per day. (That's many fewer distinct
tests but repeated many times daily as new versions are committed.)
