Add compile-only CI coverage for the parked Flink 1.18 through 2.0 modules
- Dominant language
- Java
- Stars
- 6.2k
- Forks
- 2.5k
- Avg merge
- 2d 8h
- Merged PRs (30d)
- 111
Description
#19514 leaves a single Flink lane, so the Flink 1.18, 1.19, 1.20 and 2.0 datasource modules are not compiled by any job. A shared-code change that builds against the surviving version can break them on master undetected.
A cheap compile-only lane per version would close the gap without paying for the test suites. Full test coverage can come back later as the runner budget allows.
Part of #19524.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by comparing the surviving Flink CI lane with the parked Flink 1.18, 1.19, 1.20, and 2.0 modules. Identify the existing CI configuration entry points for that lane, then add one compile-only job per version; done means each module is compiled in CI without running its test suite.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- ci-cd, stream-processing
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 65/100