Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:112721 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 29681 invoked from network); 3 Jan 2021 03:15:40 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 3 Jan 2021 03:15:40 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id 9F1FB1804DD for ; Sat, 2 Jan 2021 18:51:15 -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.1 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,FREEMAIL_FROM, RCVD_IN_DNSWL_NONE,RCVD_IN_MSPIKE_H3,RCVD_IN_MSPIKE_WL,SPF_HELO_NONE, SPF_PASS autolearn=no autolearn_force=no version=3.4.2 X-Spam-Virus: No X-Envelope-From: Received: from mail-pg1-f174.google.com (mail-pg1-f174.google.com [209.85.215.174]) (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 18:51:14 -0800 (PST) Received: by mail-pg1-f174.google.com with SMTP id i5so16562674pgo.1 for ; Sat, 02 Jan 2021 18:51:14 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=ssZszjg2Zf4+UYEF3eeEis0r0HubJM8Fs4yAoWSZjbs=; b=by7IytGdLnb/iYN7Ungw3Q9lXImzLo+EVVYSsET01647MsdcPL8kRRxA7pfci6y0OB 6pRPW8Zn2mRENPDvPAWF4JYKYYpV8rpLdCOqTuQSzENqKZNZdtAV7Cn01kHqCUYnSgJ6 Oa/dOOD/4Dos7HnMXQQumquebfySjGoQD6Utq4beuU317wQlStTROEzh13HbXJud5VUH r5FyagnJ914xpyvySfD+TPjfOA/AZpuGeaebY63j/sT4N0xIccmxGLglC+uZWhzKJjxF f/NLppsZRSAOqbgo2wmJ0GBXCnALDK+moyOQA+15F5koZRMQ+fLqdRS/CvaXukRonJsX xU/A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=ssZszjg2Zf4+UYEF3eeEis0r0HubJM8Fs4yAoWSZjbs=; b=GCgocT2YYObuIW1ZGABCJHCEavEf/kjjgOvYusgAZ3lCqfEkP0GO2ozMA+39LjkHRx y50KQOJQHT/Db2snblqm02FgRpjqtuk40DsKYVZqJg60YZjx+73OJlxmM/Izypee404u NExDmzCpPnYUQ+j22MoSPuagMrfq90bUrgEhAaWRh9SMSImOnUpwBGcRUiHuMMnn06Tz WOucasQFE+WqXQ+C6IQGlV54M5tsL+BNfpFqol4Q7+B3jfG8y/84uQoim565zQegVYnX jJpK2gV3bDklTiYomdZGuVAivELYjv3ke67Jr+xmsujp/aBgwxK8PnQSyf2JFONDVFvv /YzA== X-Gm-Message-State: AOAM531ALjv88igOoiWmWpkXIqj0sbjuEt4jmAgXYJZl+8+veV5tHzVF 9GzOlZWnwisOSSiPgBUvi+ToZsll43n5 X-Google-Smtp-Source: ABdhPJydzWfMqaPjGJMWi8Cq66ge/4/keV1Y/2KTWdR4vMrQrmV5jwijbmuj392Vrpsew6g7N9uDMw== X-Received: by 2002:a62:7ed2:0:b029:19d:9461:2b30 with SMTP id z201-20020a627ed20000b029019d94612b30mr60697929pfc.14.1609642271617; Sat, 02 Jan 2021 18:51:11 -0800 (PST) Received: from Stas-Mac-3.hsd1.ca.comcast.net ([2601:646:8d80:9130::2a90]) by smtp.gmail.com with ESMTPSA id b12sm50426408pft.114.2021.01.02.18.51.10 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Sat, 02 Jan 2021 18:51:10 -0800 (PST) To: "Christoph M. Becker" , Nikita Popov Cc: PHP Internals References: <86618f8d-7094-1cf7-c017-b7670699a8a3@gmx.de> Message-ID: <777c75df-2848-4960-2bf9-b0cbd16b6a82@gmail.com> Date: Sat, 2 Jan 2021 18:51:09 -0800 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:78.0) Gecko/20100101 Thunderbird/78.6.0 MIME-Version: 1.0 In-Reply-To: <86618f8d-7094-1cf7-c017-b7670699a8a3@gmx.de> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] Travis CI migration? From: smalyshev@gmail.com (Stanislav Malyshev) Hi! > 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. -- Stas Malyshev smalyshev@gmail.com