while the webhooks that trigger builds on docker hub are coming from the main repo and include the git tag names there, we don't have the same over here. There doesn't seem to be a sane way of telling docker hub to use repo A to build repo B using tag A.
To avoid having to manually push git tags here with the appropriate version strings, we can probably leverage travis for this here. Dockerhub then reads our git tag names, and create the matching image tags.
alternatively, we could let commits in the main repo trigger travis here and move the docker tagging logic into the deploy step. In either case, some travis fiddling is in order.
while the webhooks that trigger builds on docker hub are coming from the main repo and include the git tag names there, we don't have the same over here. There doesn't seem to be a sane way of telling docker hub to use repo A to build repo B using tag A.
To avoid having to manually push git tags here with the appropriate version strings, we can probably leverage travis for this here. Dockerhub then reads our git tag names, and create the matching image tags.
alternatively, we could let commits in the main repo trigger travis here and move the docker tagging logic into the deploy step. In either case, some travis fiddling is in order.