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

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

Avatar

1 badge earned

Collect

Participate in fun challenges

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

Challenges
Coins

Gift kudos to your peers

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

Recognition
Ribbon

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!

Leaderboard

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
4,456,196
Community Members
 
Community Events
176
Community Groups

Replace build number for deployment with custom version numbers

Hi, in Bitbucket Pipelines, we have a three deployments, DEV, UAT and PROD.  The deployments are working, but we are following a trunk based workflow and using semantic versioning.  How can replace the build number in the deployment to that of a custom value, such as a semantic version, so we can see which semantic version is deployed to which environment without having to drill in further to each build.

Thanks.

Lee

 

 

1 answer

1 accepted

0 votes
Answer accepted
Mark C Atlassian Team Jan 16, 2023

Hi @MacDonald_ Lee,

Thank you for reaching out to the community.

Unfortunately, it's not possible to change the Pipelines build number/name at the moment.
We do have an existing feature request for it that can be located through this link. - https://jira.atlassian.com/browse/BCLOUD-22161
You can upvote and watch it for now so that you'll be notified of any updates from our team when the feature becomes available on Bitbucket Cloud.
Please do note that we don't have an exact ETA for the feature request as all new features will be implemented according to our policy here.

As a workaround, you can try to use tags to version your releases (if you haven't done it yet).

Let me know if you have further questions.

Regards,
Mark C

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PERMISSIONS LEVEL
Site Admin
TAGS

Atlassian Community Events