How to find relational link between a repository commit and deployment in Bamboo
Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.
Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Summary
A normal CI-CD cycle starts with a repository commit. This commit triggers a build plan, which then triggers a release. This article will address how all these information and steps are linked to each other in the Database.
Environment
Bamboo 6 or later.
Solution
In summary, what this article will show is:
Build plan --> deployment plan (production env) -->release number and completed date --> commit related to release.
Build is stored in the table build.
Deployment projects are stored in deployment_project.
Both these tables are connected through build.full_key and deployment_project.plan_key.
Deployment environments are stored in the table deployment_environment.
The tables deployment_project and deployment_environment are connected through deployment_project.deployment_project_id and deployment_environment.package_definition_id
Release number and completed date are stored in deployment_result.
The tables deployment_result and deployment_environment connect through deployment_result.environment_id and deployment_environment.environment_id.
Release date is found in deployment_result.version_name.
Completed date is found in deployment_result.finished_date.
As for commits, we need to take a different path, so we will start again:
Build is stored in the table build.
Build results are stored in buildresultsummary
Both are linked through build.full_key and buildresultsummary.build_key
Commits are stored in table repository_changeset
It's linked to buildresultsummary through buildresultsummary.buildresultsummary_id and repository_changeset.buildresultsummary_id.
For detailed info on commits, you can link repository_changeset.repository_changeset_id and user_commit.repository_changeset_id.
Was this helpful?