|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
It seems to be the fact that the TAP plugin saves its test results in the main build.xml file that is the problem. One of our core modules has over 60,000 tests, which leads to build.xml reaching close to 100Mb in size. When the Jenkins UI populates the build history display on the left of the project page it parses build.xml to extract the <result> tag to flag the build as success, failed, unstable etc. It must parse the entire xml to extract this tag however, so with a 20 job history it parses 2Gb of xml, which causes the UI to grind to a halt for minutes. A more elegant solution would be to structure the TAP plugin as the warnings plugin, where the number of test passes / failures / skips can be stored in build.xml (allowing a quick rendering of the trend plots etc) with the actual test results / output being stored in a separate xml file which only needs to be parsed when the TAP results page is loaded.
Does this sound sensible / achievable?