Feature Request - Support trigger file

[saturnism]

Currently Skaffold triggers rebuild/redeploy on every file change and may be too frequent. Add a mode to rather watching all files, watch only one specified trigger file to kick off rebuid/redeploy.

[nkubala]

+1 to this, we're discussing different enhancements to the way skaffold triggers builds.

it might make sense to configure this on a per-artifact basis as well, since different artifacts might represent different "areas of the code" which might have separate triggers. this could live in the skaffold.yaml and look something like

build:
  artifacts:
  - image: my_image
    triggerFiles:
    - code.go
    - app.go
  - image: my_java_image
    triggerFiles:
    - app.java

we're also considering adding a way for users to switch to manual trigger mode, which would be exposed through a gRPC/HTTP endpoint. this could also be exposed through a UI element in Cloud Code.

[saturnism]

more or less, the trigger file may not be a source file at all, but a designated file that can user or IDE can touch

[tejal29]

@saturnism We now have a control api which can trigger a maunal build via curl.
I will close this once #2912.

[saturnism]

I feel curl/api is a very different use case than a file trigger though. I.e., file based trigger is the most natural/integratabtle w/ existing toolings.

[nkubala]

closing this due to inactivity.