I am having to run builds multiple times to debug a few jobs. This results in the first several runs being very short. Later when I get everything working, running a job shows Builds is taking xxxx seconds/minutes longer than usual. How can I reset the average duration timer?
As I said, setting up a build plan is an iterative process and those initial short runs only take a few seconds. If I have to run it 20x to get some scripts right, I would like to get an accurate time for real builds.
Actual use case - accurately determine if I should go get coffee or take a break while waiting for build to complete.
Theoretically, I could just create a debug plan and when it's right clone the entire plan so it starts from 0 again, but as many programmers I am lazy and expect features that give me complete control. Also, it becomes inaccurate again when we add a new stage like deploy to server instead of upload to repo (I know now there are Deploy plans for this).
As for normalization, if we have a daily build, it could more than a month to normalize, and also anytime someone breaks the build, if running through those takes a few cycles, it will make it deviate again.