GitHub user RongtongJin edited a discussion: [DISCUSS] Removing the Bazel workflow
Previously, we introduced the Bazel workflow in our community, which can quickly provide test results, but it also introduced some issues: - The maintenance cost is relatively high. This includes timely updates to configuration files when new packages are introduced. The workflow often fails due to configuration issues, which can be confusing even when there are no actual problems. - Although it can quickly provide test results, multiple workflows run simultaneously, and due to the bucket effect (wooden bucket principle), the final test results still require a long waiting time. Moreover, the test cases in other workflows can cover those in the Bazel workflow. Therefore, I would like to propose removing this workflow. If you have any suggestions, please feel free to reply below. GitHub link: https://github.com/apache/rocketmq/discussions/9410 ---- This is an automatically sent email for dev@rocketmq.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
