ctubbsii commented on PR #2561: URL: https://github.com/apache/thrift/pull/2561#issuecomment-1101070469
> i'm not sure i can debug the CI failures - seems an issue with travis itself as the failures do not have logs and they occur randomly (same situation with other pull requests) I don't think those failures are related to this change, but I can't be sure. The individual tasks aren't well named and I'm not sure what they're doing. Also, somebody familiar with the Travis CI configuration might want to investigate moving over to GitHub Actions, since 1) it's built-in to GitHub and possibly a bit more reliable/less dependencies on another party, and 2) I don't trust Travis CI's new permissions model that seems to require granting it oauth permissions for private repos in order to log in to Travis-CI.com to manage builds, even if you only want to use it with public repos. I wonder if that was partially the reason for [this recent security incident involving Travis CI app being targeted and used as a mechanism to steal private repo contents](https://github.blog/2022-04-15-security-alert-stolen-oauth-user-tokens/) I know one of the main limits of GitHub Actions is the inability to use ARM or other non-x86 architectures when building. As a Java developer I don't generally care about that, but I'm guessing the Thrift project probably cares. -- 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]
