[JIRA] (JENKINS-49131) Steps are not shown up in Blue Ocean when one of parallel stages is skipped due to "when" condition

6 views
Skip to first unread message

mvh1976@gmail.com (JIRA)

unread,
May 9, 2018, 1:26:03 PM5/9/18
to jenkinsc...@googlegroups.com
Michael Haskelsky assigned an issue to Michael Haskelsky
 
Jenkins / Bug JENKINS-49131
Steps are not shown up in Blue Ocean when one of parallel stages is skipped due to "when" condition
Change By: Michael Haskelsky
Assignee: Michael Haskelsky
Add Comment Add Comment
 
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
Atlassian logo

mvh1976@gmail.com (JIRA)

unread,
May 9, 2018, 1:26:03 PM5/9/18
to jenkinsc...@googlegroups.com
Michael Haskelsky updated an issue
Change By: Michael Haskelsky
Summary: Steps are not shown up in Blue Ocean when one of parallel stages is not active skipped due to "when" condition

mvh1976@gmail.com (JIRA)

unread,
May 9, 2018, 1:27:02 PM5/9/18
to jenkinsc...@googlegroups.com
Michael Haskelsky assigned an issue to Unassigned
Change By: Michael Haskelsky
Assignee: Michael Haskelsky

mvh1976@gmail.com (JIRA)

unread,
May 9, 2018, 1:28:02 PM5/9/18
to jenkinsc...@googlegroups.com
Michael Haskelsky updated an issue
1. If one (or more) parallel stage does not run  is skipped due to "when" condition in declarative pipeline, Blue Ocean UI does not show up running steps inside active stages until all steps in all active stages are finished.

2. In such case If one of steps is "input" step, there is no option to "Proceed" or "Abort" using Blue Ocean UI since no steps are shown up. It can be done only using regular UI or console output.

3. If all stages are active, steps are shown up, but it is impossible to switch between output of "Stage A" to "Stage B" and see steps of "Stage B" until all steps in "Stage A" are finished.

Example:
{code:java}
// code placeholder
pipeline {
agent any
parameters {
  choice(choices: 'NO\nEVEN\nODD', description: '', name: 'A')
  choice(choices: 'NO\nEVEN\nODD', description: '', name: 'B')
}
environment {
  A = "${params.A}"
  B = "${params.B}"
}
stages {
  stage('ParallelStages') {
   parallel {
    stage('Stage A') {
     when {
      anyOf {
       environment name: 'A', value: 'EVEN'
       environment name: 'A', value: 'ODD'
      }
     }
    steps {
     echo "Running Stage A"
     sleep 10
     echo "Finishing Stage A"
    }
   }
   stage('Stage B') {
    when {
     anyOf {
      environment name: 'B', value: 'EVEN'
      environment name: 'B', value: 'ODD'
     }
    }
    steps {
     echo "Running Stage B"
     sleep 30
     echo "Finishing Stage B"
     }
    }
   }
  }
}
}
{code}
 

 

mvh1976@gmail.com (JIRA)

unread,
May 15, 2018, 10:07:07 AM5/15/18
to jenkinsc...@googlegroups.com
Michael Haskelsky updated an issue
1. If one (or more) parallel stage is skipped due to "when" condition in declarative pipeline, Blue Ocean UI does not show up running steps inside active stages until all steps in all active stages are finished.


2. In such case If one of steps is "input" step, there is no option to "Proceed" or "Abort" using Blue Ocean UI since no steps are shown up. It can be done only using regular UI or console output.

3. If all stages are active, steps are shown up, but sometimes it is impossible to switch between output of "Stage A" to "Stage B" and see steps of "Stage B" until all steps in "Stage A" are finished. Refreshing page in browser (F5) allows switching between stages for some time.

mvh1976@gmail.com (JIRA)

unread,
May 15, 2018, 10:08:01 AM5/15/18
to jenkinsc...@googlegroups.com
Michael Haskelsky updated an issue
1. If one (or more) parallel stage is skipped due to "when" condition in declarative pipeline, Blue Ocean UI does not show up running steps inside active stages until all steps in all active stages are finished.

2. In such case If one of steps is "input" step, there is no option to "Proceed" or "Abort" using Blue Ocean UI since no steps are shown up. It can be done only using regular UI or console output.

3. If all stages are active, steps are shown up, but sometimes after some time it is impossible to switch between output of "Stage A" to "Stage B" and see steps of "Stage B" until all steps in "Stage A" are finished. Refreshing page in browser (F5) allows switching between stages for some time.

daniel.platz@me.com (JIRA)

unread,
Jun 27, 2018, 7:09:01 AM6/27/18
to jenkinsc...@googlegroups.com
Daniel Platz commented on Bug JENKINS-49131
 
Re: Steps are not shown up in Blue Ocean when one of parallel stages is skipped due to "when" condition

 Any update on this one? I am seeing the exact same issue on latest Jenkins builds (Jenkins (2.129)).
This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)

pietropaoloferrari@gmail.com (JIRA)

unread,
Oct 17, 2018, 7:04:01 AM10/17/18
to jenkinsc...@googlegroups.com

I am seeing the exact same issue too. 
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)

kacik.jan@outlook.com (JIRA)

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

We are too experiencing this.

kacik.jan@outlook.com (JIRA)

unread,
Nov 9, 2018, 5:29:01 AM11/9/18
to jenkinsc...@googlegroups.com
Jan Kacik edited a comment on Bug JENKINS-49131
We are too experiencing this . on the latest LTS and plugins

chris.ladd@teradata.com (JIRA)

unread,
Mar 27, 2019, 3:56:03 PM3/27/19
to jenkinsc...@googlegroups.com
Chris Ladd updated an issue
 
Change By: Chris Ladd
Priority: Major Critical

chris.ladd@teradata.com (JIRA)

unread,
Mar 27, 2019, 3:59:03 PM3/27/19
to jenkinsc...@googlegroups.com

chris.ladd@teradata.com (JIRA)

unread,
Mar 27, 2019, 4:00:02 PM3/27/19
to jenkinsc...@googlegroups.com
Chris Ladd updated an issue
Change By: Chris Ladd
Environment: Jenkins ver. 2.89.3
Blueocean 1.4.0
Windows Server 2012 R2

Jenkins 2.138.3
Blue Ocean 1.14.0
Linux

egraebert@palantir.com (JIRA)

unread,
Aug 7, 2019, 2:53:03 PM8/7/19
to jenkinsc...@googlegroups.com
Elliot Graebert commented on Bug JENKINS-49131
 
Re: Steps are not shown up in Blue Ocean when one of parallel stages is skipped due to "when" condition

Hey folks, I'm seeing this, and it wasn't directly tied. The symptom is very similar: steps don't get populated until after the stage is done. It really ruins the Blue Ocean experience.

 

Jenkins 2.187 and Blue Ocean 1.18.0

egraebert@palantir.com (JIRA)

unread,
Aug 7, 2019, 2:54:02 PM8/7/19
to jenkinsc...@googlegroups.com
Elliot Graebert edited a comment on Bug JENKINS-49131
Hey folks, I'm seeing this, and it wasn't directly tied. The symptom is very similar: steps don't get populated until after the stage is done. It really ruins the Blue Ocean experience , as people just see blank stages . If those stages indicated a problem downstream that needs investigation, they have to check the artifact logs to figure it out.

 

Jenkins 2.187 and Blue Ocean 1.18.0

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