Modernize database version testing matrix#1657
Merged
tsegismont merged 9 commits intoeclipse-vertx:masterfrom Apr 7, 2026
Merged
Modernize database version testing matrix#1657tsegismont merged 9 commits intoeclipse-vertx:masterfrom
tsegismont merged 9 commits intoeclipse-vertx:masterfrom
Conversation
Closes eclipse-vertx#1645 Update CI and test infrastructure to use currently supported database versions: - PostgreSQL: 14, 16, 18 (was 9, 10, 11) - MySQL: 8.4 LTS, 9.6 (was 5.6, 5.7, 8.0) - MariaDB: 11.8 LTS (was 10.4) - MSSQL: 2019, 2022, 2025 (was 2017, 2019, 2025) - Oracle: 23-slim-faststart (was 23.3-slim-faststart) - DB2: 12.1 (unchanged) JDK 11 tests baseline version per database (7 jobs) JDK 25 tests multiple versions comprehensively (11 jobs) Removed version-specific workarounds for EOL databases and updated PostgreSQL test SSL certificates to 2048-bit for compatibility with PostgreSQL 14+. Some portions of this content were created with the assistance of IBM Bob. Some portions of this content were created with the assistance of Claude Code. Signed-off-by: Thomas Segismont <tsegismont@gmail.com>
- Fix the list of supported versions - All the sqlcmd paths and wait strategies are now the same Signed-off-by: Thomas Segismont <tsegismont@gmail.com>
caching-sha2-password-public-key-path and caching-sha2-password-private-key-path are MySQL specific now. Signed-off-by: Thomas Segismont <tsegismont@gmail.com>
Signed-off-by: Thomas Segismont <tsegismont@gmail.com>
Starting with PG 18, PGDATA points to /var/lib/postgresql/MAJOR/docker docker-library/postgres#1259 Using the environment variable, the script works with all DB versions. Signed-off-by: Thomas Segismont <tsegismont@gmail.com>
In Postgres 14+, the default password encryption is scram-sha-256, not md5. Signed-off-by: Thomas Segismont <tsegismont@gmail.com>
Add container fixed port sysprop for easy debugging with Wireshark Set a container wait strategy to make sure the DB is ready for connections Signed-off-by: Thomas Segismont <tsegismont@gmail.com>
By default, the MySQL Client prefers SSL if available on the server. But since we have a self-signed certificate for testing, the client does not accept it. Therefore, it fallbacks to no SSL and creates two connections in total. That is why a couple metrics test fail, because the test expect only one connection to be closed. Signed-off-by: Thomas Segismont <tsegismont@gmail.com>
Starting with MySQL 9.5, overflow is reported as an error Signed-off-by: Thomas Segismont <tsegismont@gmail.com>
153fc10 to
dca622d
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes #1645
Update CI and test infrastructure to use currently supported database versions:
JDK 11 tests baseline version per database (7 jobs)
JDK 25 tests multiple versions comprehensively (11 jobs)
Removed version-specific workarounds for EOL databases and updated PostgreSQL test SSL certificates to 2048-bit for compatibility with PostgreSQL 14+.
Some portions of this content were created with the assistance of IBM Bob.
Some portions of this content were created with the assistance of Claude Code.