Buddhike de Silva

Thanks. Trying to reproduce the container scenario here. What's the base image your reference in your `Dockerfile`?

On this end, only `mbt describe local --all` is returning an empty list. Looking at the root cause at the moment. In terms of the long path issue, I think...

Quick update on this. It looks like an issue in the `filepath.Walk` API on mounted volumes in Windows. I created a simple bin to test (see below) and it does...

@sergey-ostapenko I think this is also indirectly fixed by your local discovery optimisation. Could you please check? (Not long path issue, just the one that didn't report local modules in...

Sounds great. Do you think it's worth having two lists `--pre-build` and `--post-build`?

@figuerascarlos Thanks for sending this through. This needs to be updated via our CI build. I will queue a build to get a new version with the correct version number....

Sounds like a reasonable feature request. You are on the right track with `describe`, however That still does not give you an easy way to identify deps of a given...

Thanks for providing more context @nirradi. You should be able to create the environment your build needs before you execute `mbt build` with templating capabilities. To do that, create a...

Dirty workspace check takes place only during the checkout phase. Not for each module build. https://github.com/mbtproject/mbt/blob/master/lib/build.go#L103 Build is free to produce the artifacts inside repo during the build. However, if...

I like this idea. Including it in the roadmap. Thank you!