Skip to content

Fix OIDC token exchange for Artifactory, Distribution and Xray servic… #259

Fix OIDC token exchange for Artifactory, Distribution and Xray servic…

Fix OIDC token exchange for Artifactory, Distribution and Xray servic… #259

Triggered via push April 21, 2026 22:27
Status Failure
Total duration 8m 1s
Artifacts

tests.yml

on: push
Matrix: Tests
Fit to window
Zoom out
Zoom in

Annotations

18 errors and 6 warnings
ubuntu Node 20
Process completed with exit code 2.
ubuntu Node 20: tasks/JFrogMaven/mavenBuild.ts#L92
'await' expressions are only allowed within async functions and at the top levels of modules.
ubuntu Node 20: tasks/JFrogMaven/mavenBuild.ts#L80
'await' expressions are only allowed within async functions and at the top levels of modules.
ubuntu Node 24
Process completed with exit code 2.
ubuntu Node 24: tasks/JFrogMaven/mavenBuild.ts#L92
'await' expressions are only allowed within async functions and at the top levels of modules.
ubuntu Node 24: tasks/JFrogMaven/mavenBuild.ts#L80
'await' expressions are only allowed within async functions and at the top levels of modules.
ubuntu Node 16
Process completed with exit code 2.
ubuntu Node 16: tasks/JFrogMaven/mavenBuild.ts#L92
'await' expressions are only allowed within async functions and at the top levels of modules.
ubuntu Node 16: tasks/JFrogMaven/mavenBuild.ts#L80
'await' expressions are only allowed within async functions and at the top levels of modules.
windows Node 24
Process completed with exit code 1.
windows Node 24: tasks/JFrogMaven/mavenBuild.ts#L92
'await' expressions are only allowed within async functions and at the top levels of modules.
windows Node 24: tasks/JFrogMaven/mavenBuild.ts#L80
'await' expressions are only allowed within async functions and at the top levels of modules.
windows Node 20
Process completed with exit code 1.
windows Node 20: tasks/JFrogMaven/mavenBuild.ts#L92
'await' expressions are only allowed within async functions and at the top levels of modules.
windows Node 20: tasks/JFrogMaven/mavenBuild.ts#L80
'await' expressions are only allowed within async functions and at the top levels of modules.
windows Node 16
Process completed with exit code 1.
windows Node 16: tasks/JFrogMaven/mavenBuild.ts#L92
'await' expressions are only allowed within async functions and at the top levels of modules.
windows Node 16: tasks/JFrogMaven/mavenBuild.ts#L80
'await' expressions are only allowed within async functions and at the top levels of modules.
ubuntu Node 20
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-java@v4, actions/setup-node@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
ubuntu Node 24
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-java@v4, actions/setup-node@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
ubuntu Node 16
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-java@v4, actions/setup-node@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
windows Node 24
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-java@v4, actions/setup-node@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
windows Node 20
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-java@v4, actions/setup-node@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
windows Node 16
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-java@v4, actions/setup-node@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/