Automatically detect/parse JUnit XML files for parsing
Currently, we require end users to:
- Know that we have the capability to parse JUnit reports
- Edit the CI YML to specifically note that a given filepath is a JUnit file
This presents a discoverability challenge, in that the only way you know about this feature is if you read our blog or read through that specific part of our docs.
What if we could, via a background job perhaps, scan through the XML artifacts that have been persisted to see if there are any JUnit files? We could then notify users somehow, perhaps via a banner on the project or some other method, that we could parse that file type if they edited their CI YML?
Or perhaps, we should just parse it automatically, and let an admin ignore the file path if desired? The runner could do some basic analysis of the files archived, and have a simple detection routine for JUnit XML files and automatically flag them.