Missing bamboo release commit history due to artifact download

Enrico Neuber September 14, 2018

Hi,

We have the following integrated Atlassian setup 

  • Bitbucket (Git)
  • JIRA
  • Bamboo

We have Continuous Integration implemented that every Git commit having a JIRA issue ID in the message triggers a bamboo CI build creating shared artifacts. It works fine, bamboo is showing the included commits with JIRA issues in the build summary.

Next step is a distribution build in bamboo taking the CI artifacts to get to a proper bamboo release that can be deployed to several environments. Bamboo has the feature to compare releases by its included commits and JIRA issues.

But, here's the problem. As the distribution build takes the CI artifacts and does not checkout any Git repository, bamboo does not have a commit history it can pass into the created release. So the nice feature of release comparison is useless as the commit history is empty for the release.

How can we have the full commit history of the built artifacts (coming from the CI build) available in the distribution build and later bamboo release?

I'm hoping this comes out of the box to be a bamboo feature we currently don't know how to enable. I would like to avoid making a hack or some ugly trick.

Who could help?

1 answer

0 votes
Gonchik Tsymzhitov
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
September 15, 2018

Hi! 

 

Do you mean in deployment plan provide some json file which contain commit with commits message? 

 

 

Cheers,

Gonchik Tsymzhitov

Enrico Neuber September 16, 2018

This probably we can create by our own. But as bamboo already has the functionality in the deployment projects for every release to compare against an older release for all changes .. we would like to use it. Hindering is that bamboo does not provide the full change set internally as we just download artifacts from CI to Dist/ Release and not checkout the repository to save build time.

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events