Help
cancel
Showing results for 
Search instead for 
Did you mean: 
Copilot Lvl 3
Message 1 of 3

Support saving environment variables between steps

Solved! Go to Solution.

With https://github.community/t5/GitHub-Actions/YAML-folded-multiline-strings-interpreted-as-multiple-com... solved, the only thing standing in the way of reusing a lot of commands between Linux/MacOS and Windows when building C++ with CMake is an option to keep environment variables between steps (currently the environment is reset after each step).

 

For example, an option `transfer-env` that, when enabled, saves the environment after each step and restores it in the next step would allow me to remove a lot of duplicate code from reproc's (https://github.com/DaanDeMeyer/reproc/blob/master/.github/workflows/main.yml) and doctest's WIP (https://github.com/DaanDeMeyer/doctest/blob/github-actions/.github/workflows/main.yml) Github Actions configs.

 

I've seen that it's possible to set global environment variables with `exportVariable` in https://github.com/actions/toolkit which makes me think that adding this is possible. If possible I'd try to implement it myself but I do not think the relevant code is open source.

2 Replies
Solution
GitHub Staff
Message 2 of 3

Re: Support saving environment variables between steps

You can echo out a string that will set an env for the rest of the job, this is exactly what the toolkit method will do.

 

echo ::set-env name=action_state::yellow

 

https://help.github.com/en/articles/development-tools-for-github-actions#set-an-environment-variable...

Copilot Lvl 3
Message 3 of 3

Re: Support saving environment variables between steps

Using set-env I was able to achieve the desired result.

 

On Windows, VS related environment variables are set by a third-party batch script, so I had to add them with set-env manually after calling the batch script. Instead of filtering the relevant environment variables, I just make every environment variable global using set-env. The script can be found here.