Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Pipeline title

Michael Dawart December 18, 2023

We're using bitbucket-pipelines to trigger deploys in related repositories. Is there a way we could hand over a title or comment for the target pipeline - so one could see e.g. which merge caused the new deploy

2 answers

0 votes
Igor Stoyanov
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
December 22, 2023

@Michael Dawart Hi. Thanks for your feature request. This feature requires an update to Bitbucket API trigger pipeline to allow to include data, that will contain info about trigger. So no changes to pipes until this will be implemented.

Regards, Igor

0 votes
Aron Gombas _Midori_
Community Champion
December 19, 2023

I think that the common way to do something like this is generating a version number in the build, and attach that to the resulted build artifacts.

For example, you generate a version number that includes the commit hash from which the build was created, then add this version number to the resulted filenames, or write it to metadata like an AWS Lambda function's description, etc. That way, on the deployed system side you will see which commit hash is actually deployed.

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PERMISSIONS LEVEL
Product Admin
TAGS
AUG Leaders

Atlassian Community Events