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
Consider this synthetic task:
download-ui-dependencies: cmds: - yarn status: - test -d node_modules
This task should only be successful if the status checks pass. I end up doing this:
download-ui-dependencies: cmds: - yarn - test -d node_modules status: - test -d node_modules
Would it be good to run the status checks after the task runs so we fail fast?
The text was updated successfully, but these errors were encountered:
@alexec don't you want preconditions?
Status is something slightly different, in-so-much that status means run or skip (so that a task only runs if status conditions are (not) satisfied.
Sorry, something went wrong.
@alexec , @trulede is right
status won't run the task if status conditions are not satified and it won't exit in error.
It'll run yarn if node_modules folder does not exist. If the folder exists, the task won't be ran
yarn
If you want to fail (IE: exit in error), you need to use preconditions :
fail
download-ui-dependencies: cmds: - yarn preconditions: - test -d node_modules
No branches or pull requests
Consider this synthetic task:
This task should only be successful if the status checks pass. I end up doing this:
Would it be good to run the status checks after the task runs so we fail fast?
The text was updated successfully, but these errors were encountered: