Pass build script variable to deployment when using powershell

[ckurmann]

Hi All,

As part of my build I have a powershell script that creates a zip file with a unique name.

I would like to make this name available to deployment task powershell script that is automatically triggered after the build.

All help welcome.

[Steffen Opel _Utoolity_]

You could propagate the name by means of an artifact and the Bamboo Variables task, roughly: 

1. Dump the name to a properties file via the Bamboo Script task in your build plan, i.e. (from the top of my head) something like:
   • 'echo "zipname = ..." >zip.properties' for PowerShell
2. Configure an artifact for the zip.properties file
3. Share this artifact from your build plan to your deployment project
4. Inject a new variable from the zip.properties file in your deployment project with the Bamboo Variables task
5. Use the injected variable with the unique zip file name in your deployment task PowerShell script, e.g. $Env:bamboo_your_variable_name
   • the shell specific variable syntax is not well documented - we provide a few examples within the Environment variables section of Using the AWS Credentials Variables task in Bamboo