Summary
When we push metadata sfdx force:source:push, the output lists all pushed files.
However, in C.I. where we clone our project, this is a major problem since we reach
file log limits and CI breaks. We expect either a summarised output (total number of files) in case of success or an argument (--quiet) that will return only warnings/errors
Steps To Reproduce:
- run
sfdx force:source:push
- If 1000 files are pushed, the output will return 1000 lines.
Expected result
We expected a success message with total sum of files and not each one of them.
An argument --quiet --silent is need to control the verbosity of output.
Actual result
Returns thousands of lines of pushed metadata. This a problem in C.I. as many services like Travis have a limit in log file size.
Additional information
We would expect an argument --quiet where it would return only warnings and errors.
Summary
When we push metadata
sfdx force:source:push, the output lists all pushed files.However, in C.I. where we clone our project, this is a major problem since we reach
file log limits and CI breaks. We expect either a summarised output (total number of files) in case of success or an argument (--quiet) that will return only warnings/errors
Steps To Reproduce:
sfdx force:source:pushExpected result
We expected a success message with total sum of files and not each one of them.
An argument --quiet --silent is need to control the verbosity of output.
Actual result
Returns thousands of lines of pushed metadata. This a problem in C.I. as many services like Travis have a limit in log file size.
Additional information
We would expect an argument
--quietwhere it would return only warnings and errors.