-
Notifications
You must be signed in to change notification settings - Fork 4.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Please add nojdk packages of Bazel for Windows #13779
Labels
area-Windows
Windows-specific issues and feature requests
P2
We'll consider working on this in future. (Assignee optional)
team-OSS
Issues for the Bazel OSS team: installation, release processBazel packaging, website
type: feature request
Comments
JayBazuzi
added a commit
to JayBazuzi/continuous-integration
that referenced
this issue
Aug 13, 2021
JayBazuzi
pushed a commit
to JayBazuzi/continuous-integration
that referenced
this issue
Aug 13, 2021
@comius Looks like we should also upgraded our embedded JDK version to not use |
meteorcloudy
pushed a commit
to bazelbuild/continuous-integration
that referenced
this issue
Aug 23, 2021
Was this fixed by bazelbuild/continuous-integration#1206? |
fmeum
pushed a commit
to fmeum/continuous-integration
that referenced
this issue
Dec 10, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
area-Windows
Windows-specific issues and feature requests
P2
We'll consider working on this in future. (Assignee optional)
team-OSS
Issues for the Bazel OSS team: installation, release processBazel packaging, website
type: feature request
Description of the problem / feature request:
Currently Bazel produces
nojdk
packages of Bazel for Linux and Mac, but not for Windows. Please expand that to include Windows.Feature requests: what underlying problem are you trying to solve with this feature?
Bazel 4.1.0 comes with JDK 11.0.6 which has known security vulnerabilities. Our organization requires that we stay up to date with dependencies that have CVEs, and JDK 11.0.6 is flagged as prohibted.
We know that we can supply a JDK with
JAVA_HOME
and that Bazel will use it (which is great!) but the non-nojdk
distribution of Bazel still unpacks the older JDK on the machine even though it doesn't use it, which is still flagged by our organization's security scans.What operating system are you running Bazel on?
Windows (and Linux and Mac, but this request is specific to Windows).
What's the output of
bazel info release
?Have you found anything relevant by searching the web?
https://bazelbuild.slack.com/archives/CA31HN1T3/p1627277344349100
The text was updated successfully, but these errors were encountered: