FazBrowse GitHub Viewer | Trending |
URL:
| Home
Tools: [Download Repo ZIP]   [Original HTTPS Page]

Add runner OS and arch to status report by cklin · Pull Request #959 · github/codeql-action · GitHub

Add runner OS and arch to status report - #959

Merged
cklin merged 3 commits into
github:mainfrom
cklin:report-runner-os-arch
Mar 3, 2022
Merged

cklin merged 3 commits into
github:mainfrom
cklin:report-runner-os-arch

Conversation

cklin commented Mar 2, 2022

Copy link
Copy Markdown
Contributor

Merge / deployment checklist

  • Confirm this change is backwards compatible with existing workflows.
  • Confirm the readme has been updated if necessary.
  • Confirm the changelog has been updated if necessary.

This PR adds the OS and architecture (as reported by the GitHub Action Runner environments RUNNER_OS and RUNNER_ARCH) to the status report.

cklin requested a review from a team as a code owner March 2, 2022 19:09

aeisenberg left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Choose a reason Spam Abuse Off Topic Outdated Duplicate Resolved Low Quality

I'm pretty sure status reports will fail to upload because of the new fields until we can make the server side changes.

Comment thread src/actions-util.ts Outdated

aeisenberg left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Choose a reason Spam Abuse Off Topic Outdated Duplicate Resolved Low Quality

Nice. Just be sure to get the hydro schema changes deployed before merging this.

cklin and others added 2 commits March 2, 2022 16:23
Co-authored-by: Andrew Eisenberg <aeisenberg@github.com>
Comment thread src/actions-util.ts
statusReport.matrix_vars = matrix;
}
if (runnerOs === "Windows" || runnerOs === "macOS") {
statusReport.runner_os_release = os.release();

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Choose a reason Spam Abuse Off Topic Outdated Duplicate Resolved Low Quality

Is there a reason not to do this on linux? I just tried on one of my codespaces and I get:

Welcome to Node.js v14.17.6.
Type ".help" for more information.
> require('os').release()
'5.4.0-1069-azure'

It's not in x.y.z form, but it's still valid. I think it's the kernel version.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Choose a reason Spam Abuse Off Topic Outdated Duplicate Resolved Low Quality

There are a few reasons.

  • We want to limit the cardinality of the status values reported, and there are many more variations for Linux kernel release strings than for Windows and macOS release versions.
  • Linux kernel release IDs may contain custom strings, and we want to avoid recording private data (for custom kernel builds on self-hosted runners, for example).
  • Windows and macOS release strings are more useful because they are representative of the entire system configuration (whether you are running Windows 10 or Windows 11, for example). Linux kernel versions are less coupled with the userspace environment—5.11.3 on RedHat could be very different from 5.11.3 on Ubuntu.

So we are recording OS releases only for Windows and macOS.

cklin merged commit 939659c into github:main Mar 3, 2022
cklin deleted the report-runner-os-arch branch March 3, 2022 22:59
github-actions Bot mentioned this pull request Mar 7, 2022
5 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters. Learn more about bidirectional Unicode characters
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants


Back | FazBrowse Home | New Git URL