On 04.01.2021 at 11:20, Christoph M. Becker wrote: > On 03.01.2021 at 03:51, Stanislav Malyshev wrote: > >>> 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? >> >> 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.
Any news here? Tomorrow PHP 7.3.27 will be tagged, likely without any Travis-CI build to confirm that it's not broken on Linux. Regards, Christoph -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: https://www.php.net/unsub.php
