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
Originally posted by jonathanmorley January 19, 2023
We run pnpm -r <script name> in our CI runner. While we can time the execution of this command running for in the CI runner, we do not get any visibility in the per-package time taken to run the script.
Another aspect is that if the execution fails during execution, we do not get visibility into 1) the package that failed, 2) the packages that succeeded, 3) the packages that were cancelled, or 4) the packages that were never started
I would like to propose an argument to pnpm run, something like --report=report.json, which would output a json file after execution (including failures) with syntax like:
Discussed in #5954
Originally posted by jonathanmorley January 19, 2023
We run
pnpm -r <script name>
in our CI runner. While we can time the execution of this command running for in the CI runner, we do not get any visibility in the per-package time taken to run the script.Another aspect is that if the execution fails during execution, we do not get visibility into 1) the package that failed, 2) the packages that succeeded, 3) the packages that were cancelled, or 4) the packages that were never started
I would like to propose an argument to
pnpm run
, something like--report=report.json
, which would output a json file after execution (including failures) with syntax like:The text was updated successfully, but these errors were encountered: