nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Inconsistency in Bamboo Variables bamboo.jira.userName

Xabier Davila_paa7go

Hi,

I order to be able to release from JIRA and directly from Bambooo, we've been using the following shell inline script to run in some of our plans:

...

if [ -n "${bamboo.version.name}" ]; then

  VERSION_NAME="${bamboo.version.name}"

else

  VERSION_NAME="${bamboo.jira.version}"

fi

...

All good up to here.

Today we've added the bit below, and our builds keep failing with bad substitution error message:

...

if [ -n "${bamboo.jira.username}" ]; then

  BUILD_USER="${bamboo.jira.username}"

else

  BUILD_USER="${bamboo.ManualBuildTriggerReason.userName}"

fi

...

Also tried the more obscure oneliner:

BUILD_USER="${bamboo.jira.username:-$(echo ${bamboo.ManualBuildTriggerReason.userName})}"

If I run the same code as a shell script (getting rid of the dots in the variable names) seems to work fine.

If I run a task with a plain script displaying the environment variables with env, I see those variables are not exported.

Any ideas on how to use BUILD_USER in my build scripts?

Accepted answers

Ron Chan2

Xabier,

Can you expand a bit on the workflow of the part of your script that does work. What are you trying to achieve? Please clarify "release from JIRA and directly from Bamboo".

All comments

Ron Chan2

Xabier,

Can you expand a bit on the workflow of the part of your script that does work. What are you trying to achieve? Please clarify "release from JIRA and directly from Bamboo".

Xabier Davila_paa7go

Hi, this bit belongs to the tag release build script.

I need those variables to add info to the build artifact: the user that built the binary and the version of the binary (tag name, etc).

I can trigger the build either from JIRA (relase version) or Bamboo (run customized)

- Bamboo directly: the version is typed as value for a custom variable. The user that triggers the build is picked by ${bamboo.ManualBuildTriggerReason.userName} variable

- Releasing a version from JIRA: Values are set in the variables ${bamboo.jira.username} and ${bamboo.jira.version}

This was (is) working fine if I just use the verison if block, failing if I add the username one.

Thanks

Xabier Davila_paa7go

Maybe I should reformulate the question:

How can I use in my build scripts the username that has triggered a build, regardless this is done manually in Bamboo or via JIRA > relese version

Ron Chan2

In response to this particular question, you can have bamboo task run something like:

build.sh ${bamboo.jira.username}

then from within build.sh, you can reference username value as $1

Marko Tibold

This fix apparently does not work anymore. We're running 5.6.2 currently. The new variable now seems to always override the build-specific key.

Xabier Davila_paa7go

Can you be a bit more specific with your issue? We are using this approach in 5.6.2 and it seems work fine for us

Marko Tibold

Yes, sorry about that, it was a bit brief. So I am trying to detect if the specific build was a scheduled build or not. It was scheduled, than this variable should exist: ${bamboo.ScheduledTriggerReason.scheduledDate} with a valid date in it. To prevent the substitution error, I've added a plan vaiable with the name "ScheduledTriggerReason.scheduledDate" and I've set it to the value "undef". Now for some reason the value always evaluates to "undef". If I look in the build metadata I see a "key" with the name "ScheduledTriggerReason.scheduledDate" and as value a timestamp. But I also see a variable with that same name and the value "undef". So I have a feeling the key cannot override the variable for some reason. I hope this makes more sense. Regards, Marko

Xabier Davila_paa7go

Are you running this as an inline script or in a file? bash, batch, PowerShell? I moved all my inline scripts to bash files. Bamboo variables are added as environment variables, so there's no way you can have 2 different values. Maybe that can fix your issue?

Mike Howells

If you run this as a script file rather than inline, you must use underscores instead of dots in the Bamboo variable names. If you do that then you will not get a substitution error because Bamboo does not do variable substitution on your script file, it sets environment variables instead. If you reference an undefined variable in your script you should just get a null value, so the if-statement should work.