You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I use npm run build-and-test --workspaces in a CI. If the script fails in one of the workspaces, it can be difficult to find the error in the CI log as it's followed by the output of the successful runs in the other workspaces.
How
Current Behaviour
There's no way that I know of to tell the cli to stop execution after the first fail.
Desired Behaviour
There's an option like --fail-fast.
References
n/a
The text was updated successfully, but these errors were encountered:
I literally JUST ran afoul of this exact problem. Test failures at package levels aren't halting CI workflows because --workspaces doesn't relay the error code.
I think this may be related to #575 , which has has some good conversations around this kind of behavior during the weekly meetings and so I think there is good traction on that issue. (I noticed it has been tagged for release 8.x 👀 )
Motivation ("The Why")
I use
npm run build-and-test --workspaces
in a CI. If the script fails in one of the workspaces, it can be difficult to find the error in the CI log as it's followed by the output of the successful runs in the other workspaces.How
Current Behaviour
There's no way that I know of to tell the cli to stop execution after the first fail.
Desired Behaviour
There's an option like --fail-fast.
References
The text was updated successfully, but these errors were encountered: