8254054: Pre-submit testing using GitHub Actions should not use the deprecated set-env command

[rwestberg]

The set-env command was recently deprecated in favor of a different method of setting environment variables, due to a security vulnerability [1]. The vulnerability does not affect our usage of GitHub Actions, but we should nevertheless update to avoid the associated deprecation warnings.

[1] https://github.blog/changelog/2020-10-01-github-actions-deprecating-set-env-and-add-path-commands/

---

Progress

• Change must not contain extraneous whitespace
• Commit message must refer to an issue
• Change must be properly reviewed

Issue

• JDK-8254054: Pre-submit testing using GitHub Actions should not use the deprecated set-env command

Reviewers

• Erik Helin (@edvbld - Reviewer)
• Erik Joelsson (@erikj79 - Reviewer)

Download

$ git fetch https://git.openjdk.java.net/jdk pull/518/head:pull/518
$ git checkout pull/518

[bridgekeeper]

👋 Welcome back rwestberg! A progress list of the required criteria for merging this PR into master will be added to the body of your pull request. There are additional pull request commands available for use with this pull request.

[openjdk]

@rwestberg The following label will be automatically applied to this pull request:

• build

When this pull request is ready to be reviewed, an "RFR" email will be sent to the corresponding mailing list. If you would like to change these labels, use the /label pull request command.

[mlbridge]

Webrevs

• 00: Full (f08bd46)

[edvbld]

Looks good, thanks for fixing!

[openjdk]

@rwestberg This change now passes all automated pre-integration checks.

ℹ️ This project also has non-automated pre-integration requirements. Please see the file CONTRIBUTING.md for more details.

After integration, the commit message for the final commit will be:

8254054: Pre-submit testing using GitHub Actions should not use the deprecated set-env command

Reviewed-by: ehelin, erikj

You can use pull request commands such as /summary, /contributor and /issue to adjust it as needed.

At the time when this comment was updated there had been 4 new commits pushed to the master branch:

• a34f48b: 8253832: CharsetDecoder : decode() mentioning CoderMalfunctionError behavior not as per spec
• f397b60: 8251123: doclint warnings about missing javadoc tags and comments
• c9d1dcc: 8253902: G1: Starting a new marking cycle before the conc mark thread fully completed causes assertion failure
• 9199783: 8253565: PPC64: Fix duplicate if condition in vm_version_ppc.cpp

Please see this link for an up-to-date comparison between the source branch of this pull request and the master branch.
As there are no conflicts, your changes will automatically be rebased on top of these commits when integrating. If you prefer to avoid this automatic rebasing, please check the documentation for the /integrate command for further details.

➡️ To integrate this PR with the above commit message to the master branch, type /integrate in a new comment.

[rwestberg]

/integrate

[openjdk]

@rwestberg Since your change was applied there have been 4 commits pushed to the master branch:

• a34f48b: 8253832: CharsetDecoder : decode() mentioning CoderMalfunctionError behavior not as per spec
• f397b60: 8251123: doclint warnings about missing javadoc tags and comments
• c9d1dcc: 8253902: G1: Starting a new marking cycle before the conc mark thread fully completed causes assertion failure
• 9199783: 8253565: PPC64: Fix duplicate if condition in vm_version_ppc.cpp

Your commit was automatically rebased without conflicts.

Pushed as commit d2b1dc6.

💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored.