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
@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
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.