|
||||||||
|
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/groups/opt_out.
Maybe so but that winds up being a significant portion of startup time, especially if you are running interactive or Selenium tests, etc.
This would be wonderful!
I doubt that is practical—there would be too many false positives, since performance timings are always mere estimates (unless you can run in some very tightly controlled virtual machine). Anyway in some cases a slightly slower startup is a worthwhile price to pay for some crucial fix or major feature; it requires human judgment to decide whether a performance regression is a mistake, and if so, who should fix it.