Deal with travis-ci.org to tavis-ci.com transition

[gsauthof]

Travis-CI announced it some time ago and dot org page currently reads:

Please be aware travis-ci.org will be shutting down in several weeks, with all accounts migrating to travis-ci.com. Please stay tuned here for more information.

Currently, I see the following issues with the migration:

• integration with travis-ci.com would require me to grant Travis-CI write-access to all my Github repositories - which I'm not comfortable with to do: 'This application will be able to read and write all public and private repository data.'
• open source projects start with some free credits with the new Travis-CI service; and there is some hand-wavy language suggesting that some open source projects may request additional credits once they run out via some unspecified process. Which sound quite tedious to me.

Thus, all this hustle might require switching to another CI service. Suggestions for an alternative service are welcome!

Besides being free for open source projects, a big requirement is nested virtualization support. Without that the dracut-sshd jobs run very slow and likely hit standard CI usage limits. For Travis-CI it took years to provide job runners that support nested virtualization. Last time I checked, e.g. Github Actions didn't support it and had no concrete plans to add it.

[gsauthof]

Circle-CI seems to have some nested-virtualization support, i.e. at least when using an android base image.

It also has a generous free-tier for open source projects, i.e. similar to the old travis-ci one.

However, the github integration requires extremely broad permissions:

Write Permissions + Admin Permissions

Note: CircleCI only asks for permissions that are absolutely necessary. However, CircleCI is constrained by the specific permissions each VCS provider chooses to supply. For example, getting a list of all user’s repos – public and private – from GitHub requires the repo scope, which is write-level access. GitHub does not provide a read-only permission for listing all a user’s repositories.

If you feel strongly about reducing the number of permissions CircleCI uses, consider contacting your VCS provider to communicate your concerns.

So this is a deal breaker.

Perhaps there is another CI service which also provides a sane integration.

Of course, it would be perfectly fine for such a service to have 2 integration options:

1. the I-dont-care-about-permissions just-make-it-work option, or
2. the I care about security option, just let me now what web-hook I have to setup to what URL-scheme of yours in my github repository settings