Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support file-watching on a per-artifact basis #4368

Open
briandealwis opened this issue Jun 22, 2020 · 0 comments
Open

Support file-watching on a per-artifact basis #4368

briandealwis opened this issue Jun 22, 2020 · 0 comments
Labels
area/build area/debug area/deploy area/dev area/watch kind/feature-request priority/p3 agreed that this would be good to have, but no one is available at the moment.

Comments

@briandealwis
Copy link
Member

Some language runtimes, like the JVM, support dynamic code replacement during debugging (known by different terms such as live-edit, hot-swap, hot-reload). For such language runtimes, skaffold dev's rebuild-and-redeploy (aka file watching) on a source change causes the corresponding container to be torn down and any processes being debugged to be restarted. This is disorienting and annoying for developers used to dynamic code replacement, and so debug disables this file-watching behaviour.

For languages runtimes that do not support dynamic code replacement, or where ecosystems have become sufficiently complicated that code replacement is not safe (notably the JavaScript ecosystem), applying source changes does require a rebuild and redeploy.

To support mixed-language microservice scenarios, Skaffold should support specifying and manipulating the file-watch status on a per-artifact basis.

@jmah-cc jmah-cc added this to the v1.13.0 milestone Jul 6, 2020
@jmah-cc jmah-cc added priority/p1 High impact feature/bug. and removed priority/p2 May take a couple of releases labels Jul 6, 2020
@briandealwis briandealwis self-assigned this Jul 7, 2020
@nkubala nkubala modified the milestones: v1.13.0, v1.15.0 Aug 11, 2020
@nkubala nkubala modified the milestones: v1.15.0, Backlog Sep 1, 2020
@briandealwis briandealwis added priority/p2 May take a couple of releases and removed priority/p1 High impact feature/bug. labels Nov 27, 2020
@briandealwis briandealwis removed their assignment Apr 26, 2021
@nkubala nkubala removed this from the Backlog [P0/P1] milestone May 11, 2021
@briandealwis briandealwis added priority/p3 agreed that this would be good to have, but no one is available at the moment. and removed priority/p2 May take a couple of releases labels May 17, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/build area/debug area/deploy area/dev area/watch kind/feature-request priority/p3 agreed that this would be good to have, but no one is available at the moment.
Projects
None yet
Development

No branches or pull requests

3 participants