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.
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
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
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Check out this article to learn about how you can export pull request and commit data from Bitbucket to CSV.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@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:
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.