Forums

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

Exporting commits that have gone into a deployment

P Lourenco July 3, 2020

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.

3 answers

1 vote
Victor Abedi
Contributor
July 3, 2020

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.

pipe.png

Regards,

Victor Abedi

P Lourenco July 5, 2020

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
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
July 6, 2020
0 votes
Irina Sanikovich [StiltSoft]
Atlassian Partner
August 27, 2021

Check out this article to learn about how you can export pull request and commit data from Bitbucket to CSV.

0 votes
ktomk
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
July 4, 2020

@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.

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events