-
-
Notifications
You must be signed in to change notification settings - Fork 595
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
Feature: --keep-going for task to continue on error #1318
Labels
type: feature
A new feature or functionality.
Comments
Did someone do any work on this? @sofusalbertsen did you find some workaround for this? I am currently eating a similar pickle where I must run a task with two other tasks as dependencies and even if one of them fail all execution stops... |
For some use cases |
andreynering
added
type: feature
A new feature or functionality.
and removed
state: needs triage
Waiting to be triaged by a maintainer.
labels
Sep 18, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I'm missing the
--keep-going
feature of make in Task.From the documentation of make:
--keep-going
Continue as much as possible after an error. While the target that failed, and those that depend on it, cannot be remade, the other prerequisites of these targets can be processed all the same. See Testing the Compilation of a Program.
The scenario I have at the moment is this:
task deploy
task.task destroy
task, disregarding that all the sub tasks might fail (in the case that thetask deploy
did fail at some point).At the moment, the only way I can do this is through https://taskfile.dev/usage/#ignore-errors , but I do not want to set this as a permanent configuration setting, only at runtime.
The text was updated successfully, but these errors were encountered: