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
Tasks may want to "skip" or throw an error without stopping the building/deployment process. I would call that a warning, not an error.
Tasks can either succeed or fail critically.
Task function can return a string or an array of strings. Those will be logged as info-level logging messages. Still, the green check will be shown.
We could make a custom error to indicate non-critical failure. When this is thrown, the Task fails with a warning instead of stopping the process.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
I'm submitting a...
Expected Behavior
Tasks may want to "skip" or throw an error without stopping the building/deployment process. I would call that a warning, not an error.
Current Behavior
Tasks can either succeed or fail critically.
Workaround
Task function can return a string or an array of strings. Those will be logged as info-level logging messages. Still, the green check will be shown.
Idea
We could make a custom error to indicate non-critical failure. When this is thrown, the Task fails with a warning instead of stopping the process.
Your Environment
The text was updated successfully, but these errors were encountered: