Summary

Would like to request a new feature in Atlassian Bamboo to enhance the functionality of deployment plans by allowing the usage of variables derived from triggers of sequential deployments. This feature would enable build and deployment processes to capture outputs from earlier deployments and pass them as input variables to subsequent, dependent deployments without requiring additional tasks in the existing pipelines.

Current Problem

In the current setup, capturing the output or results from an earlier deployment and utilizing them as input for a later deployment is cumbersome. While Shared Artifacts can be used to pass data between steps, this method requires manual setup and additional tasks, which disrupts the streamlined workflow. Furthermore, this solution does not natively integrate with the standard Bamboo variable selection workflow.

Requirement

Trigger-based Variables: Allow variables to be automatically populated based on the trigger deployments within deployment plans. This would mean capturing the "trigger reason" or any other relevant data from a parent environment and using it in child environments as a variable.

Deployment Plan Integration: Implement this functionality specifically within deployment plans to facilitate isolated and standalone deployment environments. The goal is to eliminate the need for adding extra tasks to existing pipelines, thus maintaining their simplicity and integrity.

Variable Accessibility: Ensure that these trigger-based variables are easily accessible and can be used within scripts or other parts of the deployment configuration.