Responding late but I'd just mention that it's worth checking the performance impacts of running bazel-deps in the wrapper (i.e. for every bazel command) since I'm not sure it's that cheap
On Friday, December 8, 2017 at 11:40:35 AM UTC+2, László Csomor wrote:
> Hi Tony,
>
>
> I'd also recommend the wrapper script approach. In fact, if you're on Linux, you already are using a wrapper script.
> See
https://stackoverflow.com/questions/47678041/user-name-in-bazelrc/47692113#47692113
>
>
> Cheers,
> Laszlo
>
>
>
>
>
>
>
> --
> László Csomor | Software Engineer |
laszlo...@google.com
>
> Google Germany GmbH | Erika-Mann-Str. 33 | 80636 München | Germany
> Registergericht und -nummer: Hamburg, HRB 86891
> Sitz der Gesellschaft: Hamburg
> Geschäftsführer: Paul Manicle, Halimah DeLaine Prado
>
>
> On Fri, Dec 8, 2017 at 4:13 AM, <
tony....@rubrik.com> wrote:
>
>
> So I'm migrating a relatively sizable maven build over to bazel and we are using bazel-deps to manage our maven dependencies.
> Currently, we need to run a script to generate all of the 3rdparty BUILD files and the workspace.bzl file before being able to run bazel.
> However, the step is a little clunky in our developer workflow. Is it possible to have bazel to automatically run this script before initialization?
>
> Perhaps as a pre-initialization step, or as a part of the build. I'm not sure it's kosher to have bazel generate BUILD files.
>
>
> We thought about writing a wrapper script around bazel to run the bazel-deps script before running the actual bazel command, but we wanted to know if there was a better way to use this tool.
>
>
> Thanks!
> Tony
>
>
>
>
>
> --
>
> You received this message because you are subscribed to the Google Groups "bazel-discuss" group.
>
> To unsubscribe from this group and stop receiving emails from it, send an email to