Avoid set-env environment warning during build log generation #2422
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.
GitHub Actions is deprecating set-env and add-path commands as outlined by
https://github.blog/changelog/2020-10-01-github-actions-deprecating-set-env-and-add-path-commands/
Therefore starting from version 2.273.5 of the runner
GenerateBuildLogOutputoutputsEnvironment files should be used instead
https://docs.github.com/en/free-pro-team@latest/actions/reference/workflow-commands-for-github-actions#environment-files
Description
see above
Related Issue
Fixes #2421 and GitTools/actions#213.
Motivation and Context
How Has This Been Tested?
No, I edited the file online and did not try to build and intermediate package to a private feed and then use that in my code. We should be able though to see the impact on the build on this project. I'll update the screenshots as soon as this compiles
Screenshots (if appropriate):
Also happens on the build of this project, see
Checklist: