cloudbase-ai opened a new pull request, #7367: URL: https://github.com/apache/shenyu/pull/7367
### What changed Expand each E2E protocol case into three independent matrix entries: - `websocket` - `http` - `zookeeper` The workflow passes the selected mode through `E2E_SYNC_TYPE`. The six E2E scripts run only that mode when the variable is present, while preserving the existing three-mode loop for local/manual calls that do not set it. Affected cases: - HTTP - Spring Cloud - Apache Dubbo - gRPC - WebSocket - RocketMQ logging ### Why Each protocol currently executes all three synchronization modes serially inside one job. On PR #6528: - E2E image preparation: 4.85 min; - Apache Dubbo E2E job: 12.60 min; - Dubbo `Run E2E Tests` step: 10.48 min; - total E2E critical path: about 17.8 min. The protocol matrix is already parallel, but the three sync modes inside each protocol are not. Expanding the sync modes into isolated GitHub-hosted runners changes the critical path from the sum of three modes to the slowest single mode. ### Expected effect - E2E wall clock: approximately 17.8 min to 9-12 min. - Runner usage may increase because checkout, artifact restore, and example setup are repeated for each sync-mode job. - This PR prioritizes total CI completion time; a later optimization can prebuild example artifacts to reduce the repeated runner overhead. ### Compatibility - Manual script execution without `E2E_SYNC_TYPE` still runs all three modes. - Storage E2E is unchanged. - Existing path-based protocol selection is unchanged. - Each matrix job has an isolated runner, so Docker ports, networks, and container names do not conflict across sync modes. ### Verification - Resolver regression tests verify exact three-mode expansion for gRPC and RocketMQ. - Admin registration E2E routing verifies 5 protocols × 3 modes. - All six scripts are checked for the single-mode override contract. - Resolver tests pass on Bash 5.2. - ShellCheck passes for all changed shell scripts. - Workflow YAML and Bash syntax parse successfully. -- 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]
