Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:112743
To: Stanislav Malyshev <smalyshev@gmail.com>,
 Nikita Popov <nikita.ppv@gmail.com>
Cc: PHP Internals <internals@lists.php.net>
References: <fdc86867-1325-072a-e5cd-154cb48b7c0c@gmail.com>
 <CAF+90c-CZ60CZZJdRjLtO5CTez48Yx28umOO8dbD6cMmQ7T8ng@mail.gmail.com>
 <86618f8d-7094-1cf7-c017-b7670699a8a3@gmx.de>
 <777c75df-2848-4960-2bf9-b0cbd16b6a82@gmail.com>
Message-ID: <7243ac79-6716-948d-ba9a-e0ebc6dee7d0@gmx.de>
Date: Mon, 4 Jan 2021 11:20:53 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101
 Thunderbird/78.6.0
MIME-Version: 1.0
In-Reply-To: <777c75df-2848-4960-2bf9-b0cbd16b6a82@gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Language: de-DE
Content-Transfer-Encoding: quoted-printable
Subject: Re: [PHP-DEV] Travis CI migration?
From: cmbecker69@gmx.de ("Christoph M. Becker")

On 03.01.2021 at 03:51, Stanislav Malyshev wrote:

>> The exception being the PHP-7.3 branch, which in security mode.=C2=A0 U=
nless
>> we add GH CI for that branch as well, switching to travis-ci.com seems
>> to be useful.=C2=A0 Maybe we get enough free credits for the relatively=
 rare
>> builds?
>
> I don't think it's possible to migrate only one branch, but if we
> migrate the whole repo and use cron-only builds for upper branches, and
> request OSS credits if we run out of free ones, I think we should be OK.
>
> Given that we have 7.3 still which aren't supported by Azure as I
> understand, I think we should migrate the repo but not invest too much
> into making it work for 8.x, just make it work for more infrequent 7.x
> builds. I'm not sure how credits work there yet, but I think we could
> ask enough of them to have 7.3 and maybe even 7.4 supported and not
> worry too much about the rest.

I meant to switch the repo to travis-ci.com, but to only run PHP-7.3
jobs there (the rest should be migrated to GH actions).  As I understand
it, OSS projects get 10k credits for free, which would allow for about
1000 minutes in a Linux environment.  If we'd only run a single build
per release (with two jobs), that might just be enough till EOL.

Christoph