List changes of parent projet

[Sascha Schwartz]

Hello,

we currently have this setup:

• Project A, parent project of B. An application module.
• Project B, child of A, rebuilding itself when Project A has finished. The overall application.
• One task of Project B is to download the latest artifact produced by Project A
• Project B has several parent project, each being a module for project B.
• Project A has several deployment projects

Project A is a module for Project B. Project B is the complete application bundled with all relevant modules. We build various versions of the application project B with different modules (parents). Each version of the application is its own build. Language/Environment is PHP/JavaScript.

What we'd like to achieve:

• Changes of Project A (Issues or commits) and other parent projects listed for builds of Project B.
• List of issues/commits for Project B and all parent projects of it (i.e. Project A) for a new deployment of Project B (changeset, release notes).
• Deployment targets are different stages and live-systems. Ideally we could get a changeset individually for each target. Stage gets deployed more frequently with smaller changesets, while we'd like to have an aggregated list for a deployment of the live-server as well.

Happy for any input on how to solve this. Alternative approaches to organize the build process are welcome too.

Thanks in advance :)

[Gretchen]

You could try working with the bamboo.dependency.parent.# variables to extract the information. See https://confluence.atlassian.com/display/BAMBOO/Bamboo+variablesfor documentation on that.

You would likely have to script something with rest from the child to get that.

For example this:

.../rest/api/latest/result/PRJ-PLAN-BLD.json?expand=jiraIssues or

../rest/api/latest/result/${bamboo.buildResultKey}.json?expand=jiraIssues maybe?

to get the individual issues for each build. Again extracting them from all the other stuff that is delivered in that result.

plus adding the .../rest/api/latest/result/${bamboo.dependency.parent.0}.json?expand=jiraIssues should get you what you're looking for. Play with it. See if you can get that to work.