Skip to content

Extend plugin test coverage for newer framework versions #2109

Extend plugin test coverage for newer framework versions

Extend plugin test coverage for newer framework versions #2109

Triggered via pull request April 8, 2026 13:02
Status Cancelled
Total duration 25m 27s
Artifacts 9

plugins-jdk17-test.0.yaml

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

Annotations

10 errors and 8 warnings
jetty-11.x-scenario-jdk17
Canceling since a higher priority waiting request for plugins-jdk17-801 exists
undertow-2.3.x-scenario-jdk17
Canceling since a higher priority waiting request for plugins-jdk17-801 exists
grizzly-2.3.x-4.x-workthreadpool-scenario-jdk17
Canceling since a higher priority waiting request for plugins-jdk17-801 exists
spring-kafka-3.x-scenario-jdk17
Canceling since a higher priority waiting request for plugins-jdk17-801 exists
jdk17-with-gson-scenario-jdk17
Canceling since a higher priority waiting request for plugins-jdk17-801 exists
spring-ai-1.x-scenario-jdk17
Canceling since a higher priority waiting request for plugins-jdk17-801 exists
jetty-thread-pool-scenario-jdk17
Canceling since a higher priority waiting request for plugins-jdk17-801 exists
graphql-20plus-scenario-jdk17
Canceling since a higher priority waiting request for plugins-jdk17-801 exists
graphql-20plus-scenario-jdk17
The operation was canceled.
Test
Canceling since a higher priority waiting request for plugins-jdk17-801 exists
Build
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v2, actions/setup-java@v2, actions/upload-artifact@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/
jetty-11.x-thread-pool-scenario-jdk17
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v2, actions/download-artifact@v4, actions/setup-java@v2, actions/upload-artifact@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/
grizzly-2.3.x-4.x-scenario-jdk17
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v2, actions/download-artifact@v4, actions/setup-java@v2, actions/upload-artifact@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/
resttemplate-6.x-scenario-jdk17
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v2, actions/download-artifact@v4, actions/setup-java@v2, actions/upload-artifact@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/
spring-rabbitmq-scenario-jdk17
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v2, actions/download-artifact@v4, actions/setup-java@v2, actions/upload-artifact@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/
jetty-10.x-scenario-jdk17
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v2, actions/download-artifact@v4, actions/setup-java@v2, actions/upload-artifact@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/
jersey-3.x-scenario-jdk17
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v2, actions/download-artifact@v4, actions/setup-java@v2, actions/upload-artifact@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/
graphql-20plus-scenario-jdk17
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v2, actions/download-artifact@v4, actions/setup-java@v2, actions/upload-artifact@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/

Artifacts

Produced during runtime
Name Size Digest
skywalking-agent
44.3 MB
sha256:8955c53fc0a9a704190245e36b7e5b7b4778d9f90345fb7d5f7fdb8df4122993
test-plugin-workspace-graphql-20plus-scenario
213 MB
sha256:f2575012696c54624f84a4a2315c09b94efe46d40ad124822f3974153826c9b0
test-plugin-workspace-grizzly-2.3.x-4.x-scenario
13.1 MB
sha256:20e660600a50a76752afe3f6f42ced0482bf8862839fc2ae2925c9c440c323e6
test-plugin-workspace-jersey-3.x-scenario
20.4 MB
sha256:0e1e8e2a0f955a16066315d7eccedc0dd85889616d8e571fa18406b40bdd3388
test-plugin-workspace-jetty-10.x-scenario
14.3 MB
sha256:891a84e4cba3c4aded7e94b53c3e24d30e005fe3faac2a303e39108da2b8c529
test-plugin-workspace-jetty-11.x-thread-pool-scenario
4.8 MB
sha256:731e77a96b6fc9c0157a10ee8d8e36e4ec6539106ce16032b31c6f73c97843eb
test-plugin-workspace-resttemplate-6.x-scenario
33.6 MB
sha256:6b029edc72e8969cba946950859e3d62f2287ea2fc9d256cae0461e9b88aa619
test-plugin-workspace-spring-rabbitmq-scenario
82.2 MB
sha256:ac33575f1e949b0051f12f1aefd0168286914ef3a0a0c2f5fd2f93162d350bd5
test-tools
646 MB
sha256:ab3b55d969a83920d849e16fc832de3140f7828c870a4e2ede70d46cf50c8ba8