Bamboo Deployment Version ID from REST API

talleym

Given a build result key (e.g., BAM-BOO-23), how do I find the associated release created in a deployment plan? I need a way to find this information through the REST API.

 

Here's the trouble I'm having:

*I can't find associated release information anywhere in the build result's REST resources.

*Deployment plan REST resources only contain the associated build result if that build result produced an artifact. Not all of my plans produce artifacts, and I can't start making them produce artifacts just for the sake of keeping build information.

Daniel Santos_157bm4

Hello @talleym

I have an approach that could solve this issue. It is not an elegant solution (a direct rest), but at least It will give you what you need.

1. Get the <PLAN_KEY> and run the following request:

   curl -u <USER>:<PASSWORD> \
        -X GET -p <BAMBOO_URL>/rest/api/latest/deploy/project/forPlan?planKey=<PLAN-KEY> \
        | jq -r '.[] | "Name: " + .name + "\tdeploymentId: " + (.id|tostring)'
   
   

   It should give you a result like:

    Name: <DEPLOYMENT_NAME>       deploymentId: <DEPLOYMENT_ID>

2. Get the <DEPLOYMENT_ID> and run:

   curl -u <USER>:<PASSWORD> \
        -X GET -p '<BAMBOO_URL>/rest/api/latest/deploy/project/<DEPLOYMENT_ID>' \
        | jq -r '.environments[] | "Name: " + .name + "\tenvironmentId: " + (.id|tostring)'
   
   

    As a result, you should get:

    Name: <ENVIRONMENT_NAME>      environmentId: <ENVIRONMENT_ID>

3. Following the same idea, get the <ENVIRONMENT_ID> and run:

   curl -u <USER>:<PASSWORD> \
        -X GET -p '<BAMBOO_URL>/rest/api/latest/deploy/environment/<ENVIRONMENT_ID>/results' \
        | jq -r '.results[] | "Version: " + .deploymentVersionName + "\treasonSummary: " + .reasonSummary'
   
   

   This one should give you the deploymentResultId you need:

    Version: <VERSION> reasonSummary: Child of <a href="<BAMBOO_URL>/browse/<BUILD-RESULT-KEY>"><BUILD-RESULT-KEY></a>

   
   ⚠️Please notice that the above requests use jq (command-line JSON processor) to simplify filtering the results.

The last one will give you the information you need even if there is no artifact associated to that build.

I hope that helps.