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 to individual failures, but there's no way to get additional analysis short of modifying the plugins.
You may also run into some scaling issues the further back you keep the test results, since the test results graphs on the build pages have to be geberated on the fly from the test results XML files. With the amount of tests you're looking at, I would recommend looking at exporting the results to a tool such as ElasticSearch that will let you create arbitrary graphs and queries over the data. My company is taking this approach so that we can analyze trends such as "flaky" tests that intermittently fail, and also keep the test results longer than would be possible in Jenkins without running out of disk space. -- 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]. For more options, visit https://groups.google.com/d/optout.
