-
-
Notifications
You must be signed in to change notification settings - Fork 393
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
Local backend fails when using clone configuration #1931
Comments
SSH backend seems to have the same logic, and I suspect the same lack of support. |
With #1958 we dont need to guess if it's a clone step anymore ... the backend get's to know the types then too |
Was this solved by #2017? |
Uh most likely but i have to test |
yes it is ... but there looks to be a regression ... I'll close this and we can open a new issue if needed ... |
also "plugins" as in the example config will be supported by #2239 |
Thanks! #2239 definitely looks like an improvement :) |
Component
server
Describe the bug
When using a local backend and specifying a
clone
configuration, the clone step fails.This configuration:
Generates this error:
Looking through the backend led me to try using the constant string.
woodpecker/pipeline/backend/local/local.go
Lines 131 to 139 in 0cf602a
This does /not/ fail, but the settings are not honored nor supported.
System Info
Additional context
No response
Validations
next
version already [https://woodpecker-ci.org/faq#which-version-of-woodpecker-should-i-use]The text was updated successfully, but these errors were encountered: