Yipes! Even better for the full test run - from 51m47s end-to-end on ci.jenkins.io to 6m8s with @ClassRule. Looks like that actually is the magic bullet here.
A. On Mon, Sep 26, 2016 at 1:37 PM, Andrew Bayer <andrew.ba...@gmail.com> wrote: > huh, initial experiments with turning the JenkinsRule into a @ClassRule > rather than a @Rule have been...surprisingly positive. 4+x decrease in one > of the parameterized tests (from 95s to 21s). I'll experiment more in that > direction. > > A. > > On Mon, Sep 26, 2016 at 1:24 PM, Andrew Bayer <andrew.ba...@gmail.com> > wrote: > >> My tests in https://github.com/jenkinsci/pipeline-model-definition-plugin >> take...an ungodly amount of time. In part, that's 'cos I'm doing a *lot* of >> tests, and I'm using parameterized tests to make sure that failures are >> clear in some cases. But I gotta feel like things could be sped up. Does >> anyone know of any obvious tricks with JenkinsRule that can speed things up >> for a bunch of tests in a single class? >> >> A. >> > > -- 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 jenkinsci-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAPbPdOaWfXQ3vW1LQbSqFTj3NfL24MZScM6%2B%3DLwLPHuxy9A5_A%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
