Skip to content

Add MongoDB 5.x plugin, Jedis 5.x support, fix Spring MVC javax/jakarta detection #2392

Add MongoDB 5.x plugin, Jedis 5.x support, fix Spring MVC javax/jakarta detection

Add MongoDB 5.x plugin, Jedis 5.x support, fix Spring MVC javax/jakarta detection #2392

Triggered via pull request April 9, 2026 09:09
Status Cancelled
Total duration 26m 6s
Artifacts 2

plugins-test.1.yaml

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

Annotations

33 errors and 1 warning
h2-scenario
Canceling since a higher priority waiting request for plugins-1-803 exists
hystrix-scenario
Canceling since a higher priority waiting request for plugins-1-803 exists
httpclient-3.x-scenario
Canceling since a higher priority waiting request for plugins-1-803 exists
httpasyncclient-scenario
Canceling since a higher priority waiting request for plugins-1-803 exists
sentinel-scenario
Canceling since a higher priority waiting request for plugins-1-803 exists
httpclient-4.3.x-scenario
Canceling since a higher priority waiting request for plugins-1-803 exists
jdk-threading-scenario
Canceling since a higher priority waiting request for plugins-1-803 exists
httpclient-5.x-scenario
Canceling since a higher priority waiting request for plugins-1-803 exists
jedis-2.x-scenario
Canceling since a higher priority waiting request for plugins-1-803 exists
influxdb-scenario
Canceling since a higher priority waiting request for plugins-1-803 exists
hutool-http-5.x-scenario
Canceling since a higher priority waiting request for plugins-1-803 exists
jedis-4.x-scenario
Canceling since a higher priority waiting request for plugins-1-803 exists
jdk-http-scenario
Canceling since a higher priority waiting request for plugins-1-803 exists
jedis-2.x-3.x-cluster-scenario
Canceling since a higher priority waiting request for plugins-1-803 exists
jedis-3.1.x-plus-scenario
Canceling since a higher priority waiting request for plugins-1-803 exists
mongodb-4.x-scenario
Canceling since a higher priority waiting request for plugins-1-803 exists
kotlin-coroutine-scenario
Canceling since a higher priority waiting request for plugins-1-803 exists
jetty-scenario
Canceling since a higher priority waiting request for plugins-1-803 exists
kafka-scenario
Canceling since a higher priority waiting request for plugins-1-803 exists
lettuce-6.5.x-scenario
Canceling since a higher priority waiting request for plugins-1-803 exists
mongodb-3.x-scenario
Canceling since a higher priority waiting request for plugins-1-803 exists
jedis-3.3.x-plus-scenario
Canceling since a higher priority waiting request for plugins-1-803 exists
lettuce-webflux-5x-scenario
Canceling since a higher priority waiting request for plugins-1-803 exists
netty-socketio-scenario
Canceling since a higher priority waiting request for plugins-1-803 exists
mongodb-5.x-scenario
Canceling since a higher priority waiting request for plugins-1-803 exists
lettuce-scenario
Canceling since a higher priority waiting request for plugins-1-803 exists
mssql-jdbc-scenario
Canceling since a higher priority waiting request for plugins-1-803 exists
mybatis-3.x-scenario
Canceling since a higher priority waiting request for plugins-1-803 exists
mssql-jtds-scenario
Canceling since a higher priority waiting request for plugins-1-803 exists
postgresql-above9.4.1207-scenario
Canceling since a higher priority waiting request for plugins-1-803 exists
netty-http-4.1.x-scenario
Canceling since a higher priority waiting request for plugins-1-803 exists
resteasy-4.x-scenario
Canceling since a higher priority waiting request for plugins-1-803 exists
Test
Canceling since a higher priority waiting request for plugins-1-803 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/

Artifacts

Produced during runtime
Name Size Digest
skywalking-agent
44.4 MB
sha256:3cd60145d43ef3d53a34c4e756ff789c77cdeaebdfbe6f07068959ad308dadd8
test-tools
469 MB
sha256:0469d0fd55ab8e2541d3b8523a462b04f7e42b720a737f312b9537e3e774dfcd