woodpecker: Don't fail on missing CI config
Component
server
Describe the bug
Not necessarily all branches of a repository are intended to have a CI config. But branches without a CI config will always create an error in the UI.
In the past, I was able to work around this issue by adding [skip ci] to all commits to branches without a CI config. This is now also broken, see https://github.com/woodpecker-ci/woodpecker/pull/2216.
My suggestion would be to simply ignore missing CI configurations, or at least not create a failed pipeline in the UI. Alternatively, users should have the option to ignore branches. A common example would be github-pages branches, where only page artifacts are published and no CI configuration.
System Info
{"source":"https://github.com/woodpecker-ci/woodpecker","version":"next-06d1f3c92e"}
Additional context
No response
Validations
- Read the Contributing Guidelines.
- 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
nextversion already [https://woodpecker-ci.org/faq#which-version-of-woodpecker-should-i-use] - Check that this is a concrete bug. For Q&A join our Discord Chat Server or the Matrix room.
About this issue
- Original URL
- State: closed
- Created 10 months ago
- Reactions: 2
- Comments: 17 (16 by maintainers)
Ok so i would say: if the forge report no found we ignore, if its any other error we show error config fetch failed 😃
Recently started using a pretty large project with Woodpecker and experiencing this again. I get errors for a lot of branches, PRs, … all of them because there is no Woodpecker config. I guess skipping those pipeline as almost all other CI systems do it would be the best here.
added the label
breakingto it for nowComparing to other CI systems it is normally ignoring webhooks as long as there is no config, so I think it would be fine if woodpecker does so as well. We have to check if it could be a breaking change for someone however