How can environment variables inherited to sub scripts in a script task?

Thomas Leitner_v9o74o

In Bamboo job I run a perl script using a script task.

The name of the (perl) script is entered in the field "Script file", "Interpreter" is set to "Shell".

In the perl script another (shell) script is called that does not have the same environment than the perl script but a new one. Shell variables set in the perl script are not known in the called shell script.

What is to do to inherit the environment variables from the perl script to the shell script?

Daniel Santos_157bm4

Hi @Thomas Leitner,

Can you share more details about the OS you are using and the script call?

Shells which are child processes of the Bamboo script task should have the Bamboo variables in them.

I've run the following test and it succeeded:

1. Created a repository with the following scripts:
   Script 1 (name: perl_script1.pl)

   use strict;
   use warnings;
   my $perl_var=$ENV{bamboo_var};
   print "Bamboo global var script 1: $perl_var";
   
   system("perl perl_script2.pl")

   Script 2 (name: perl_script2.pl) 

   use strict;
   use warnings;
   my $perl_var=$ENV{bamboo_var};
   print "Bamboo global var script 2: $perl_var";

2. Created a global variable called var with the value hello world!!!
3. Created a plan using the repository above
4. Added a script task calling the first script.

   perl perl_script1.pl 

The results were like:

01-Feb-2019 16:27:59 Bamboo global var script 1: hello world!!!
01-Feb-2019 16:27:59 Bamboo global var script 2: hello world!!!

Can you share how your perl script is calling the next script?
Could you also try the example above to check if it will work for you?