CI testing updates (GitHub Actions > Travis)

[Christopher <ct...@apache.org>]

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

Re: CI testing updates (GitHub Actions > Travis)

[Christopher <ct...@apache.org>]

No, I didn't try to check into the issues with Travis at all... GitHub
Actions seems better overall anyway, so it didn't seem worth pursuing
the issues with Travis.

I've migrated the accumulo repository to use GitHub Actions, and will
work on migrating the other repos over time.

On Thu, Aug 6, 2020 at 10:46 AM Mike Miller <mm...@apache.org> wrote:
>
> 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 <ct...@apache.org> 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
> >

Re: CI testing updates (GitHub Actions > Travis)

[Mike Miller <mm...@apache.org>]

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 <ct...@apache.org> 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
>