-
Notifications
You must be signed in to change notification settings - Fork 8
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
Show the error message why it has failed or at least show the pipeline URL just like running locally #17
Comments
@kkweon could you try to set the |
https://github.com/codingpot/pr12er/runs/3671096358?check_suite_focus=true That was the first thing i tried but didn't work. The name is not required unlike its description. I've been using without a name for several months already. That's another bug too. |
In the logs it says:
I don't think it is getting the name parameter properly. |
push- is the name https://github.com/codingpot/pr12er/actions/runs/1260313992/workflow - uses: okteto/pipeline@master
with:
name: push-${{ github.event.number }} it's just the event number didn't get propagated because i triggered manually. |
Oh, I see. Did you try when it runs automatically? I think it is going to work |
I'm pretty positive that it wouldn't work. |
Just to be clear, the issue here is about an error message rather than debugging my issue (which will be resolved naturally if there's a clear error message). |
|
thank you. it indeed resolve the issue. is there a documentation on what a valid name is? if not, that would be the second feature request. |
We will add it to the docs, but they have the same restrictions than kubernetes labels: |
I'm also seeing the same error message as in #14, but the thing is that error message doesn't help.
It simply says
It doesn't say why it has failed.
Could it be perhaps updated to show an actual error message? Or show the pipeline URL just like running locally.
In my case, I can successfully run
okteto pipeline deploy
but in GitHub Actions, I get the error message and I'm still not sure what's going on (it used to work in the past months, and suddenly stopped working yesterday).The text was updated successfully, but these errors were encountered: