|
||||||||
|
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/d/optout.
We (the authors of the plugin, i.e. Diabol), believe that manual triggers DO make sense in a pipeline. A high degree of automation is great and necessary in a pipeline, but some decisions will be taken by humans in many pipelines. What should always be automated is the repetitive tasks. This is one of the reasons that we believe that the total CYCLE time is an important measure.
Also, I think your presentation is focusing too much on 'anecdotal' measurements. It's the statistical values that should matter. I attach a suggestion for displaying total cycle time and total build time. For the aggregate row, it's the same but with statistical values: average, minimum, median, 90-percentile and maximum. How about that?