Thanks for getting ahead on this one. That is unfortunate but this isn't the first time that we have had to pass on a service because of overreaching permissions. Did you try to contact anyone to at least get an explanation? Just curious since there may be a small chance it was unintentional.
On Wed, Aug 5, 2020 at 11:12 AM Christopher <[email protected]> wrote: > So, I recently noticed that Travis CI is changing. > > It looks like travis-ci.org is being phased out, as it no longer shows > my organizations or builds repos within organizations (such as the > 'apache' org). I believe this is an attempt to consolidate their > service with travis-ci.com. However, I'm not willing to authorize > travis-ci.com in order to view builds there, because the site asks for > too broad of permissions from GitHub (specifically, it asks for access > to private repos, and write access to everything). I get that these > permissions are supposed to empower specific optional features, but I > don't like granting so many permissions *until* I need them. So, > Travis is no longer usable for me as it once was. > > Additionally, I have been experimenting with CI builds using GitHub's > own built-in "Actions" feature. I have created several workflows in > other non-Apache projects I work on, such as the one at > > https://github.com/revelc/impsort-maven-plugin/blob/main/.github/workflows/maven.yaml > and have observed numerous benefits over Travis. > > It is my intention to migrate us to using GitHub Actions in place of > Travis. > https://github.com/apache/accumulo/issues/1671 >
