bazel-watcher

For folks using bazel, there is also [bazel-watcher][1]. Also worth checking out [watchman][2] for this style of workflow in general. [1]: https://github.com/bazelbuild/bazel-watcher [2]: https://facebook.github.io/watchman/

If you're using Bazel, bazel-watcher [1] takes care of this, and does it in a much smarter way than just looking at a predetermined list of files. [1] - https://github.com/bazelbuild/bazel-watcher

For those using Bazel, there's ibazel: https://github.com/bazelbuild/bazel-watcher It's great, I use it all the time, especially with unit tests.

Bazel-watcher tries to accomplish this on Linux by using process group IDs. It works, if imperfectly sometimes. I ported this to Windows[1] using Job Objects. As usual, the Windows API was hell, and I made use of undocumented syscalls in order to make it work (though that part is partly Go’s fault: when you start a process, it immediately drops the thread handle on the floor. If you start a process suspended, that means it’s impossible to resume using documented APIs.) Thankfully Raymond Chen wrote an article[2] about Job Objects which helped me figure out the last bits. I genuinely am not sure I could have gotten it right without that article. There’s so many subtle ways to fail! [1] https://github.com/bazelbuild/bazel-watcher/pull/144/files [2] https://devblogs.microsoft.com/oldnewthing/20130405-00/?p=47...