Claus Ibsen created CAMEL-24602:
-----------------------------------
Summary: CI test reporting should include elapsed time (duration)
not just module/test counts
Key: CAMEL-24602
URL: https://issues.apache.org/jira/browse/CAMEL-24602
Project: Camel
Issue Type: Improvement
Reporter: Claus Ibsen
Today the CI test reporting only shows the *number of modules* and the *number
of tests* executed. It would be very useful if the reporting could also include
the *elapsed time* (e.g. in minutes) of the build/test runs.
Ideally the timing should be reported per module (or grouped) so we can
pinpoint which modules take disproportionately long to build/test.
*Motivation*
We currently run a lot of CI and put too much stress on the CI infrastructure.
Having per-module timing data would let us identify the slowest modules and
target them for optimization, helping reduce the overall CI load and turnaround
time.
*Suggested outcome*
- Report total elapsed build/test time.
- Ideally break the time down per module (or highlight the top N slowest
modules) so hotspots are easy to spot.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
