Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:112718 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 15554 invoked from network); 2 Jan 2021 23:42:13 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 2 Jan 2021 23:42:13 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id 057C71804DC for ; Sat, 2 Jan 2021 15:17:47 -0800 (PST) X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on php-smtp4.php.net X-Spam-Level: X-Spam-Status: No, score=-2.4 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,FREEMAIL_ENVFROM_END_DIGIT,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW, RCVD_IN_MSPIKE_H2,SPF_HELO_NONE,SPF_PASS autolearn=no autolearn_force=no version=3.4.2 X-Spam-Virus: No X-Envelope-From: Received: from mout.gmx.net (mout.gmx.net [212.227.17.21]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by php-smtp4.php.net (Postfix) with ESMTPS for ; Sat, 2 Jan 2021 15:17:45 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gmx.net; s=badeba3b8450; t=1609629464; bh=OmnGAc/N4lzirToUXulTH3BP82IEgN6NgpuOe5KVXbQ=; h=X-UI-Sender-Class:Subject:To:Cc:References:From:Date:In-Reply-To; b=bB+8167oTmPrqlx1Tts760schx52PoqFSJK5RyQxDeuumbbV6/AWKRqy+Be0whBX9 NoUVEZnP3Ul62Fl1zOR3EelWg5gCf3PW7ngTFhOTrZQkXROA6myptQYifjtfdJwNvQ 0rupX8Z5G+X6afdNOI0NUMX1Ln0AK1ip8t8MzzAM= X-UI-Sender-Class: 01bb95c1-4bf8-414a-932a-4f6e2808ef9c Received: from [192.168.2.130] ([79.222.36.9]) by mail.gmx.com (mrgmx104 [212.227.17.168]) with ESMTPSA (Nemesis) id 1N2mBQ-1jzI7v3alI-0133YX; Sun, 03 Jan 2021 00:17:43 +0100 To: Nikita Popov , Stanislav Malyshev Cc: PHP Internals References: Message-ID: <86618f8d-7094-1cf7-c017-b7670699a8a3@gmx.de> Date: Sun, 3 Jan 2021 00:17:43 +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: Content-Type: text/plain; charset=utf-8 Content-Language: de-DE Content-Transfer-Encoding: quoted-printable X-Provags-ID: V03:K1:jVyZRdtn4+f32uL/33JVOHwGBU1iSH7X3m0jKwfzXopHFFtp2Mo lHtiBSvkw+iCucgSeR0NxsYo95o/eCMaQpUoiMq3Ghjij+D4Tnc7hJNXNAOrybaY7CgKzqb R+2t6yxIJyerXdhEUBysCLa+NN2kGEOT/zclQsWYVBvlAeqCfLCwAd3wyesXZCpGThZ+fLP ZVsWc2MT5ctPxSvod/wew== X-UI-Out-Filterresults: notjunk:1;V03:K0:SUeV4XmANak=:IVmULKPDDqRaLzlBm1cYBW +3wZ0ILarh9meuj7yrK74sk7Bc41Z6xtBWRV/xxgn4Le+UZFbt+53xMeaENmcOXhEhZE5JPXL WbwfUzCMcuLDNhCgVbN00DGIqyejFsgpGp1IO07fqv/f4VdoyTDA+Ajf4oBwaAulQZ1PalV0h bMUYs3BLBi4i0uGXw8bCVoRQRgEAdHamg+6Zgv7Rk22wIEflZ0Zc4EBhZQoKSAaGHRBUUwd14 KX2ZRYE8DHziVkXnNZk2kDq9o21nRo7ISG3Y1r/prf2pUAsO7xverWT5c8hgJ2JnxCyfZB4b+ BAfPX3+XsqRVEKc1GYuhvc/TnUkFp4a2Y2LVlkXVK1mR5WN6Lc3j8fH4JaYLr1p3jLFr3dJI6 r3c354PBm/7392K6IN7UlIY6WsdLXHSunC/kxPcUukPWcn/GHurMRi6NuY2CGYGg6WHbEMKLa kt65z03fA2vAOcJr1Zbo/By0u/ocR8hUE2OLTdiQ36T/eql3sjpnSqqMfV6pEv2T35FI6xWvd 5LFbIakhC3iU0Q28TBYbwfXuQC2ZXLY1OInGcFreZoWgYamxq6gSE2SsCQBZfeO01+g/821OR fMWL67u6cnqE0RVbo79nbf34CVWdxfv5lk5h10yTgWn+3qw7xt20FtG9eokEGAW4QabiU2/3G 2ArJog7iapSaHi2PSC6HlOwOtjuKanpodxTb6hnP1kuJYZCPoN9EUrEf9vrkJUIcfzZcgafT8 H6ngoAPhLdS3qNO9cm8kgS1gO6s7DYsuvv2MKA9o8nYE5/3vo9Fw/soMgxqentLpUaGV7dpMc vGsrGxL+2h4ERI/jE5rhGL65JG76+hsKwSgXw3hL0Oow/V2doGC5BlefybMA+ojbEmJ0X7+tz JrWiK04OLBUYFQN4hlBg== Subject: Re: [PHP-DEV] Travis CI migration? From: cmbecker69@gmx.de ("Christoph M. Becker") On 02.01.2021 at 22:43, Nikita Popov wrote: > On Sat, Jan 2, 2021 at 6:51 AM Stanislav Malyshev > 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 fo= r >> more information. >> >> As far as I know, our repo is still not migrated. Anybody looked into i= t? >> >> 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 u= se > AppVeyor for Windows testing and Azure Pipelines for everything else. Th= e > only thing Travis is still used for is a daily cron job that tests PHP o= n > "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