Re: Travis CI migration?
| From: | Christoph M. Becker | Date: | Sat, 02 Jan 2021 23:17:43 +0000 |
| Subject: | Re: Travis CI migration? | ||
| References: | 1 2 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-112718@lists.php.net to get a copy of this message | ||
On 02.01.2021 at 22:43, Nikita Popov wrote:
> On Sat, Jan 2, 2021 at 6:51 AM Stanislav Malyshev <smalyshev@gmail.com>
> wrote:
>
>> Today I noticed the message on travis-ci.org:
>>
>> 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.
>>
>> As far as I know, our repo is still not migrated. Anybody looked into it?
>>
>> Also, as I understand, the .com builds will be managed used credits
>> system, with OSS getting allocated credits:
>>
>>
>> https://docs.travis-ci.com/user/billing-faq#what-if-i-am-building-open-source
>> but this has to be done manually. I can reach out to them but wanted to
>> ask first in case somebody already did.
>>
>> Looks like we need to take care of it pretty soon or we risk losing
>> access to the CI.
>
> We haven't been using Travis as our primary CI for a while already. We use
> AppVeyor for Windows testing and Azure Pipelines for everything else. The
> only thing Travis is still used for is a daily cron job that tests PHP on
> "exotic" architectures like aarch64 and s390x. Having those builds is a
> nice to have, but not particularly critical.
The exception being the PHP-7.3 branch, which in security mode. Unless
we add GH CI for that branch as well, switching to travis-ci.com seems
to be useful. Maybe we get enough free credits for the relatively rare
builds?
Christoph