Sharing custom variables between script and after-script blocks

[Pavan Prasad]

I have a step that sets variables in the script section and gets accessed in the after-script section. However I have found that variables set in the script block are not available in the after-script block. I have read that both the blocks are run in the same container. Environment variables are accessible in both blocks.

Is it just not possible or am doing something wrong?

Here's an example:

```

- step: &run-variable-tests

     name: Run Variable Sharing Tests

       script:

         - export VARIABLE_1=mytestrun

         - VARIABLE_2=mytestenv-${ENV_NAME}

       after-script:

         - echo "VARIABLE_1=${VARIABLE_1}"

         - echo "VARIABLE_2=${VARIABLE_2}"

```

Output:
VARIABLE_1=
VARIABLE_2=

[Theodora Boudale]

Hi @Pavan Prasad and welcome to the community!

This is expected behavior. Both blocks indeed run on the same container. However, Pipelines creates a script with all commands of your step's script and runs it. Then, it creates a new script with all the commands of your step's after-script, and runs it in a new session. Therefore, any variables created during the script will not be available in the after-script.

As a workaround, you can save the export command in a file and then source the file in the after-script.

We have a feature request for defining variables per step in the yml file (this, making them available to the after-script) that you can vote for here:

• https://jira.atlassian.com/browse/BCLOUD-21026

Please feel free to reach out if you have any questions.

Kind regards,
Theodora