Scope: AGW can be developed and released using Bazel only instead of make
done - possible optimizations can be added after a switch-over
in progress
not yet started
will not be used with bazel
worked on in the last/current iteration
Switch Over
- We are starting the switch over! Make builds will be replaced step by step with Bazel builds.
- Single parts will be announced in Slack.
- This is tested extensively - but we expect needed improvements.
- Please let us know about any issue you encounter → Slack: #bazel or #dev
Status
Building
Services
Debian Build
Docker Build PoC ongoing - improve developer experience of Docker builds
Testing & CI/CD
Unit Tests
Integration Tests (+ "sudo Tests")
- workflow runs in CI on bazelified artifacts
- tests are executed with bazel build with bazel, but execute directly with pytest in progress
- tests run vs a .deb based environmen
- tests run vs a docker based environment - only needed if docker artifacts are build with bazel
Load Tests but not in CI (as for the make version)
Coverage
OAI Jenkins
Developer Experience
Developer Documentation locate documentation to be updated - planned: (feed-back from PTG) already add Bazel documentation for more easy access
prepare IDEs for code navigation with bazel setup environment with proto builds and pip dependencies
detail improvements many are in progress
Linter and Formatter with Bazel - Analysis: this is not feasible - will be kept as direct calls to current tooling (can also be kept in Makefiles for convenience)
Remote Caches