For GitHub Actions, outgoing env vars need to be written to $GITHUV_ENV file

[DavidBoike]

It turns out #2422 was an incorrect implementation of GitHub Actions' new way of exporting environment variables from a workflow step. GitHub Actions does not parse environment variables out of the log output. It generates a temporary file, which is different for every step of a workflow, that it identifies using the $GITHUB_ENV environment variable. You need to write each key as {NAME}={VALUE} to that temp file. GitHub Actions then parses that file and then (I believe) disposes of it before the next step starts.

So while #2422 still resulted in a correctly built binary, the exported environment variables essentially disappeared from any later step, making it impossible to do things like deploy prerelease builds to one environment and production builds to a different one.

Description

• Identify file path from GITHUB_ENV value
• Output key=value pairs to file
• Change log output to indicate values are being written to file, to erase confusion that they are parsed from log output
• If GITHUB_ACTIONS is set but GITHUB_ENV is missing, log a warning message

Related Issue

• Fixes [Bug] New GenerateBuildLogOutput for GitHub Actions in 5.5.0 doesn't export variables #2449
• Bug introduced in Avoid set-env environment warning during build log generation #2422

Motivation and Context

Regression in behavior previously working in GitHub Actions

How Has This Been Tested?

• Updated unit tests for GitHub Actions to provide a temporary file in GITHUB_ENV and assert its contents are written correctly.
• All unit tests run successfully.
• Though I'd like to generate a package and test on my target project, I'm getting errors executing build.ps1.

Screenshots (if appropriate):

N/A

Checklist:

• My code follows the code style of this project.
• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I have added tests to cover my changes.
• All new and existing tests passed.

[DavidBoike]

Downloaded the NuGet artifact and tested it in my project - now all GitVersion variables are availble when dumping all env vars with Get-ChildItem Env:*.

[asbjornu]

This looks great! Just a tiny nitpick and this should be good to go.

[asbjornu]

Excellent, thank you so much @DavidBoike & @danielmarbach! 🙏

[JesperMonsted]

Looking forward to having your fix in a release 👍

[github-actions]

🎉 This issue has been resolved in version 5.5.1 🎉
The release is available on:

• GitHub Release
• Chocolatey Package
• .Net Global Tool

Your GitReleaseManager bot 📦🚀