-
Notifications
You must be signed in to change notification settings - Fork 21
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
feat: multi-stage output #1155
feat: multi-stage output #1155
Conversation
feat: use @oclif/multi-stage-output
* fix: human readable output * fix: source member tracking percentage * fix: bump mso * fix: bump mso * chore(release): 3.11.2-beta.0 [skip ci] * fix: handle zip details * test: update nut --------- Co-authored-by: svc-cli-bot <[email protected]>
QA Notes✅ : quickly played with various options, prior testing already done by Vivek & co |
@WillieRuemmele Because when we are running metadata validation or deploy or retrieve in our CI/CD system, it creates tremendously long log of job execution with ~200,000 stats records in it. Am I just missing the point of this feature? I just want my concise logs back. |
@avesolovksyy - please post your findings and opinions here |
What does this PR do?
Use new @oclif/multi-stage-output for
project delete source
project deploy start
project deploy resume
project deploy validate
project deploy report
project retrieve start
What issues does this PR fix or reference?
[skip-validate-pr]