-
Improvement
-
Resolution: Unresolved
-
Minor
Jenkins's time estimate for jobs looks wrong.
On the screenshot attached, you can see that the estimate is of 3h, but just by looking at the estimate for each step of my build, I know it will be much less.
I think the estimate is currently computed as the mean of all (successful ?) builds.
I believe it would be better to estimate it based on the estimated time of the remaining steps.
In the case that a build step goes faster (part of the build cached from last run), the estimate will be much more precise
[JENKINS-67259] Jenkins time estimation
Francois Michaut
created issue -
Francois Michaut
made changes -
| Description |
Original:
Jenkins's time estimate for jobs looks wrong.
On the screen attached, you can see that the estimate is of 3h, but just by looking at the estimate for each step of my build, I know it will be much less. I think the estimate is currently computed as the mean of all (successful ?) builds. I believe it would be better to estimate it based on the estimated time of the remaining steps. In the case that a build step goes faster (part of the build cached from last run), the estimate will be much more precise |
New:
Jenkins's time estimate for jobs looks wrong.
On the screenshot attached, you can see that the estimate is of 3h, but just by looking at the estimate for each step of my build, I know it will be much less. I think the estimate is currently computed as the mean of all (successful ?) builds. I believe it would be better to estimate it based on the estimated time of the remaining steps. In the case that a build step goes faster (part of the build cached from last run), the estimate will be much more precise |
Francois Michaut
made changes -
| Component/s | New: pipeline-stage-view-plugin [ 21139 ] |