v0.11.0 is the latest tag my commits are based on locally
8 is the number of custom commits I have locally added on top of the v0.11.0 tag
g is constant
4f9a9ed3 is the abbreviated commit sha of the latest commit
The tag does no change when doing changes locally without commits. make extension-up runs build a new image but tag it with the same tag. Running update is not triggered for the extension Pods as the tag didn't change.
How to categorize this issue?
/area dev-productivity /kind bug
What happened:
make extension-upgenerates always a tag in the formatv0.11.0-8-g4f9a9ed3.This is the output of the
git describe --tags --alwayscommand: ref https://github.com/GoogleContainerTools/skaffold/blob/6293a3efe10fc12ccb16c2477e59aa4b9335a8dc/pkg/skaffold/tag/git_commit.go#L109-L111Demystifying
v0.11.0-8-g4f9a9ed3:v0.11.0is the latest tag my commits are based on locally8is the number of custom commits I have locally added on top of thev0.11.0taggis constant4f9a9ed3is the abbreviated commit sha of the latest commitThe tag does no change when doing changes locally without commits.
make extension-upruns build a new image but tag it with the same tag. Running update is not triggered for the extension Pods as the tag didn't change.Upstream docs for taggers: ref https://skaffold.dev/docs/taggers/.
What you expected to happen: Code changes locally to generate a new tag and ControllerDeployment to be updated with a new tag.
How to reproduce it (as minimally and precisely as possible): See above.
Anything else we need to know?: Many thanks to @rrhubenov for helping analysing this issue.
Environment:
kubectl version):