Good question - also, an option to "reset" this would be great, because overtime calculation goes completely wrong after significant changes to the build steps.
Good question - also, an option to "reset" this would be great, because overtime calculation goes completely wrong after significant changes to the build steps.
Actually, as I understand the question is not about overtime, but rather about build estimated time. Estimate is calculated as weighted average among builds in the history. Builds on the same agent has higher weights, also we are trying to detect spikes and remove them. As this is based on some heuristics in some cases estimation can be wrong. Usually when enough builds passed estimates become more reasonable. Anyway feel free to submit issue to our tracker for manual reset of estimates history.
Good question - also, an option to "reset" this would be great, because overtime calculation goes completely wrong after significant changes to the build steps.
C.
Good question - also, an option to "reset" this would be great, because overtime calculation goes completely wrong after significant changes to the build steps.
C.
Actually, as I understand the question is not about overtime, but rather about build estimated time. Estimate is calculated as weighted average among builds in the history. Builds on the same agent has higher weights, also we are trying to detect spikes and remove them. As this is based on some heuristics in some cases estimation can be wrong. Usually when enough builds passed estimates become more reasonable. Anyway feel free to submit issue to our tracker for manual reset of estimates history.