-
-
Notifications
You must be signed in to change notification settings - Fork 378
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
Pipeline stucks for kubernetes if image is invalid #3856
Comments
In regard Kubernets backend, probably, wider range of statuses should be hacked (#3580). |
Not sure, but this seems to be a yaml issue. AFAIK docker backend tells you if it fails to pull the image, or do you only specifically about kubernetes? |
It is. It is only a part. Second is the Server's checks/linter. And third is Kube backend.
Cool :) Kubernetes stucks.
There, where backend is meant, yes, I'm about Kubernetes backend, cause I have no other backends. #3909 could have fixed the Server part. Schema is right, but there are no checks for commands and entrypoint steps. |
well your yaml is parsed: skip_clone: true
when:
- event:
- 'manual'
steps:
hello:
image: 'alpine - echo Hello - echo world' so the error that the image is invalid is fine! how should the linter know if it is not a plugin and misses commands ?!? |
Absolutely, if pipeline fails (third part).
I thought, that plugin uses
However, we check volume/pod/service names in Kube backend. Some regexp could be introduced for image check in the server. |
well that's an enhancement proposal :) #3919 |
What about
? What if I am just user without access to the cluster? |
uh missed that, this is another issue! |
Component
server
Describe the bug
When the one forgot
commands
directive, then they join toimage
=> image cannot be pulled, pipeline stucks.Steps to reproduce
Screenshot 2024-06-29 1
Screenshot 2024-06-29 2
Screenshot 2024-06-29 3
Screenshot 2024-06-29 4
Expected behavior
Pipeline should fail and linter should warn about missed
commands
as well.System Info
`2.6.0`, Kubernetes
Additional context
woodpecker-server.log
woodpecker-agent.log
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: