MartijnVisser opened a new pull request, #223: URL: https://github.com/apache/flink-connector-jdbc/pull/223
## What is the purpose of the change The weekly matrix covers `main` (2.2-SNAPSHOT), `v4.1` (2.2.0) and `v3.4` (1.20.3 on JDK 8, 11, 17 and 21), but `strategy` has no `fail-fast: false`, so the first leg to fail cancels the rest. Since FLINK-40221 updated the matrix on 2026-07-23, all four `v3.4` jobs have been cancelled on every one of the nine runs since, leaving the branch we ship for Flink 1.20 without CI coverage for nine weeks. It also hides whichever of `main` and `v4.1` loses the race; both are red, for two unrelated reasons. ## Brief change log - Set `fail-fast: false` on the weekly `compile_and_test` matrix, as `flink-connector-kafka` already does. ## Verifying this change This change is a trivial rework / code cleanup without any test coverage. The effect is visible on the next scheduled run, or on a manual `workflow_dispatch`. ## Does this pull request potentially affect one of the following parts: - Dependencies (does it add or upgrade a dependency): no - The public API, i.e., is any changed class annotated with `@Public(Evolving)`: no - The serializers: no - The runtime per-record code paths (performance sensitive): no - Anything that affects deployment or recovery: no - The S3 file system connector: no ## Documentation - Does this pull request introduce a new feature? no --- ##### Was generative AI tooling used to co-author this PR? - [X] Yes (please specify the tool below) Generated-by: Claude Code (Claude Opus 5) -- 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]
