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

A completed parallel branch isn't showing up as completed in karaoke mode

    XMLWordPrintable

Details

    • tasman

    Description

      In some cases when you have a parallel branch finish early, this won't show up as completed until the whole stage completes.

      Looking at the following recording:
      http://www.giphy.com/gifs/3oz8xtmarVuXWqfug0

      The right branch finishes after 1s, but doesn't show up as completed until I click on it.

      The pipeline to reproduce this:

      node {
          stage("first") {
              sh 'ping -c 3 www.apple.com'    
          }
          
          stage("second") {
              parallel (
                  "left" : {
                      sh 'ping -c 10 www.apple.com'            
                  }, 
                  "right" : {
                      sh 'ping -c 1 www.apple.com'    
                  }
                  )
              
          }
          
          stage("third") {
              sh 'ping -c 3 www.apple.com'    
          }
          
      }
      

      this sometimes does work. This also depends on the https://github.com/jenkinsci/blueocean-plugin/pull/557 being merged, which uses the new bismuth api.
      There is likely some front end code that can be simplified.

      Attachments

        Issue Links

          Activity

            michaelneale Michael Neale added a comment -

            tscherler I thought this is a nice one to finish off karaoke - a long standing thing which can now be addressed.

            michaelneale Michael Neale added a comment - tscherler I thought this is a nice one to finish off karaoke - a long standing thing which can now be addressed.
            michaelneale Michael Neale added a comment - svanoort is this likely related to: https://issues.jenkins-ci.org/browse/JENKINS-38536 (now we are using bismuth?) (see also: https://github.com/jenkinsci/blueocean-plugin/pull/557#issuecomment-252608032 )
            svanoort Sam Van Oort added a comment -

            michaelneale It probably is related. I've got a partial fix that is being wrapped up. Once done you should be able to bump the pipeline-graph analysis and workflow-api version and everything will be good.

            svanoort Sam Van Oort added a comment - michaelneale It probably is related. I've got a partial fix that is being wrapped up. Once done you should be able to bump the pipeline-graph analysis and workflow-api version and everything will be good.
            jamesdumay James Dumay added a comment -

            Just testing the example now with svanoorts fix

            jamesdumay James Dumay added a comment - Just testing the example now with svanoort s fix
            jamesdumay James Dumay added a comment -

            svanoort I did some testing and it looks like the 2.8-SNAPSHOT of workflow-api fixes this - nice one

            jamesdumay James Dumay added a comment - svanoort I did some testing and it looks like the 2.8-SNAPSHOT of workflow-api fixes this - nice one
            jamesdumay James Dumay added a comment -

            Thanks Sam

            jamesdumay James Dumay added a comment - Thanks Sam

            People

              svanoort Sam Van Oort
              michaelneale Michael Neale
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: