[JIRA] (JENKINS-57929) BlueOcean steps do not appear green when they were successful when using parallel stages while still running

0 views
Skip to first unread message

block.jon@gmail.com (JIRA)

unread,
Jun 10, 2019, 1:50:02 AM6/10/19
to jenkinsc...@googlegroups.com
Jon B updated an issue
 
Jenkins / Bug JENKINS-57929
BlueOcean steps do not appear green when they were successful when using parallel stages while still running
Change By: Jon B
Summary: BlueOcean steps do not appear green when they were successful when using parallel stages while still running
Add Comment Add Comment
 
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)

dnusbaum@cloudbees.com (JIRA)

unread,
Jun 11, 2019, 3:32:02 PM6/11/19
to jenkinsc...@googlegroups.com

dnusbaum@cloudbees.com (JIRA)

unread,
Jun 11, 2019, 3:32:02 PM6/11/19
to jenkinsc...@googlegroups.com
Devin Nusbaum commented on Bug JENKINS-57929
 
Re: BlueOcean steps do not appear green when they were successful when using parallel stages while still running

Spent a bit of time trying to reproduce this in case it was related to my changes for JENKINS-39203, but was not able to do so. Here is the Pipeline I was using:

pipeline {
    agent any
    stages {
        stage('before') {
            steps {
                echo 'before'
            }
        }
        stage("parallel") {
            parallel {
                stage("simple") {
                    stages {
                        stage ("simple-inner?") {
                            steps {
                                echo 'simple-inner?'
                                sleep 1
                            }
                        }
                    }
                }
                stage("sequential") {
                    stages {
                        stage("sequential-1") {
                           steps {
                                echo 'sequential-1'
                                sleep 1
                            }
                        }
                        stage("sequential-2") {
                           steps {
                                echo 'sequential-2'
                                sleep 1
                            }
                        }
                    }
                }
            }
        }
        stage('after') {
            parallel {
                stage('after-1') {
                    steps {
                        sleep 60
                    }       
                }
                stage('after-2') {
                    steps {
                        echo 'after-2'
                    }       
                }
            }
        }
    }
}

And here is what it looked like:

Jon B If you can figure out how to reproduce the problem with tweaks to my basic Pipeline here, that would be helpful. From what I can tell, it looks like what you are reporting might be a dupe of JENKINS-53816, see in particular this comment which notes some problems in this area in Blue Ocean 1.17.0.

block.jon@gmail.com (JIRA)

unread,
Jun 19, 2019, 3:37:02 PM6/19/19
to jenkinsc...@googlegroups.com

block.jon@gmail.com (JIRA)

unread,
Jun 25, 2019, 5:19:02 AM6/25/19
to jenkinsc...@googlegroups.com
Jon B commented on Bug JENKINS-57929

Here's a clue: I use declarative jenkins pipelines.. however, the "testing" stage calls to a script{} block and inside of there is some groovy scripting that uses the "parallel" command in order to fire a bunch of jobs in parallel.

The defect appears to be that the jenkins declarative parallel build steps dont know how to play nice with groovy scripting that calls for parallel jobs to run.

Interesting that usually when the pipeline is completely finished that things tend to render correctly.. they just dont render correctly while its running causing confusion to the developers who are trying to make sense of whats going on.

dnusbaum@cloudbees.com (JIRA)

unread,
Jun 25, 2019, 9:29:02 AM6/25/19
to jenkinsc...@googlegroups.com

the "testing" stage calls to a script{} block and inside of there is some groovy scripting that uses the "parallel" command in order to fire a bunch of jobs in parallel

Ah ok, yeah running stages/parallel blocks inside of script blocks in a Declarative Pipeline generally breaks the visualization, so I'm surprised that it ends up working once the build is complete. Fixing this is probably nontrivial, and might require some substantial changes to the graph generation code in Blue Ocean.

block.jon@gmail.com (JIRA)

unread,
Jul 2, 2019, 1:03:03 PM7/2/19
to jenkinsc...@googlegroups.com
Jon B commented on Bug JENKINS-57929

We have a massive jenkins installation and the overwhelming majority of our jenkins pipeline users use declarative scripts and then they use script blocks to call out to subfunctions. Since parallelization is essential, we have a lof of cases where the pipelines UI rendering is messed up

From my vantage point, you absolutely need to change that graph algo to be able to render for this case.

block.jon@gmail.com (JIRA)

unread,
Jul 2, 2019, 5:17:02 PM7/2/19
to jenkinsc...@googlegroups.com
Jon B edited a comment on Bug JENKINS-57929
We have a massive jenkins installation and the overwhelming majority of our jenkins pipeline users use declarative scripts and then they use script blocks to call out to subfunctions . Since parallelization is essential, we that often have a lof of their own parallel steps. In these cases where the pipelines UI rendering is messed up .

From my vantage point, you absolutely need to change that graph algo to be able to render
for this case correctly when declarative and scripted parallel steps are mixed .
Reply all
Reply to author
Forward
0 new messages