[JIRA] (JENKINS-48879) User is trapped if a parallel stage is skipped. Blueocean shows "Waiting for run to start" instead of log messages.

3 views
Skip to first unread message

daniel.kurzynski@sap.com (JIRA)

unread,
Feb 16, 2018, 7:31:02 AM2/16/18
to jenkinsc...@googlegroups.com
Daniel Kurzynski updated an issue
 
Jenkins / Bug JENKINS-48879
User is trapped if a parallel stage is skipped. Blueocean shows "Waiting for run to start" instead of log messages.
Change By: Daniel Kurzynski
Summary: If User is trapped if a parallel stage is skipped blueocean . Blueocean shows "Waiting for run to start" instead of the other stage log messages.
Add Comment Add Comment
 
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
Atlassian logo

daniel.kurzynski@sap.com (JIRA)

unread,
Feb 16, 2018, 7:34:02 AM2/16/18
to jenkinsc...@googlegroups.com
Daniel Kurzynski updated an issue
In a pipeline with two parallel stages where one stage is skipped BlueOcean shows "Waiting for run to start", although the other stage produces log outputs. (See Waiting.PNG)

It seems like the skipped stage is selected by default. However, there is no output.

If there is an additional stage after the parallel stages and the pipeline reaches this stage, the pipeline is visualized properly. However, if you click on the skipped stage the message "Waiting for a run to start" is shown again. 

Steps to reproduce:

Execute the following pipeline:
{code:java}
pipeline {
    agent any
    options {
        timeout(time: 120, unit: 'MINUTES')
        timestamps()
        skipDefaultCheckout()
    }
    stages {
        stage('Parallel Stage') {
            parallel {
                stage("Executed Stage") {
                    steps {
                     script {
                     for(i=0; i< 100000 1000 ;i++){
                     echo "Temp"
                      sleep 1
                      }   
                     }
                    }
                }
                stage("Skipped Stage") {
                    when { expression { false } }
                    steps {
                     echo "I am skipped"    
                    }
                }
            }
        }
    }
}

{code}

jdumay@cloudbees.com (JIRA)

unread,
Feb 18, 2018, 7:51:27 PM2/18/18
to jenkinsc...@googlegroups.com
James Dumay updated an issue
Change By: James Dumay
Sprint: Blue Ocean 1.5 - beta 2

imeredith@cloudbees.com (JIRA)

unread,
Mar 7, 2018, 4:17:01 AM3/7/18
to jenkinsc...@googlegroups.com
Ivan Meredith assigned an issue to Ivan Meredith
Change By: Ivan Meredith
Assignee: Ivan Meredith

imeredith@cloudbees.com (JIRA)

unread,
Mar 7, 2018, 4:18:01 AM3/7/18
to jenkinsc...@googlegroups.com
Ivan Meredith started work on Bug JENKINS-48879
 
Change By: Ivan Meredith
Status: Open In Progress

imeredith@cloudbees.com (JIRA)

unread,
Mar 7, 2018, 6:47:03 AM3/7/18
to jenkinsc...@googlegroups.com
Ivan Meredith commented on Bug JENKINS-48879
 
Re: User is trapped if a parallel stage is skipped. Blueocean shows "Waiting for run to start" instead of log messages.

Vivek Panday There is an issue in the rest api. While the stages are executing PIpelineStepVisitor.currentStage is always set to be a stage that is skipped for conditional. therefore it does not add any steps. But if you cancel the job, this is no longer the case. I'm stuck on this, I don't know enough about how this works.

imeredith@cloudbees.com (JIRA)

unread,
Mar 7, 2018, 6:49:04 AM3/7/18
to jenkinsc...@googlegroups.com

Sam Van Oort Not sure if you can help here, I noticed your name on StandardChunkVisitor  

 

Its always skipped at https://github.com/jenkinsci/blueocean-plugin/blob/master/blueocean-pipeline-api-impl/src/main/java/io/jenkins/blueocean/rest/impl/pipeline/PipelineStepVisitor.java#L159 , the debugger never hits the next line

imeredith@cloudbees.com (JIRA)

unread,
Mar 7, 2018, 4:40:03 PM3/7/18
to jenkinsc...@googlegroups.com
Ivan Meredith assigned an issue to Vivek Panday
 
