Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Docker-based microservices - how to approach tag names and version releases


Dear Bamboo Experts,

I'm representing a small team working on a multi-service application (aka microservices).  We are using Bamboo to build docker images which are then pushed into a docker repository (Artifactory).

We are struggling with an optimal approach to tag the images and glue them into a single version release. Could you plase share your approach to this with Bamboo or point me to the right article?

As for now, the images are tagged with build numbers, so the specific version release is done by hardcoding those numbers in a docker-compose configuration files.

This approach has mutliple drawbacks and highly depends on manual procedure.

I believe Bamboo already delivers the right functionality.


0 answers

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events