Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

stages with 'skipped due to earlier failure(s)' should have attribute or another status 2 #926

Open
sebEg opened this issue Aug 23, 2024 · 0 comments
Labels
enhancement New feature or request

Comments

@sebEg
Copy link

sebEg commented Aug 23, 2024

What feature do you want to see added?

Hi,

We are trying to use the plugin to find out where pipelines failed, similar to #281.
To make this easier, PR #283 already implemented to 'Use spanStatus "unset" rather than "ko" when interruption cause is parallel fail fast'.
However, later stages that are also 'skipped due to earlier failure(s)' are still marked with otel.status_code=ERROR.
I would expect that these stages also have the spanStatus "unset"?

In this example:

options { parallelsAlwaysFailFast() }
stages {
    stage('ze-parallel-stage') {
        parallel {
            stage('failingBranch') {
                steps {
                    error 'the failure'
                }
            }
            stage('parallelBranch1') {
                steps {
                    sleep 5
                }
            }
            stage('parallelBranch2') {
                steps {
                     sleep 5
                }
            }
            stage('parallelBranch3') {
                steps {
                    sleep 5
                }
            }
        }
    }
    stage('another stage') {
        steps {
            sleep 5
        }
    }
} 

I would expect that another stage has the same spanStatus as the parallelBranches, instead of otel.status_code=ERROR:

image

Upstream changes

No response

Are you interested in contributing this feature?

No response

@sebEg sebEg added the enhancement New feature or request label Aug 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant