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,617
Community Members
 
Community Events
176
Community Groups

How to send build details to deployment dashboard in bitbucket pipeline?

I want to send build details to deployment dashboard without using deployment tag in pipeline. I have created a custom pipeline to deploy an application to a specific environment based on input provided by user and currently, it seems, deployment tag is not accepting dynamic value.

I was looking for an API that can send data to deployment dashboard but no luck.

pipeline deploy step looks like below

- step:

name: Deploy to test

deployment: $env

script: - python deploy.py test

 

Also is there any other way by which we can track build number that's been deployed to specific environment ex. production.

 

1 answer

0 votes

Hi @saddam shaikh and welcome to the community!

The only way to view deployments in the deployment dashboard is by

1. Defining the deployment environments in Repository settings > Deployments
2. Then use the deployment keyword with a valid environment name in your bitbucket-pipelines.yml file

It is not possible to do this with API or in any other way, and you are right that the deployment keyword does not accept variables.

This has been requested by other users as well and we have a feature request in our issue tracker:

If you'd be interested in this feature, I would suggest adding your vote in the feature request (by selecting the Vote for this issue link) as the number of votes helps the development team and product managers better understand the demand for new features.

You are more than welcome to leave any feedback, and you can also add yourself as a watcher (by selecting the Start watching this issue link) if you'd like to get notified via email on updates.

Implementation of new features is done as per our policy here and any updates will be posted in the feature request.

In the meantime, the only way to make this work would be by creating one step for each environment and using the environment name in each definition. If the same script is used for all deployments, you could perhaps make use of YAML anchors:

Additionally, it is possible to define deployment variables in each environment:

If the script you are using is referencing a specific variable that has a different value for each environment, you can define the variable in all environments with the same name but a different value for each environment.

Please feel free to let me know if you have any questions.

Kind regards,
Theodora

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events