skaffold: `dev` not invalidating image cache on lib change to multi-project config

Expected behavior

on code change, skaffold cache should have been invalidated and not used.

Actual behavior

cached docker images used and rebuild isn’t triggered.

Information

  • Skaffold version: 1.0.0
  • Operating system: macos mojave 10.14.6

skaffold (via cloud code plugin) in continuous deploy mode is intermittently not picking up source changes and rebuilding the docker images.

multi-module POM that’s using jib to build containers. project includes two micronaut microservices in different submodules. Update source code (refactored method name), and maven/jib wasn’t used to re-build containers.

Same issue happens outside of Cloud Code if I just do skaffold dev from command line.

I can work-around it by deleting ~/.skaffold/cache , or running skaffold dev --cache-artifacts=false

About this issue

  • Original URL
  • State: closed
  • Created 5 years ago
  • Reactions: 1
  • Comments: 15 (9 by maintainers)

Most upvoted comments

I also confirmed upgrading to jib version 2.2.0 fixed my issue. skaffold is deploying the latest build with jib now. Thanks!

I’m working on the reproduction for this one. From the sound of it, we’re not propagating dependencies upwards across artifacts.