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

Execution time of parallel blocks of in-flight jobs wrong

    Details

    • Similar Issues:

      Description

      Desired behaviour

      • Duration should be 20s for the whole pipeline.
      • ed1 node duration should be 20s
      • ed2 node duration should be 10s

      Undesired behaviour

      • Duration should be 20s for the whole pipeline.
      • ed1 node duration should be 20s
      • ed2 node duration should be 10s but is reported as 20s

      Example

      def map = [:]
      
      map['ed1'] = {
          node() {
              sleep 20
          }
      }
      
      map['ed2'] = {
          node() {
              sleep 10
          }
      }
      
      stage('Stage 1') {
          parallel map
      }
      

      Original request
      Hi,

      the execution time of a stage containing two parallel jobs shows, after the first job has finished, only the execution time of the first job, as long as the second job is running.
      After the second job has finished, the displayed time is updated to the right runtime.

      It would be nice if the time could be right during the execution of the job as well.

        Attachments

          Issue Links

            Activity

            Hide
            jiangty_addepar Damien Jiang added a comment -

            I created a new ticket to track my issue, which may be different from this one.

            Show
            jiangty_addepar Damien Jiang added a comment - I created a new ticket to track my issue, which may be different from this one.
            Hide
            jiangty_addepar Damien Jiang added a comment -

            See above comment; this issue is happening for us on the latest version of Blue Ocean.

            Show
            jiangty_addepar Damien Jiang added a comment - See above comment; this issue is happening for us on the latest version of Blue Ocean.
            Hide
            jiangty_addepar Damien Jiang added a comment -

            This problem seems to be occurring for us on a newer version of Blue Ocean (Jenkins Core 2.73.3, Blue Ocean 1.4.2 + dependencies, Pipeline 2.5, Pipeline: API 2.26).

            We have a parallel step where each of the individual nodes has a clearly different runtime, but Blue Ocean (and the Blue Ocean API) report all the parallel nodes as having roughly the same runtime (+/- a few ms).

            Show
            jiangty_addepar Damien Jiang added a comment - This problem seems to be occurring for us on a newer version of Blue Ocean (Jenkins Core 2.73.3, Blue Ocean 1.4.2 + dependencies, Pipeline 2.5, Pipeline: API 2.26). We have a parallel step where each of the individual nodes has a clearly different runtime, but Blue Ocean (and the Blue Ocean API) report all the parallel nodes as having roughly the same runtime (+/- a few ms).
            Hide
            svanoort Sam Van Oort added a comment -

            Sounds good to me

            Show
            svanoort Sam Van Oort added a comment - Sounds good to me
            Hide
            jamesdumay James Dumay added a comment -

            Sam Van Oort I am going to backport this dependency upgrade to our 1.1 branch so we don't have people confused about it.

            Show
            jamesdumay James Dumay added a comment - Sam Van Oort I am going to backport this dependency upgrade to our 1.1 branch so we don't have people confused about it.

              People

              • Assignee:
                svanoort Sam Van Oort
                Reporter:
                cri Cornelius Riemenschneider
              • Votes:
                4 Vote for this issue
                Watchers:
                11 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: