Hi Michele, The efforts stalled around FLIP-396 [1]. I haven't found time to pick that up again. Back then, the goal was to migrate away from Azure and rely entirely on GitHub Actions for CI and the release pipeline. Some issues with the ephemeral runners provided by Apache Infra slowed down the migration [2], and I haven't managed to pick that up again.
It would be great if someone could pick up the leftover pieces and verify that we are on-par with the AzureCi run in the end. That would probably also help with the instabilities we experience during releases. The goal is still to finish the GitHub Actions work and let both pipelines run side by side (GitHub Actions usually tends to be more sensitive to test instabilities. You can ping me for help and reviews. I will try to dedicate some time to this again. Thank you, Matthias [1] https://cwiki.apache.org/confluence/display/FLINK/FLIP-396%3A+Trial+to+test+GitHub+Actions+as+an+alternative+for+Flink%27s+current+Azure+CI+infrastructure [2] https://issues.apache.org/jira/browse/FLINK-34331 On Tue, May 12, 2026 at 5:40 PM Michele Guerriero < [email protected]> wrote: > Hi everyone, > > I'd like to check in on the status of FLINK-33901 (migrating Flink's CI > from Azure DevOps to GitHub Actions). > > Looking at the umbrella ticket, the core of the migration is in place — > GitHub Actions runs the test suite on PRs and on pushes, and the nightly > workflow runs daily across master and the active release branches. At the > same time, the umbrella still has a number of open subtasks, and the > original "end of 2025" target has passed without an explicit follow-up that > I could find on the list. > > A few questions for the community: > > 1. What's the current status of the migration? Is anyone actively driving > the remaining subtasks, or has the effort effectively stalled? > 2. Is the original goal — retiring Azure CI once GHA is fully equivalent — > still the agreed direction? Or has the plan shifted toward keeping both > systems running long-term? > 3. What are the practical blockers right now? From the open subtasks the > most visible gaps look like S3 integration tests (FLINK-34508), Maven > snapshot deployment (FLINK-34488), and the ASF runner-concurrency limit > (FLINK-34989), but I'd appreciate a community read on which of these are > real blockers versus nice-to-haves. > > If the goal is still to finish the migration and decommission Azure CI, I'd > be glad to help. Concretely, I'm willing to pick up some of the currently > unassigned subtasks and to resume work on the ones that have stalled > (FLINK-34508 in particular — the PR was auto-closed last May for lack of > review, which seems to have been the main blocker rather than anything > technical). > > Thanks, > Michele >
