[JIRA] [core] (JENKINS-21099) Don't give useless build time estimates by considering failed builds' durations

2 views
Skip to first unread message

dev@baltrinic.com (JIRA)

unread,
Aug 13, 2015, 8:57:01 AM8/13/15
to jenkinsc...@googlegroups.com
Kenneth Baltrinic edited a comment on Improvement JENKINS-21099
 
Re: Don't give useless build time estimates by considering failed builds' durations
I am generally in agreement with the perspective that failures are outliers and meaningless.  I believe that the algorithm should exclude failed builds.  However I wonder if this is something that can  1)  be made configurable (i.e. include failed builds: yes/no, include unstable builds: yes/no, average the past N qualifying builds).  Alternately could a plugin be created that would override the default behavior so that people can have some choice in what algorithm to use by installing the desired plugin?
Add Comment Add Comment
 
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
Atlassian logo

dev@baltrinic.com (JIRA)

unread,
Aug 13, 2015, 8:57:01 AM8/13/15
to jenkinsc...@googlegroups.com

dbeck@cloudbees.com (JIRA)

unread,
Apr 1, 2016, 10:12:03 AM4/1/16
to jenkinsc...@googlegroups.com

https://jenkins.ci.cloudbees.com/job/core/job/acceptance-test-harness-stable/buildTimeTrend

Builds #649, #650 have been running for just over an hour, and Jenkins says they are half done.

Tom FENNELLY is rightfully confused, because all successful (well, unstable) runs take 6-7 hours.

15:58 Tom Fennelly: not much more I can say until the tests run and we see the results
15:59 Daniel Beck: six hours from now?
15:58 Tom Fennelly: well the build on https://github.com/jenkinsci/acceptance-test-harness/pull/88 says less than 2 hours
15:59 Tom Fennelly: estimated remaining is 1 hour 8 mins

sverre.moe@gmail.com (JIRA)

unread,
Aug 5, 2019, 4:45:02 AM8/5/19
to jenkinsc...@googlegroups.com

An very old issue. Is there anyone who could do anything to implement this? We would like failed build to be excluded as well from the average calculation.

Perhaps a way to configure this would be preferable, so that it would work as before, but allow others to add excludes criteria.

This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)

adam.brousseau88@gmail.com (JIRA)

unread,
Apr 23, 2020, 1:29:02 PM4/23/20
to jenkinsc...@googlegroups.com

+1 for this.
Also related, perhaps needs a separate issue. For pipeline builds, I would like to see estimates take into account what stage the build is in. We use a "queue" stage at the start of a build for the time spent waiting for a machine. Queue time can range from seconds to hours and that really throws off the estimates for the remainder of the build. Even though the remaining stages are generally consistent for execution times.

This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
Atlassian logo
Reply all
Reply to author
Forward
0 new messages