Major Description
cbcollect-info should invoke mossScope on the FTS moss subdirectories.
This is a little tricky... as first, you'll need to find the FTS moss subdirectories.
And, this cbcollect-info change has to behave or degrade well to error conditions – that is, invoking mossScope should be done in a way so that cbcollect-info keeps on going forwards even if one subdirectory or mossScope child invocation has a problem and not inadvertently exiting. Worse case is if this somehow inadvertently prevents other cbcollect-info steps from running.
Also, this cbcollect-info change should be "open ended", in that even if mossScope's stats (sub) command picks up more features over time, we should not have to change the cbcollect-info tool. For example, consider adding a "--diag" flag or similar for mossScope (which Abhinav and I discussed).
And, this cbcollect-info change has to work on windows and linux and OSX. (Consider directory paths with backslashes, "C:", etc)
Attachments
| For Gerrit Dashboard: MB-22540 | ||||||
|---|---|---|---|---|---|---|
| # | Subject | Branch | Project | Status | CR | V |
| 72975,4 | MB-22540: Add a "diag" option for mossScope stats | master | moss | Status: MERGED | +2 | +1 |
| 73028,5 | MB-22540: mossScope to be invoked from cbcollectInfo | master | ns_server | Status: MERGED | +2 | +1 |