Read information about projects from configuration file about mbt HOT 2 CLOSED

This is largely due to blind workspace traversal we do to detect modules in locally. It traverses the entire directory tree without respecting .gitignore. As a result, if you run local commands on repository with say... node_modules, it might take up a few seconds.

Having said that, we revised this implementation recently to address a different issue and in the process I realised that we should be able to discover modules without traversing the file system quite efficiently. It requires changing the below routine to perform two tasks:

• Discover modules in head
• Discover modules in workspace (same as what you get when you run mbt describe local
  And union the two sets.
• Finally get rid of ModulesInWorkspace function in discover.go

https://github.com/mbtproject/mbt/blob/master/lib/manifest_builder.go#L134

It will be much faster.

from mbt.

As a result, if you run local commands on repository with say... node_modules, it might take up a few seconds

Exactly our situation, but we have a lot of node_modules folders. So it would be great to have these improvements to allow use this tool more efficiently.

Btw, just noticed that:
mbt describe head
is working many times faster than
mbt describe local --all
Have it been optimized already?
Really looking forward to this optimization 👍

from mbt.