You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[chore]: Initial Unified Development Experience #274
Currently developers need to know service specific toolings to spin up the service. This introduces unnecessary overhead of learning different toolings which the developer is not even responsible for. As Bazel has already been introduced, place such important service specific commands that a developer might need behind bazel so that every developer can simply use bazel to do common cross-service tasks.
As part of this initial implementation do the following,
Put different startup scripts under bazel. Note, for now, for local development only, start the services in a profile which does not require external dependencies.
Have a standard form of the command so that it's easy to remember. Like,
bazel run //service_name:start-dev
Similarly unify the test commands like,
bazel test //service_name:unit-test
Benefit hypothesis
This will help developers talk the same language in-terms of tooling.
Activity