-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
With buildpack & auto sync a full re-build happens unpredictably #5140
Comments
+1 here's a video of the same behavior |
@briandealwis i am going to look into this as a starter bug for buildpacks :) |
Some notes from my debugging on command line
|
|
In preparation for GoogleContainerTools#5140, 1. Move fsNotifyTrigger into its own package. 2. Add a function `Ignore` to configure the fsNotifyWatcher to ignore - files belonging to predefined dirs like .idea .vscode & .git - hidden file like .somefile.swp *Output change** None. *Future Work* 1. Configure the `Ignore` to ignore files mentioned above
* [Refactor] Move FSNotify trigger into a separate package In preparation for #5140, 1. Move fsNotifyTrigger into its own package. 2. Add a function `Ignore` to configure the fsNotifyWatcher to ignore - files belonging to predefined dirs like .idea .vscode & .git - hidden file like .somefile.swp *Output change** None. *Future Work* 1. Configure the `Ignore` to ignore files mentioned above * override first, create later
@tejal29 are you still working on this; or should we lower the priority (exceeded the threshold for P1s)? |
This is a P1 but i havent been actively working on it. |
After discussing the issue with @briandealwis, We need to figure a way in skaffold to ignore files Changing this to feature request |
Tested using skaffold
1.17.2
main.go
Expected: Skaffolds auto-sync for buildpacks would automtically sync the change without performing a full container rebuild.
Actual: The full build happens.
Note: This only seems to happen unpredictably; in my tests, some changes sync, others trigger a full rebuild (the changes are identical each time - e.g. a simple
fmt.Println
string modification in this case).Example output (the first couple changes did a full rebuild, the last change synced).
The text was updated successfully, but these errors were encountered: