We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
It'd be great if the Debian build gets executed when the windows build fails. Sequential builds could also be interesting.
(from psst/actions/runs/885002673)
Edit:
Found this in the docs: Example not requiring dependent jobs to be successful
Example not requiring dependent jobs to be successful
jobs: job1: job2: needs: job1 job3: if: always() needs: [job1, job2]
needs may not apply, but if: always() sounds promissing.
needs
if: always()
https://docs.github.com/en/actions/reference/workflow-syntax-for-github-actions#example-not-requiring-dependent-jobs-to-be-successful
The text was updated successfully, but these errors were encountered:
I'm not sure how to use this for a matrix-triggered jobs :/
matrix
Sorry, something went wrong.
This seems to be the culprit: https://docs.github.com/en/actions/reference/workflow-syntax-for-github-actions#jobsjob_idstrategyfail-fast
Should be fixed by 11cec9d. There's another issue with the deb job not running if Windows or MacOS builds fail, not sure how to approach that one.
deb
No branches or pull requests
It'd be great if the Debian build gets executed when the windows build fails. Sequential builds could also be interesting.
(from psst/actions/runs/885002673)
Edit:
Found this in the docs:
Example not requiring dependent jobs to be successful
needs
may not apply, butif: always()
sounds promissing.https://docs.github.com/en/actions/reference/workflow-syntax-for-github-actions#example-not-requiring-dependent-jobs-to-be-successful
The text was updated successfully, but these errors were encountered: