Gitlab: Cannot transition status via :enqueue from :pending

[lukashass]

Component

server

Describe the bug

Gitlab jobs show the following error:

{"level":"error","error":"POST https://git.redacted/api/v4/projects/89/statuses/redacted: 400 {message: Cannot transition status via :enqueue from :running (Reason(s): Status cannot transition via \"enqueue\")}","time":"2024-08-29T14:22:18Z","message":"error setting commit status for redacted/redacted/redacted"}
{"level":"error","error":"POST https://git.redacted/api/v4/projects/89/statuses/redacted: 400 {message: Cannot transition status via :enqueue from :pending (Reason(s): Status cannot transition via \"enqueue\")}","time":"2024-08-29T14:26:51Z","message":"error setting commit status for redacted/redacted/redacted"}

Steps to reproduce

1. Updated to next
2. Run a Gitlab pipeline

Expected behavior

No response

System Info

{"source":"https://github.com/woodpecker-ci/woodpecker","version":"next-42e7d71680"}

Additional context

No response

Validations

• Read the docs.
• Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
• Checked that the bug isn't fixed in the next version already [https://woodpecker-ci.org/faq#which-version-of-woodpecker-should-i-use]

[lukashass]

runatlantis/atlantis#1971

[pat-s]

I had a closer look at this.

The underlying issue is that GL cannot update a pipeline status with the same status it is already in.

I also tried the fix from atlantis - however, even when changing pending/running (or only use running), the error still persists as some part of the WP is trying to change a pipeline state to the same value it is already in.
I assume this might be coming from matrix workflows or similar.

FWIW this error is not of any harm as everything else continues to work as intended - and likely also hard to fix as only GL complains about it and fixing it would likely require a rewrite of some pipeline status update logic when then would maybe break other forges.