-
Notifications
You must be signed in to change notification settings - Fork 228
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
Update strategy: newest-build not working #697
Comments
I did some testing with using the 'newest-build' strategy and noticed in the logs this was not an acceptable strategy. Image updater ended up defaulting to semver. I am using v0.12.2 when I observed the below error.
The documentation is a bit confusing as there are warnings to switch to the new names but they appear to be not ready yet. You might try using |
The version v0.12.2 is different from version latest (sha256:b3622d981368b5dc31e7d85545c3572e4a1c990cbe2403f8bb8053aa70766672), but the update-strategy: latest is working fine in your version v0.12.2? I have tried all scenarios but none of them is work :( |
Describe the bug
I using argocd image updater latest (sha256:b3622d981368b5dc31e7d85545c3572e4a1c990cbe2403f8bb8053aa70766672). It was working fine with update-strategy: semver (default) but when i change tag to 8 characters of SHA git commit, it not working it not even show logs (it just empty).
To Reproduce
Here is my yaml file:
Expected behavior
When code change in git, a workflow will run to build and push image with a tag is first 8 characters and i want argocd image updater monitoring image registry and automation update new tag to file kustomization.yaml
Additional context
I also give credential of image registry for argocd-image-updater
Version
latest (sha256:b3622d981368b5dc31e7d85545c3572e4a1c990cbe2403f8bb8053aa70766672)
Logs
I don't know why but when i use update-strategy: newest-build there not print logs, it completely empty. When update-strategy is semver everything working fine (have logs)
The text was updated successfully, but these errors were encountered: