[FLINK-30965] git-repo-sync doesn't pick up the 2nd-most-recently published Flink version (even though it's still supported) after a new release branch is cut

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Component/s: Test Infrastructure
• Assignee: Matthias Pohl
• Reporter: Matthias Pohl
• Created: 08/Feb/23 13:18
• Updated: 16/Feb/23 09:39
• Resolved: 16/Feb/23 09:39

Description

I noticed that we're always synchronizing the most-recent release branches (see flink-ci/git-repo-sync:git-repo-synch:27). That means that we stop running CI on the Flink version that is soon to be deprecated after a new release branch is cut, e.g.: 1.16 & 1.15 are supported and we cut release-1.17 to start the release process for 1.17. From this point onwards, we are synchronizing 1.17 and 1.16 but skip 1.15 eventhough 1.15 is still supported.

Issue Links

• is related to: FLINK-30972 E2e tests always fail in phase "Prepare E2E run"
• links to: GitHub Pull Request #2