Restarting a pipeline that failed due to missing secrets is not enough

woodpecker-ci / woodpecker

Woodpecker is a simple yet powerful CI/CD engine with great extensibility.

Apache License 2.0

3.94k stars 352 forks source link

server

Restarting a pipeline that failed due to missing secrets is not enough. I have seen it in a tag event.

secret "***" not found or not allowed to be used

Then I added the secret and restarted the pipeline and the error changed to

[generic]
pipeline definition not found

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

[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Checked that the bug isn't fixed in the next version already [https://woodpecker-ci.org/faq#which-version-of-woodpecker-should-i-use]
[X] Check that this is a concrete bug. For Q&A join our Discord Chat Server or the Matrix room.

I'm facing it too.

server

After fixing error (secrets permissions in my case) pipeline can't restart.

Commit and push with [skip ci] pipeline

skip_clone: true
steps:
test:
image: alpine
commands:
  - echo Hello
secrets:
  - retsec

Run pipeline manually
Get error [generic] secret "retsec" is not allowed to be used with pipeline event "manual"
Allow secret for manual event
Restart previously failed pipeline by clicking Restart button
Get error [generic] pipeline definition not found

After fixing secret's permissions, pipeline can be restarted successfully.

Woodpecker 2.6.0, Gitea 1.22.0, Kubernetes.

Can be reproduced with organization secret with push, manual and tagging. After allowing tag and restarting, it fails.

woodpecker-ci / woodpecker