kbendick opened a new issue, #5553: URL: https://github.com/apache/iceberg/issues/5553
### Feature Request / Improvement Right now, we depend on the workflow itself to cancel duplicates, using the built-in features of the github actions via the `concurrency_group`. https://github.com/apache/iceberg/blob/c965af5d489b4acdaef9267fd98fa845393f23bc/.github/workflows/flink-ci.yml#L52-L54 While this is good enough, it requires each individual run to start and then notice that it is cancelled. As the number of actions has increased, we are spending more time waiting on CI. One case where we can get time back is cancelling duplicates in bulk. For example, it's not uncommon for somebody to open a PR, then push to it, and then push to it again not too long after (if they notice a small issue etc). In the case above, we'd have to wait for each action run to be matched to a runner, start, then notice that it's a duplicate and get cancelled. If we use something like https://github.com/marketplace/actions/skip-duplicate-actions, we can have it so that when a duplicate workflow is picked up, it will cancel all but the latest workflow runs. Thus saving a lot of time in churning workflows that would be cancelled. This is not a high priority, but something to consider. I'd also still like to get it so that we have one starting point and then all of that spreads out via github's `workflow_dispatch`, so that if one test fails, all test groups fail simultaneously. This way, if the Java CI fails, we won't have 7 or 9 concurrent Spark test workloads that still run for that patch (as that patch isn't going to be mergeable in that state anyway). ### Query engine _No response_ -- 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] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
