> Am 26.06.2020 um 03:32 schrieb Sanjeet Malhotra > <[email protected]>: > > Thanks actually I need to have build info for all the builds which needs to > be displayed on the graph. So, I think anyhow the loading of xml file will > get triggered because I will be trying for last 30-50 builds.
What information are you reading? The data from the build xml or the data from the test results xml? > Apart from this, I was trying to write a unit test using power mockito and I > encountered an an error while building the plugin. I have attached the > terminal output for the same and it does not seem to be due the testcases > that I wrote but due to some version conflict. > See https://www.jenkins.io/doc/developer/plugin-development/updating-parent/ <https://www.jenkins.io/doc/developer/plugin-development/updating-parent/> > On Wednesday, June 24, 2020 at 5:43:02 PM UTC+5:30, Jesse Glick wrote: > On Tue, Jun 23, 2020 at 7:18 PM Jesse Glick <[email protected] <>> wrote: > >> reloading of previous builds is quite expensive > > > > There is not really a workaround > > I should clarify that you _can_ load historical results without > triggering disk I/O, if they happened to be in memory anyway, which > the test trend graph does: > > https://github.com/jenkinsci/junit-plugin/blob/bab34bcc96154a494f8c371953efe06d45813f67/src/main/java/hudson/tasks/test/AbstractTestResultAction.java#L341-L346 > > <https://github.com/jenkinsci/junit-plugin/blob/bab34bcc96154a494f8c371953efe06d45813f67/src/main/java/hudson/tasks/test/AbstractTestResultAction.java#L341-L346> > > https://github.com/jenkinsci/junit-plugin/blob/bab34bcc96154a494f8c371953efe06d45813f67/src/main/java/hudson/tasks/test/AbstractTestResultAction.java#L218-L225 > > <https://github.com/jenkinsci/junit-plugin/blob/bab34bcc96154a494f8c371953efe06d45813f67/src/main/java/hudson/tasks/test/AbstractTestResultAction.java#L218-L225> > > > The issue is that you cannot efficiently query historical builds > without forcing them to be loaded—there is no equivalent of a SQL > statement you could run to get some aggregate statistic over thousands > of builds that would perform tolerably. So if the last five builds are > in memory (a typical situation forced by the weather list view > column), you can cheaply inspect those five, but inspecting the one > before them will be expensive. > > -- > You received this message because you are subscribed to the Google Groups > "Jenkins Developers" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected] > <mailto:[email protected]>. > To view this discussion on the web visit > https://groups.google.com/d/msgid/jenkinsci-dev/12410601-8a06-4b91-b391-37892f666f4ao%40googlegroups.com > > <https://groups.google.com/d/msgid/jenkinsci-dev/12410601-8a06-4b91-b391-37892f666f4ao%40googlegroups.com?utm_medium=email&utm_source=footer>. > <Screenshot 2020-06-26 at 6.41.26 AM.png><Screenshot 2020-06-26 at 6.42.12 > AM.png> -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/B704033D-A204-4D26-BE1D-FF2670FA5C6C%40gmail.com.
