Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:112715
MIME-Version: 1.0
References: <fdc86867-1325-072a-e5cd-154cb48b7c0c@gmail.com>
In-Reply-To: <fdc86867-1325-072a-e5cd-154cb48b7c0c@gmail.com>
Date: Sat, 2 Jan 2021 22:43:42 +0100
Message-ID: <CAF+90c-CZ60CZZJdRjLtO5CTez48Yx28umOO8dbD6cMmQ7T8ng@mail.gmail.com>
To: Stanislav Malyshev <smalyshev@gmail.com>
Cc: PHP Internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="000000000000164b8705b7f1c1bf"
Subject: Re: [PHP-DEV] Travis CI migration?
From: nikita.ppv@gmail.com (Nikita Popov)

--000000000000164b8705b7f1c1bf
Content-Type: text/plain; charset="UTF-8"

On Sat, Jan 2, 2021 at 6:51 AM Stanislav Malyshev <smalyshev@gmail.com>
wrote:

> Hi!
>
> 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.
>

Hi Stas,

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.

Regards,
Nikita

--000000000000164b8705b7f1c1bf--