Hi all, Just to facilitate this thread, I am +1 regarding having micro-benchmarking support in Jenkins Test Harness. There are many stories related to performance degradation in Jenkins, and having a framework could help us to have some checks for the critical functionality like permission checks. The end goal of the project is to improve Role Strategy performance (which is far from perfect now), but it would be great if we could reuse the framework in other components.
Tomorrow at 7am UTC we will be doing a recorded demo of the current framework state, and everybody is welcome to join. Best regards, Oleg On Tuesday, May 28, 2019 at 8:20:14 AM UTC+2, [email protected] wrote: > > Hi everyone, > > As a part of this year's Google Summer of Code, I have been working on a > framework for allowing Java Microbenchmark Harness (JMH) benchmarks to be > run with Jenkins. The basic framework was implemented in the Role Strategy > Plugin through this pull request: > https://github.com/jenkinsci/role-strategy-plugin/pull/63 . For each > benchmark, a temporary Jenkins instance is created, similar to how > JenkinsRule from Jenkins Test Harness does it. The benchmarks are run > through a unit test which allows them to be integrated with the normal > pull > request builds (if required). Apart from configuring the Jenkins instance > for test using Java code, I've also added support for easily configuring > the > instance by YAML files using Jenkins Configuration as Code. The benchmark > reports are generated as JSON files which are compatible with the > jmh-report > plugin. I have implemented a couple of benchmarks for the Role Strategy > Plugin which can be seen in the Role Strategy Plugin GitHub repository. I > have attached screenshots of these results as visualized by the jmh-report > plugin. To make the framework easier to use, I'm also working on running > the > benchmarks through a Maven profile. > > To make it available to the rest of the community, I would like to propose > to make it either a part of Jenkins Test Harness or a part of new library > so > it can be used by other plugins and perhaps by Jenkins core itself. I > would > to love to hear your feedback, comments and suggestions. It would be even > better if you could join the project's weekly meetings (Tuesdays and > Fridays > at 7:00 AM UTC) and help us improve this framework. > > Thanks > Abhyudaya > GitHub: AbhyudayaSharma > > > -- 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/09147b86-6565-4b83-a4f8-3fbf48baa6cf%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
