Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add bazel support for easier external integration #130

Merged
merged 5 commits into from
Nov 24, 2023

Conversation

golovasteek
Copy link
Contributor

@golovasteek golovasteek commented Nov 23, 2023

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.

Signed-off-by: Evgeny Petrov <evgeny@epetrov.net>
Signed-off-by: Evgeny Petrov <evgeny@epetrov.net>
Copy link
Contributor

@SirVer SirVer left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Very nice, just a couple of nits.

.github/workflows/bazel_build.yml Show resolved Hide resolved
bazel/README.md Outdated Show resolved Hide resolved
bazel/README.md Outdated Show resolved Hide resolved
bazel/third-party/BUILD.curl.bazel Outdated Show resolved Hide resolved
bazel/third-party/BUILD.json-schema-validator.bazel Outdated Show resolved Hide resolved
@SirVer
Copy link
Contributor

SirVer commented Nov 24, 2023

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
Copy link
Contributor

@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.

@corneliusclaussen
Copy link
Contributor

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.

Signed-off-by: Evgeny Petrov <evgeny@epetrov.net>
Signed-off-by: Evgeny Petrov <evgeny@epetrov.net>
Signed-off-by: Evgeny Petrov <evgeny@epetrov.net>
@golovasteek golovasteek marked this pull request as ready for review November 24, 2023 13:37
@golovasteek
Copy link
Contributor Author

I've addressed all comments.

@corneliusclaussen corneliusclaussen merged commit 708c485 into EVerest:main Nov 24, 2023
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants