passing Environment variables between tasks

Question

I have a script task in Bamboo where I create a random password, and I'm trying to store it in an environment variable so I can access it in another task in the same pipeline.  I create the password in the first task and can see it with an echo, but in the next script task, I do an "echo" of that variable, and the log produces a blank line. Is there a way to make a env variable accessible by another task

First Task - Script Body

pw=$(openssl rand -base64 15)
export DEVICE_PASSWORD=$pw

Second Task - Script Body

echo $Device_PASSWORD

Eduardo Alvarenga · Answer

Hello @David Desjardins

Thank you for the extra details.

"Scope of the variables" was introduced in Bamboo 7.0. As you don't have that option I assume you are using an earlier version of Bamboo -- I highly recommend you plan an upgrade as soon as possible.

The steps you have provided so far are accurate. If all your tasks are contained on the same Bamboo Job, the bamboo_inject_AVI_PASSWORD variable will be passed over to the next tasks within the same Job. But, if you want to use that variable within different stages, you need to have the variable set at the "Result" scope level, only present on Bamboo 7.0+.

Eduardo Alvarenga
Atlassian Support APAC

--please don't forget to Accept the answer if the reply is helpful--

David Desjardins_4l10xt · Answer

Hell @Eduardo Alvarenga

Thank you so much for your help on this, as I'm one step away from making this happen, and I was hoping you could help me with the last part.  I did what you said and created a "Script Task" with this:

* pw=$(openssl rand -base64 15)
echo $pw
AVI_PASSWORD=$pw
echo "AVI_PASSWORD=$AVI_PASSWORD" >secrets.txt

I then have an "Inject Bamboo Variables" task (see image), but I don't have a "scope" field.

So the question I have is, will this still work, and if so, I'm having a hard time accessing the AVI_PASSWORD variable in other "Forge Manifest Processor" Tasks - I have been trying to access the variable like this:

$bamboo_inject_AVI_PASSWORDI should be good to go once I have this corrected.  Once again, Thank you so much for your help.

Thanks,

Dave

Eduardo Alvarenga · Answer

Hello @David Desjardins,

Thank you for the provided context.

You have to use the Inject Bamboo variables task for that. Simply follow these steps:

* On a task, create your password file using the "key=variable" format. How you are generating the string doesn't matter, as long you create a text file that can be later loaded by Bamboo* echo my_password=abc123 > secret.txt

* Add an Inject Bamboo variables task and load the secret.txt file, make sure to select Scope as Result
* Load the variable as ${bamboo_my_password} (on shell scripts) or ${bamboo.my_password} where you need

Eduardo Alvarenga
Atlassian Support APAC