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
worked on in the last/current iteration
Building
Services
Debian Build
Docker Build PoC ongoing - does a Docker build with Bazel improve developer experience?
Testing & CI/CD
Unit Tests
Integration Tests (+ "sudo Tests")
- workflow runs in CI on bazelified artifacts
- tests are executed with bazel executing tests with bazel in CI
- supporting in test stabilization in order to make work here possible
- tests run vs a .deb based environment in review
- tests run vs a docker based environment
Load Tests
Coverage use bazel for coverage in CI
OAI Jenkins
Developer Experience
Developer Documentation
- locate documentation to be updated
- improve local integration test setup
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