Success() does not works #26898
-
I use my_workflows.yml
and the performance: |
Beta Was this translation helpful? Give feedback.
Replies: 8 comments
-
Since the last step that reported a status was a success I guess it continued this one instead of skipping. If it’s really a problem it seems you should check the outcome of each step, or check for Context and expression syntax for GitHub Actions - GitHub Docs |
Beta Was this translation helpful? Give feedback.
-
But in docs:
Context and expression syntax for GitHub Actions - GitHub Docs |
Beta Was this translation helpful? Give feedback.
-
Could you link the workflow run? |
Beta Was this translation helpful? Give feedback.
-
I tested the judgment using the |
Beta Was this translation helpful? Give feedback.
-
I’m not so sure your cancel was actually processed at all. The “setup and build” step actually says it was skipped, which I believe means that the condition Subsequent steps were skipped cause success() wasn’t true after “Get menifest version” failed. (“Get menufest version” failed because success was still true and the file it needed wasn’t present. It doesn’t look like there’s a way to check skipped steps … at least not as a success/failure/cancelled condition [that I’ve seen]). Note, not sure if you care but there’s a few occurrences of "menifest’ which should likely be “manifest” 😉 |
Beta Was this translation helpful? Give feedback.
-
Thank you for your reply. You mean that the success status judged by I think it may be caused by such a situation. Is there any judgment of skip state? I only saw the ones that were judged to be cancelled. To determine the state of the previous step, you need to add an id to each state and write a long judgment formula, which is too verbose. Finally, thank you for pointing out my spelling mistakes, I am always so careless and I will fix this. 😃 |
Beta Was this translation helpful? Give feedback.
-
yi-Xu-0100:
Yes I think that’s what’s going on.
I just did a bit more quick reading, I think you could do something like:
(^ Add
No problem, happens to all of us. |
Beta Was this translation helpful? Give feedback.
-
Because the subsequent steps to publish the release also need the support of the previous steps, I have judged the subsequent related steps as an outcome, and there is no problem with the current tests. |
Beta Was this translation helpful? Give feedback.
Yes I think that’s what’s going on.
I just did a bit more quick reading, I think you could do something like: