Closed golovasteek closed 1 year ago
Following the process that was suggested on the TSC meeting yesterday, we'd like to merge this best-effort support for Bazel which we have been using internally. Having it here makes it easier to keep in sync with future development of the framework and also makes it easy for others to use this in their own build processes.
@corneliusclaussen @caller or any other: any inputs on this?
@corneliusclaussen @caller or any other: any inputs on this?
I'm good with this, but I also think we should put a warning in the Readme or so stating that this build method is wip and your milage may vary.
To get this merged pls look at the comments and especially at the caching key and mark as "Ready for review" when you are done.
I've addressed all comments.
Many enterprise companies use Bazel to build their softwawre. Among them Qwello, BMW, Fernride.
Bazel is very good suitable for large repositories, because it ensures correctness of the incremental builds. And therefor even on large code bases CI can handle testing every commit.
To make adoption of Everest easier in such projects we may ship bazel rules for everest-framework.
In this PR bazel rules are added that allow to build everest-framework library, manager and controller.
The proposed usage is described in bazel/README.md.