Change By: Ivan Meredith
Assignee: Ivan Meredith Vivek Panday

imeredith@cloudbees.com (JIRA)

unread,
Mar 7, 2018, 8:00:03 PM3/7/18
to jenkinsc...@googlegroups.com
Ivan Meredith assigned an issue to Ivan Meredith
Change By: Ivan Meredith
Assignee: Vivek Panday Ivan Meredith

imeredith@cloudbees.com (JIRA)

unread,
Mar 7, 2018, 8:00:06 PM3/7/18
to jenkinsc...@googlegroups.com
Ivan Meredith assigned an issue to Vivek Pandey
Change By: Ivan Meredith
Assignee: Ivan Meredith Vivek Pandey

vivek.pandey@gmail.com (JIRA)

unread,
Mar 12, 2018, 4:58:02 PM3/12/18
to jenkinsc...@googlegroups.com
Vivek Pandey updated an issue
Change By: Vivek Pandey
Sprint: Blue Ocean 1.5 - beta 2 3

vivek.pandey@gmail.com (JIRA)

unread,
Apr 2, 2018, 9:13:03 PM4/2/18
to jenkinsc...@googlegroups.com
Vivek Pandey updated an issue
Change By: Vivek Pandey
Sprint: Blue Ocean 1. 5 6 - beta 3 1

vivek.pandey@gmail.com (JIRA)

unread,
Apr 17, 2018, 2:51:03 PM4/17/18
to jenkinsc...@googlegroups.com
Vivek Pandey updated an issue
Change By: Vivek Pandey
Sprint: Blue Ocean 1.6 - beta 1 2

vivek.pandey@gmail.com (JIRA)

unread,
May 21, 2018, 9:11:19 PM5/21/18
to jenkinsc...@googlegroups.com
Vivek Pandey updated an issue
Change By: Vivek Pandey
Sprint: Blue Ocean 1.6 - beta 2 , Blue Ocean - 1.6 - beta 4

vivek.pandey@gmail.com (JIRA)

unread,
May 29, 2018, 7:12:03 PM5/29/18
to jenkinsc...@googlegroups.com
Vivek Pandey stopped work on Bug JENKINS-48879
 
Change By: Vivek Pandey
Status: In Progress Open

vivek.pandey@gmail.com (JIRA)

unread,
May 29, 2018, 7:12:05 PM5/29/18
to jenkinsc...@googlegroups.com
Vivek Pandey assigned an issue to Unassigned
Change By: Vivek Pandey
Assignee: Vivek Pandey

william.daniel.laszlo@gmail.com (JIRA)

unread,
Nov 2, 2018, 5:01:03 AM11/2/18
to jenkinsc...@googlegroups.com
William Laszlo updated an issue
Change By: William Laszlo
Attachment: wariting-for-run.png
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)

william.daniel.laszlo@gmail.com (JIRA)

unread,
Nov 2, 2018, 5:02:02 AM11/2/18
to jenkinsc...@googlegroups.com

dawn@ravenswurk.frl (JIRA)

unread,
Nov 23, 2018, 5:05:02 AM11/23/18
to jenkinsc...@googlegroups.com

Still present in Blue Ocean 1.9.0. Really annoying being unable to see how our parallel stages are doing when one is skipped, have to resort to sifting through the classic console logs. 

 

shamil.si@gmail.com (JIRA)

unread,
Mar 14, 2019, 8:14:03 PM3/14/19
to jenkinsc...@googlegroups.com

Blue Ocean 1.13. The issue still present

daniel@velo3d.com (JIRA)

unread,
Mar 14, 2019, 8:21:09 PM3/14/19
to jenkinsc...@googlegroups.com

A hack that works for us is to add an always active stage that is alphabetically last. That doesn't seem consistent with William Laszlo's post though.

artur.czarnota@ims-gmbh.de (JIRA)

unread,
May 4, 2020, 8:32:05 AM5/4/20
to jenkinsc...@googlegroups.com

Still reproducible with Jenkins 2.222.1 and Blue Ocean 1.22.0
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
Atlassian logo
Reply all
Reply to author
Forward
0 new messages