What’s the best practice for Docker images tagging in a multibranch project?


I have a C# application on which different teams work in parallel and each team may work on feature branches. I’m configuring the build pipeline that builds the Docker images and pushes them to an Azure Container Registry.
In our daily work, during the deploys we need to address the specific Docker images for each branch/team so that anytime each team can deploy their images.

I am wondering, is there any best practice in multi branch projects to tag the Docker images? For example, <version>-<commit_hash>-<branch_name>?

Source: Docker Questions

Categorised as azure, azure-container-registry, docker, git, git-flow Tagged , , , ,


Leave a Reply

Still Have Questions?

Our dedicated development team is here for you!

We can help you find answers to your question for as low as 5$.

Contact Us