Including Commit history and JIRA tickets in Bamboo built deployments.

[Mark Gillespie]

For our CI builds, we are trying to include an automatically generated commits since last deployment and associated JIRA tickets.

This information we want to include in out setup package is available in Bamboo at the following pages:

http://our-bamboo:8085/deploy/viewDeploymentVersionCommits.action?versionId=18546718&deploymentProjectId=19267585

http://our-bamboo:8085/deploy/viewDeploymentVersionJiraIssues.action?versionId=18546718&deploymentProjectId=19267585

What I am trying to do is automate a download of these reports to include as offline HTML files in our build package for our integration testers to see what's changed. I can't seem to work out how to get the versionID and deploymentProjectID using Bamboo's variables.

Anyone achieved this? Is there an easier way to do this?

Many thanks.

[Gretchen]

You can certainly use those actions via rest and redirect to a file on disk that is included as a shared artifact. You'd have to script it and unless you really like scripting it wouldn't be much fun.

I don't know of any easier way to do this.

We have a plugin (internally written) that does a svn diff and echoes the output to the log files to list the specific files included in the deployment. See this list: https://confluence.atlassian.com/display/BAMBOO/Bamboo+variables

and https://confluence.atlassian.com/display/BAMBOO/Variables+for+deployment+environments

for lists of variables available to you.

I have a list of rest notes that includes this:

For example this:
.../rest/api/latest/result/PRJ-PLAN.json
will get you a list of builds which (if you were really clever with scripting and regex) could be used with this:
.../rest/api/latest/result/PRJ-PLAN-BLD.json?expand=jiraIssues
to get the individual issues for each build. Again extracting them from all the other stuff that is delivered in that result.

that may help you get started with rest.