[JIRA] (JENKINS-52005) catchError should give a visual hint in which stage the error occurred

16 views
Skip to first unread message

kutzi@gmx.de (JIRA)

unread,
Jun 18, 2018, 8:52:04 AM6/18/18
to jenkinsc...@googlegroups.com
kutzi created an issue
 
Jenkins / Bug JENKINS-52005
catchError should give a visual hint in which stage the error occurred
Issue Type: Bug Bug
Assignee: Unassigned
Components: blueocean-plugin
Created: 2018-06-18 12:51
Priority: Minor Minor
Reporter: kutzi

When using catchError in a stage and the steps in catchError fail, then no visual feedback on the pipeline view is given in which stage it failed. You have to click on each individual stage to find the bad one.

It would be better if the stage would be rendered red as for normal failures
Add Comment Add Comment
 
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
Atlassian logo

rodrigc@FreeBSD.org (JIRA)

unread,
May 9, 2019, 8:08:01 PM5/9/19
to jenkinsc...@googlegroups.com
Craig Rodrigues updated an issue
Change By: Craig Rodrigues
Attachment: bad_nodes.png
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)

rodrigc@FreeBSD.org (JIRA)

unread,
May 9, 2019, 8:08:02 PM5/9/19
to jenkinsc...@googlegroups.com
Craig Rodrigues commented on Bug JENKINS-52005
 
Re: catchError should give a visual hint in which stage the error occurred

I can reproduce this problem with this pipeline:

pipeline {
    agent any
    
    stages {
        stage("Remove file which does not exist") {
            steps {
               catchError {
                    sh("rm /nonexistent")
                }
            }
        }
        
        stage("Hello!") {
            steps {
                sh("echo Hello1")
            }
        }
    }
}

rodrigc@FreeBSD.org (JIRA)

unread,
May 9, 2019, 8:09:02 PM5/9/19
to jenkinsc...@googlegroups.com
Craig Rodrigues edited a comment on Bug JENKINS-52005
I can reproduce this problem with this pipeline:

{noformat}

pipeline {
    agent any
    
    stages {
        stage("Remove file which does not exist") {
            steps {
               catchError {
                    sh("rm /nonexistent")
                }
            }
        }
        
        stage("Hello!") {
            steps {
                sh("echo Hello1")
            }
        }
    }
}
{noformat}

!bad_nodes.png|thumbnail!


The *Remove file which does not exist* node should be red, but it is green.

lividfaust@gmail.com (JIRA)

unread,
Jun 27, 2019, 9:06:02 AM6/27/19
to jenkinsc...@googlegroups.com
Alexandr Semak updated an issue
 
Change By: Alexandr Semak
Attachment: Screen Shot 2019-06-27 at 4.02.19 PM.png
Attachment: Screen Shot 2019-06-27 at 4.02.56 PM.png

lividfaust@gmail.com (JIRA)

unread,
Jun 27, 2019, 9:06:03 AM6/27/19
to jenkinsc...@googlegroups.com
Alexandr Semak commented on Bug JENKINS-52005
 
Re: catchError should give a visual hint in which stage the error occurred 
node {
    stage("successful"){
        echo "successful stage"
    }
    stage("unstable"){
        catchError(buildResult: 'SUCCESS', stageResult: 'UNSTABLE'){
            sh "gooo version"
        }
    }
    stage("continue working"){
        echo "continue working"
    }
}

I also have this is issue.
Jenkins v2.164.3 already installer doesn't work if I update Basic Steps but when I was testing on new spiup Jenkins with the same version 2.164.3 it is work

lividfaust@gmail.com (JIRA)

unread,
Jun 27, 2019, 9:07:02 AM6/27/19
to jenkinsc...@googlegroups.com
Alexandr Semak updated an issue
Change By: Alexandr Semak
Priority: Minor Major

lividfaust@gmail.com (JIRA)

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

node {
    stage("successful"){
        echo "successful stage"
    }
    stage("unstable"){
        catchError(buildResult: 'SUCCESS', stageResult: 'UNSTABLE'){
            sh "gooo version"
        }
    }
    stage("continue working"){
        echo "continue working"
    }
}
{code}
I also have this is issue.
Jenkins v2.164.3 (Basic Steps 2.18) already installer doesn't work if I update Basic Steps but when I was testing on new spiup Jenkins with the same version 2.164.3 it is work
!Screen Shot 2019-06-27 at 4.02.19 PM.png|thumbnail!  !Screen Shot 2019-06-27 at 4.02.56 PM.png|thumbnail!

anupama.j01@gmail.com (JIRA)

unread,
Apr 8, 2020, 11:01:03 PM4/8/20
to jenkinsc...@googlegroups.com

having the same problem. Stage fails , but doesn't show up in OpenBlueOcean visualization.  Post stage action failure{} gets executed giving a hint that currentBuild.Result = FAILURE, but interestingly the following stages get executed while not expected to do so.
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
Atlassian logo
Reply all
Reply to author
Forward
0 new messages