Skip to content

#294 - Setting project version to 0.9.0 #367

#294 - Setting project version to 0.9.0

#294 - Setting project version to 0.9.0 #367

Triggered via push August 18, 2024 11:31
Status Success
Total duration 12m 30s
Artifacts

posmulten.yml

on: push
Compilation and unit tests
2m 35s
Compilation and unit tests
Compilation and unit tests for java 11
2m 14s
Compilation and unit tests for java 11
Database creation tests for multiple postgres versions 9.6, 10, 11, 12, 13
1m 24s
Database creation tests for multiple postgres versions 9.6, 10, 11, 12, 13
Testing configuration jar
1m 45s
Testing configuration jar
Integration and functional tests in postgresql-core module
2m 58s
Integration and functional tests in postgresql-core module
E2E smoke tests for configuration jar
1m 50s
E2E smoke tests for configuration jar
Tests for configuration jar documentations
1m 49s
Tests for configuration jar documentations
Testing Swing Application
3m 13s
Testing Swing Application
Running integration and functional tests that checks if code is compatible with postgres versions...
6m 7s
Running integration and functional tests that checks if code is compatible with postgres versions...
Publish to the Maven Central Repository
7s
Publish to the Maven Central Repository
Fit to window
Zoom out
Zoom in

Annotations

18 warnings
Database creation tests for multiple postgres versions 9.6, 10, 11, 12, 13
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/
Database creation tests for multiple postgres versions 9.6, 10, 11, 12, 13
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Testing configuration jar
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-java@v1, cactuslab/maven-toolchains-xml-action@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Testing configuration jar
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v2, actions/setup-java@v3, actions/setup-java@v1, cactuslab/maven-toolchains-xml-action@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Compilation and unit tests for java 11
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-java@v1, cactuslab/maven-toolchains-xml-action@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Compilation and unit tests for java 11
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v2, actions/setup-java@v1, actions/setup-java@v3, cactuslab/maven-toolchains-xml-action@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Compilation and unit tests
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-java@v1, cactuslab/maven-toolchains-xml-action@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Compilation and unit tests
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v2, actions/setup-java@v3, actions/setup-java@v1, cactuslab/maven-toolchains-xml-action@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Tests for configuration jar documentations
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-java@v1, cactuslab/maven-toolchains-xml-action@v1, actions/setup-node@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Tests for configuration jar documentations
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v2, actions/setup-java@v3, actions/setup-java@v1, cactuslab/maven-toolchains-xml-action@v1, actions/setup-node@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
E2E smoke tests for configuration jar
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-java@v1, cactuslab/maven-toolchains-xml-action@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
E2E smoke tests for configuration jar
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v2, actions/setup-java@v3, actions/setup-java@v1, cactuslab/maven-toolchains-xml-action@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Integration and functional tests in postgresql-core module
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-java@v1, cactuslab/maven-toolchains-xml-action@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Integration and functional tests in postgresql-core module
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v2, actions/setup-java@v3, actions/setup-java@v1, cactuslab/maven-toolchains-xml-action@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Testing Swing Application
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-java@v1, cactuslab/maven-toolchains-xml-action@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Testing Swing Application
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v2, actions/setup-java@v3, actions/setup-java@v1, cactuslab/maven-toolchains-xml-action@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Running integration and functional tests that checks if code is compatible with postgres versions...
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-java@v1, cactuslab/maven-toolchains-xml-action@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Running integration and functional tests that checks if code is compatible with postgres versions...
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v2, actions/setup-java@v3, actions/setup-java@v1, cactuslab/maven-toolchains-xml-action@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/