Is your feature request related to a problem?
Yes. I'd like to be able to specify some sort of a pattern that would filter out only the matching tags, so that only they're pulled & updated by watchtower.
Describe the solution you'd like
Something like:
watchtower --allow-tags='v*'
or
watchtower --disallow-tags='dev-*'
Given tags v1.2.0, dev-d8f7983, latest,
the first option would allow the first tag (v1.2.0),
and the second option would disallow the second tag, allowing others.
Additional context
I'd like build (& thus auto-deploy) docker images not only for the master branch, but for other branches / PRs too, without automatically deploying them to production - that's all - thanks.
Hi there! 馃憢馃徏 As you're new to this repo, we'd like to suggest that you read our code of conduct as well as our contribution guidelines. Thanks a bunch for opening your first issue! 馃檹
I don鈥檛 get that. Watchtower will pull new version of the same tag. It will never jump from one tag to another afaik. Instead you can add the label to only allow updates for the containers that are running the images you actually want to be updated.
The way I currently solve this for my own projects is that I push to two different tags depending on where the image should be deployed; :latest and :latest-dev. But as @zoispag points out, watchtower never jumps between tags but rather looks for hash changes of the same tag.
Wait, so if I normally push to, say, name:latest, and then I push to name:8439e4, watchtower won't pull it?
If so - we can close, as this is exactly the behaviour I need!
Exactly. If name:latest is running and watchtower is monitoring, only new builds with tag :latest will be picked up and update the running container.
Most helpful comment
Exactly. If
name:latestis running and watchtower is monitoring, only new builds with tag:latestwill be picked up and update the running container.