ctubbsii edited a comment on issue #1884: URL: https://github.com/apache/accumulo/issues/1884#issuecomment-853864865
Using TravisCI or CircleCI requires additional user registration and privileges to manage builds, so I'm not comfortable doing that myself, and would prefer to avoid it. If some other PMC member wanted to do that, I wouldn't be opposed, so long as it didn't increase the burden on the other active PMC/committers to maintain. I'd be opposed to using something like Huawei Cloud, or anything else that requires storing credentials to a third party service in the repo settings, as that's a lot more work to manage, and harder for the PMC to secure and protect as a collective, often requiring interaction with ASF INFRA to maintain and update, and much harder to self-service. Every 3rd party GitHub action, like `huaweicloud/cce-cluster-credentials@v1` would also require INFRA approval, since they have a curated allow-list, for security and project safety. Aside from security using 3rd-party services, my main concern is the disproportionate work required to maintain a workflow that has marginal value to the Accumulo community. I wouldn't want us to spend more time and effort on maintaining a CI workflow than the value the community gets from having support for those architectures. If there is a small community of ARM64 or s390x users that would benefit from having Accumulo support those, another option is for that community to run CI on their own against the public repo, and report back bugs they find. If that community grows sufficiently to warrant a bigger investment of time/effort from the PMC to maintain CI for those architectures, the interest of that community will be reflected in their ongoing contributions to the project, and we can add support for CI on those later. Currently, given the lack of bugs being reported that are specific to s390x/ARM64, my personal opinion is that there isn't sufficient interest or risk of problems to warrant the effort at this time. -- 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. For queries about this service, please contact Infrastructure at: [email protected]
