Fixed CCUD CI detection when using wsl-bash on GHA #643
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Added the CCUD necessary env vars to the WSLENV for wsl-bash githubActions testing.
Until now, cross-platform tests on windows, which use wsl-bash shell did not correctly pick up that this was executed on github actions. This is not an issue of CCUD, it's an issue of WSL, which by default doesn't "forward" env vars set in Windows (host) by default. The only way to forward them is to set them using
WSLENV
- see discussion and Microsoft blog. You can also observe that in this test project, where the env vars are printed out. All of them are available with the default windows shell (pwsh), but almost none are there with wsl. When WSLENV is configured, the specified vars are available, which also means that CCUD will tag the build correctly, as well as add all of the other values.Note: These are the two cross-platform runs with these changes: