Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-48821

Time remaining for all pipeline jobs is N/A

    XMLWordPrintable

    Details

    • Similar Issues:

      Description

      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

        Attachments

          Issue Links

            Activity

            Hide
            starfire_ Andreas Tscharner added a comment -

            This error also appears in 2.89.4

            Show
            starfire_ Andreas Tscharner added a comment - This error also appears in 2.89.4
            Show
            oleg_nenashev Oleg Nenashev added a comment - https://github.com/jenkinsci/jenkins/pull/3329
            Hide
            scm_issue_link SCM/JIRA link daemon added a comment -

            Code changed in jenkins
            User: Berno Langer
            Path:
            core/src/main/java/hudson/model/Executor.java
            http://jenkins-ci.org/commit/jenkins/3fc392108ae382a4616964aa8bbb6b8cb9dff0dc
            Log:
            JENKINS-48821 - Don't forget estimated duration of asynchronous jobs (#3329)

            • Don't forget estimated duration of asynchronous jobs.

            When jobs are executed, the estimated duration is calculated, memorized
            and reseted when the job is finished.

            But when the job is executed asynchronously (e.g. as for pipeline
            scripts), the execution is just triggered. Therefore the estimated
            duration should remain - and not be reseted after triggering.

            JENKINS-48821: Time remaining for all pipeline jobs is N/A
            JENKINS-49616: Estimated time remaining NA

            • Reset cached estimated duration also when asynchronous job ends.
            Show
            scm_issue_link SCM/JIRA link daemon added a comment - Code changed in jenkins User: Berno Langer Path: core/src/main/java/hudson/model/Executor.java http://jenkins-ci.org/commit/jenkins/3fc392108ae382a4616964aa8bbb6b8cb9dff0dc Log: JENKINS-48821 - Don't forget estimated duration of asynchronous jobs (#3329) Don't forget estimated duration of asynchronous jobs. When jobs are executed, the estimated duration is calculated, memorized and reseted when the job is finished. But when the job is executed asynchronously (e.g. as for pipeline scripts), the execution is just triggered. Therefore the estimated duration should remain - and not be reseted after triggering. JENKINS-48821 : Time remaining for all pipeline jobs is N/A JENKINS-49616 : Estimated time remaining NA Reset cached estimated duration also when asynchronous job ends.
            Hide
            oleg_nenashev Oleg Nenashev added a comment -

            The patch has been integrated towards 2.111

            Show
            oleg_nenashev Oleg Nenashev added a comment - The patch has been integrated towards 2.111
            Hide
            scm_issue_link SCM/JIRA link daemon added a comment -

            Code changed in jenkins
            User: Berno Langer
            Path:
            core/src/main/java/hudson/model/Executor.java
            http://jenkins-ci.org/commit/jenkins/1400918ddaef45470720e60d4d1dbfd2f6ac78d4
            Log:
            JENKINS-48821 - Don't forget estimated duration of asynchronous jobs (#3329)

            • Don't forget estimated duration of asynchronous jobs.

            When jobs are executed, the estimated duration is calculated, memorized
            and reseted when the job is finished.

            But when the job is executed asynchronously (e.g. as for pipeline
            scripts), the execution is just triggered. Therefore the estimated
            duration should remain - and not be reseted after triggering.

            JENKINS-48821: Time remaining for all pipeline jobs is N/A
            JENKINS-49616: Estimated time remaining NA

            • Reset cached estimated duration also when asynchronous job ends.

            (cherry picked from commit 3fc392108ae382a4616964aa8bbb6b8cb9dff0dc)

            Show
            scm_issue_link SCM/JIRA link daemon added a comment - Code changed in jenkins User: Berno Langer Path: core/src/main/java/hudson/model/Executor.java http://jenkins-ci.org/commit/jenkins/1400918ddaef45470720e60d4d1dbfd2f6ac78d4 Log: JENKINS-48821 - Don't forget estimated duration of asynchronous jobs (#3329) Don't forget estimated duration of asynchronous jobs. When jobs are executed, the estimated duration is calculated, memorized and reseted when the job is finished. But when the job is executed asynchronously (e.g. as for pipeline scripts), the execution is just triggered. Therefore the estimated duration should remain - and not be reseted after triggering. JENKINS-48821 : Time remaining for all pipeline jobs is N/A JENKINS-49616 : Estimated time remaining NA Reset cached estimated duration also when asynchronous job ends. (cherry picked from commit 3fc392108ae382a4616964aa8bbb6b8cb9dff0dc)

              People

              • Assignee:
                blanger Berno Langer
                Reporter:
                tomlarrow Tom Larrow
              • Votes:
                3 Vote for this issue
                Watchers:
                13 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: