Exporting commits that have gone into a deployment

[P Lourenco]

Is there any way to export the commits that have gone into a particular bitbucket pipeline deployment?

We have multiple deployment targets, and need to reconcile what commits were deployed and when. Any suggestions welcome.

[Victor Abedi]

Hey @P Lourenco 

Yes you can track commit on bit bucket pipeline simply select the pipeline that were had triggered. On the top right corner the should be some numbers combine with letter highlighted in blue i.e 581100f . It's clickable and that should be your commit.

Regards,

Victor Abedi

[P Lourenco]

Thank you Victor I was aware of this, I was just wondering if it was possible to export this list of commits (csv?) to provide to non-dev people so they can build release notes, communicate with customers etc

[ktomk]

@P Lourenco What about fetching the data via the API

• https://developer.atlassian.com/bitbucket/api/2/reference/resource/repositories/%7Bworkspace%7D/%7Brepo_slug%7D/deployments/

and the transforming the JSON into a CSV

• https://unix.stackexchange.com/questions/163845/using-jq-to-extract-values-and-format-in-csv

?

[ktomk]

@P Lourenco My suggestion would not be very specific to Bitbucket Pipelines but is more a general approach in build automation and version control.

Assuming you're using `git` as SCM, it allows to create tags. If the build automation tags each revision that is getting deployed it's easy to keep track of these _within_ the repository.

In Bitbucket Pipelines there are two options specifically:

1. The step container has the `git` utility so the build script can create a tag and push it to the remote.
2. The step container has a REST client utility so the build script can create a tag via the Bitbucket REST API.

Personally I normally prefer the first way as most often there are other things to do with `git` like merge checks and the tooling is much more standard.