rzo1 opened a new pull request, #209: URL: https://github.com/apache/openjpa/pull/209
Following up on @solomax suggestion in #207: the pull request build covers Derby and H2 only, so a defect invisible on those two reaches master and is found when someone runs another database by hand. Two recent cases — a JPQL `LIKE` pattern that matched only on Derby for several releases (OPENJPA-3009) and six tests asserting the SQL shape Derby and H2 emit (OPENJPA-3010, your MySQL report). This adds a `Databases` workflow running the existing `test-mysql-docker`, `test-mariadb-docker` and `test-postgresql-docker` profiles weekly (Mondays 04:17 UTC) plus `workflow_dispatch` for use before a risky merge. It is separate from `pr-validation.yml`, so it never blocks a pull request. Two implementation notes: the `docker-maven-plugin` declarations in those profiles carry configuration but no executions, so nothing starts a container during an ordinary build — the servers therefore come from Actions service containers with health checks, using the credentials each profile already expects. And it is one job per database rather than a matrix, because MySQL and MariaDB both listen on 3306 and a service container cannot be selected per matrix entry. I verified locally that each profile connects to a container started with exactly these service settings (MySQL needed no extra `GRANT`, which my earlier manual runs did). Java 21 only, to keep the weekly cost down — happy to add 17 if you would rather mirror the PR matrix. Expect the first scheduled run to be red until #208 lands, since `testLikeExpr` still fails on the MySQL family on master. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
