Closed xoxys closed 1 month ago
related #1871 #1893
It gets even worse. Even if the pipeline status is correct in the UI, CI_PIPELINE_STATUS
is wrong, which makes it pretty useless to use for notifications :see_no_evil:
while CI_PIPELINE_STATUS
has reported success
during a notification step
Maybe related. Pipeline is already show as error, but is still running and no steps has an error 🤔 https://ci.woodpecker-ci.org/repos/3780/pipeline/9551
Step failed, but pipeline was marked as successful: https://ci.woodpecker-ci.org/repos/3780/pipeline/13542
Found another interesting status mismatch: https://ci.woodpecker-ci.org/repos/3780/pipeline/14498
I think this line could be the issue: https://github.com/woodpecker-ci/woodpecker/blob/2bda19024ece0bf0deab5244fb8799f653d5adfc/agent/runner.go#L168
In case of a canceled workflow the error is set to ""
(no error). The configured exit code doesn't seem to be considered by any logic at all and is only used for logging: #3848
Component
server
Describe the bug
Pipeline status for cancelled pipeline is wrong:
System Info