Skip to content
PR

chore: update build and tooling to utilize new java version #3505

Sign in to view logs

chore: update build and tooling to utilize new java version

chore: update build and tooling to utilize new java version #3505

Triggered via pull request February 12, 2025 11:48
@aepfliaepfli
synchronize #1321
beta/new_java_build
Status Success
Total duration 2m 57s
Artifacts –

pullrequest.yml

on: pull_request
Matrix: build
Fit to window
Zoom out
Zoom in

Annotations

8 warnings
with Java 8
This run of the CodeQL Action does not have permission to access Code Scanning API endpoints. As a result, it will not be opted into any experimental features. This could be because the Action is running on a pull request from a fork. If not, please ensure the Action has the 'security-events: write' permission. Details: Resource not accessible by integration
with Java 8
Feature flags do not specify a default CLI version. Falling back to the CLI version shipped with the Action. This is 2.20.4.
with Java 8
1 issue was detected with this workflow: Please specify an on.push hook to analyze and see code scanning alerts from the default branch on the Security tab.
with Java 8
Unable to validate code scanning workflow: MissingPushHook
with Java 17
This run of the CodeQL Action does not have permission to access Code Scanning API endpoints. As a result, it will not be opted into any experimental features. This could be because the Action is running on a pull request from a fork. If not, please ensure the Action has the 'security-events: write' permission. Details: Resource not accessible by integration
with Java 17
Feature flags do not specify a default CLI version. Falling back to the CLI version shipped with the Action. This is 2.20.4.
with Java 17
1 issue was detected with this workflow: Please specify an on.push hook to analyze and see code scanning alerts from the default branch on the Security tab.
with Java 17
Unable to validate code scanning workflow: MissingPushHook