-
Bug
-
Resolution: Fixed
-
Minor
-
Jenkins 2.100. All other information in the support.zip
Since upgrading to Jenkins 2.100, all Jenkins Pipeline Jobs have started showing barber poles, and reporting the time left as N/A, despite some of them having run thousands of times, and should have plenty of run information to at least give some perspective on the time remaining.
As over 90% of our jobs now use pipeline or declarative pipeline, I thought that all jobs were experiencing the issue, however Freestyle projects seem to report their time remaining just fine
- is duplicated by
-
JENKINS-49616 Estimated time remaining NA
-
- Resolved
-
- is related to
-
JENKINS-48350 Cache estimated duration for execution
-
- Resolved
-
- links to
From the outside, it appears that https://build.kde.org/ may be experiencing the same issue. From my unauthenticated view, all jobs are reporting N/A , and they are also on Jenkins 2.101 and using many pipeline jobs building on external nodes. I just don't know if it is because I am unauthenticated which is the reason for me seeing N/A on all the jobs.