Make it possible to not restart the server and only rebuild the data dependencies of a job (while leaving it running)

[achew22]

To quote @mprobst,

I found that to be more useful than respawning the binary. In
particular for servers that often take a long time to start, it's useful to
rebuild their assets (think: JS, TypeScript, etc) without restarting the
server.

[alexeagle]

Definitely need this for Karma, it takes a while for karma to start up, launch its server, launch and connect to a browser.

[achew22]

@alexeagle Do you know if this is done with a bazel query (seems likely to be slow) or by parsing the BUILD file directly or is there another mechanism that I'm unaware of

[alexeagle]

I think you are already watching all the right files? You just shouldn't kill the program, instead run another bazel build behind the running program. If we get lost, we'll probably need Martin for details.

…

On Thu, Sep 21, 2017 at 5:31 PM Andrew Z Allen ***@***.***> wrote: @alexeagle <https://github.com/alexeagle> Do you know if this is done with a bazel query (seems likely to be slow) or by parsing the BUILD file directly or is there another mechanism that I'm unaware of — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#29 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAC5I-mucpLIzvWBauvtITvUyZx2wWqUks5skv_zgaJpZM4POm-a> .

[achew22]

100% agree on that, but how do you detect if the target has the tag "no_seriously_dont_kill_me". The only idea I have off hand is to do bazel query attr(tags, no_seriously_dont_kill_me, //path/to:target) and see if the target is returned. Do you have any other ideas on that?

[alexeagle]

Can we always leave binaries running under ibazel run? I don't think iblaze has a feature to restart the binary on changes?

[achew22]

@mrmeku and I worked on this Friday night (mrmeku@54930bf) by refactoring the way commands are launched. We got pretty far and think we have a plan for handling the numerous edge cases. @mrmeku is going to fix up the tests and send me a PR which I'll merge then it'll be pretty simple to add the support for not restarting the binary on change

[alexeagle]

sweet, I'd be excited to have this for AngularMix, my demo will be a lot faster if karma stays running

…

On Sun, Sep 24, 2017 at 11:51 AM Andrew Z Allen ***@***.***> wrote: @mrmeku <https://github.com/mrmeku> and I worked on this Friday night ( ***@***.*** <mrmeku@54930bf>) by refactoring the way commands are launched. We got pretty far and think we have a plan for handling the numerous edge cases. @mrmeku <https://github.com/mrmeku> is going to fix up the tests and send me a PR which I'll merge then it'll be pretty simple to add the support for not restarting the binary on change — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#29 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAC5I4f-KX3UgPW5A088OQIp9nXK6t4nks5slqS6gaJpZM4POm-a> .

[mrmeku]

@achew22 I think this can be closed now can't it?

[achew22]

I want to close it when it's documented and e2e tested. It's not done till it's documented 😉

[achew22]

I think this is reasonably well e2e tested now. Closing.