Skip to content

test: Add integration tests for maven and jar deployments #10

test: Add integration tests for maven and jar deployments

test: Add integration tests for maven and jar deployments #10

Triggered via pull request February 29, 2024 09:33
Status Failure
Total duration 2m 54s
Artifacts

integration-tests.yml

on: pull_request
Build Docker Images for Integration Tests
33s
Build Docker Images for Integration Tests
Matrix: Run Debian 12 Maven JAR integration tests
Fit to window
Zoom out
Zoom in

Annotations

3 errors and 4 warnings
Run Debian 12 Maven JAR integration tests (-m, build-*car*, ubuntu-latest)
Process completed with exit code 1.
Run Debian 12 Maven JAR integration tests (-m, build*public*, ubuntu-latest)
The job was canceled because "_-m_build-_car__ubuntu-la" failed.
Build Docker Images for Integration Tests
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@v2, docker/setup-buildx-action@v2, actions/setup-java@v2. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
Build Docker Images for Integration Tests
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-java@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Run Debian 12 Maven JAR integration tests (-m, build-*car*, ubuntu-latest)
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@v2, docker/setup-buildx-action@v2. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
Run Debian 12 Maven JAR integration tests (-m, build-*car*, ubuntu-latest)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/