blob VS mkdkr

> Bazel has remote execution and remote caching as built-in features. Hey - those are built-in features of modern CI systems too! So here's a thought experiment: if I define a build system in Bazel and then define a server-side Git push hook so the remote server triggers Bazel to build, run tests, and post the results somewhere, is that a CI system? I think it is! A crude one. But I think that qualifies as a CI system.

Bazel can be a pain. Integration with external package managers is unnatural, hermetic toolchains are tricky, naively-written rules end up using system-provided utilities, breaking reproducibility.

But the remote execution API (besides feeling like magic) lets you treat your CI as "just another user" by design, unning the same `bazel test //...` or whatever else. This means

- the CI DSL/YAML files tend to have mostly publishing and other CI-specific information in then (this feels right)

- you get to debug your build pipeline locally

- you are actually testing the ability of a new user to pull the repo, build, and have everything just work. There is no special CI build environment that users implicit have to match.

- tangentially: the remote execution API is beautiful in its simplicity:

https://github.com/bazelbuild-remote-apis/blob/master/build/...

My main problem is running the job/step locally and not wait to CI steps to validate some change.

My solution is: https://github.com/rosineygp/mkdkr

I can write somethings like this:

```Makefile

I just put it in a small solution that I can run in a lot of CI platforms.

https://github.com/rosineygp/mkdkr

in another words: https://xkcd.com/927/