Thank you for the screenshots associated with the pull request.

I would prefer to display the actual time for the pipeline to finish, rather than just adding up the build task duration for each task. In a pipeline with parallel stages the figure would otherwise be deceptive.

Thanks for the comment. I think you are right about the concurrent builds. I will update the code.

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?

Pipeline with individual cycle and build times and stats.

Great suggestion. I will work more on that. Meanwhile I'm going to close the PR and lower the priority of this JIRA.

I would love to see this feature come to fruition. Let me know if I can help.

Merged PR https://github.com/Diabol/delivery-pipeline-plugin/pull/103

Release in 0.9.4

Thank you all for this great feature, very useful!

I am using v0.9.5 and I see that the build times are reported as the sum of the build times for all steps. However, earlier in this thread, there was a discussion about the concurrent steps that should not be counted twice. So in this version, it does not seem to be implemented.
Could you please clarify?

And if confirmed, what is the general sense of what the logic should be?
IMHO, I see value in different scenarios:

• Actual build times, excluding concurrent steps (i.e. actual time spent building steps)
• Total end-to-end times (pipeline time to complete), including the inactive time in case of MANUAL triggers
  So, and realizing this adds complexity, maybe a configuration for potentially multiple displays:
  [ ] show total build times
  [ ] show actual build times
  [ ] show end-to-end pipeline duration
  What is your sense, so that we can decide if a follow-up enhancement ticket should be created ? Thanks in advance!

Is it possible to use this feature in messages? I.e. in HipChat messages. Like:

job-pipeline #3007 SUCCESSFUL after 1 min 42 sec