Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:112323
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="=_611d1e260d6b677143688e63d137303f"
Date: Mon, 30 Nov 2020 17:40:26 +0100
To: PHP internals <internals@lists.php.net>
In-Reply-To: <CAF+90c-QBOBwnvONOe2naeynWi4p4fVMkKVC3CdV0GbrFo=5Lg@mail.gmail.com>
References: <8caf76f8d4374cde64343132fa8f2ba1d0debe7a5bc4a05f346f67fdabe499f7@mahalux.com>
 <CAF+90c-QBOBwnvONOe2naeynWi4p4fVMkKVC3CdV0GbrFo=5Lg@mail.gmail.com>
Message-ID: <66732f052246d4ead86e4c9009c777bd8bce4d606774b3219abd06fae3aeec19@mahalux.com>
Subject: Re: [PHP-DEV] Nightly builds
From: vorismi3@fel.cvut.cz (=?UTF-8?Q?Michael_Vo=C5=99=C3=AD=C5=A1ek_-_=C4=8CVUT_FEL?=)

--=_611d1e260d6b677143688e63d137303f
Content-Transfer-Encoding: 8bit
Content-Type: text/plain; charset=UTF-8; format=flowed

Thanks - via api - externally - it should be possible -
https://dev.azure.com/phpazuredevops/PHP/_apis/pipelines/1/runs?orderBy=date%20desc&top=1000&api-version=6.0-preview.1

> The only thing we could produce are Docker images

Yes, building nightly Docker image is the intended usecase and I may
help with it. 

Is it ok to introduce "master-passing" branch in official repo, that
will be updated at the very end by CI job triggered by push to "master"
branch? 

With kind regards / Mit freundlichen Grüßen / S přátelským pozdravem,

Michael Voříšek
ČVUT FEL

On 30 Nov 2020 16:07, Nikita Popov wrote:

> On Sat, Nov 28, 2020 at 12:44 PM Michael Voříšek - ČVUT FEL <vorismi3@fel.cvut.cz> wrote: 
> 
>> Hi internals, 
>> 
>> currently, as far as I know, php does not have nightly builds. 
>> 
>> By nighly I means builds/releases that are tested to pass all CI tests.
>> This is not the case with master branch, as that branch can be failing
>> tests. 
>> 
>> I propose to introduce "nightly" branch that will point to "the latest
>> master head that passed all CI tests". To limit cache misses on
>> dependent projects/builds (like docker images), I propose to update
>> "nightly" branch no more than once per day. 
>> 
>> This will allow php comunity reliable testing of new language/engine
>> features much more sooned until next php minor version has an alpha
>> release. 
>> 
>> What is your opinion on this and is here someone that can implement it? 
>> 
>> With kind regards / Mit freundlichen Grüßen / S přátelským pozdravem,
>> 
>> Michael Voříšek
>> ČVUT FEL
> 
> Hey Michael, 
> 
> It's not entirely clear to me what you're asking for here. Is it about producing actual build artifacts? It's not possible to produce useful build artifacts for PHP, because the number of dynamically linked libraries will make them non-portable. The only thing we could produce are Docker images -- and other people already provide that service. 
> 
> If what you want is to just determine whether a certain commit is a good base for a nightly build, I'd suggest finding our how to query scheduled builds on Azure pipelines (builds like these: https://dev.azure.com/phpazuredevops/PHP/_build/results?buildId=13228&view=results) and check whether they pass. Note though that these will commonly fail even on good commits, because they run tests in more than 60 different configurations, and as such spurious failures are common. 
> 
> Nikita
--=_611d1e260d6b677143688e63d137303f--