Hi, > Is this something people would be interested in?
yes, sounds interesting > Having either large sample JENKINS_HOME specimens or test code that can > generate pathological data would be required, as well as automation around > running it on a variety of machines (not necessarily cloud, ideally want to > be testing code not cloud infrastructure). IMHO it's better to have some code do generate various type of workspaces and loads - same as in the mentioned presentation, you should check performance characteristics for various job types, log sizes, number of plugin used etc. Using one big workspace can be harder to understand as it can combine multiple issues together and you can end up with tuned Jenkins which works fine with this use case, but performs not that well with other use cases. I did very simple job generator of freestyle jobs [1] for PerfCake [2] to measure responsiveness of job upload in the past. If you are interested, I can updated it to generate various jobs or it can be done in any other tool you prefer (or standalone application if you like). Cheers Vojta [1] https://github.com/vjuranek/jenkins-perf-tests/blob/master/perfcake/src/main/resources/scenarios/create-freestyle.xml [2] https://www.perfcake.org/ -- 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/1541911.yeAEkfGOKe%40localhost.localdomain. For more options, visit https://groups.google.com/d/optout.
signature.asc
Description: This is a digitally signed message part.
