Re: AppVeyor timeouts -- Migrate to Azure Pipelines?
| From: | Nikita Popov | Date: | Sat, 02 Feb 2019 13:31:31 +0000 |
| Subject: | Re: AppVeyor timeouts -- Migrate to Azure Pipelines? | ||
| References: | 1 2 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-104022@lists.php.net to get a copy of this message | ||
On Sat, Feb 2, 2019 at 2:06 PM Christoph M. Becker <cmbecker69@gmx.de>
wrote:
> On 02.02.2019 at 13:18, Nikita Popov wrote:
>
> > Since some time ago (not sure how long) our AppVeyor builds have been
> > timing out more often than not, to the point that I've started ignoring
> > failing AppVeyor builds entirely.
>
> Indeed, this is particularly annoying for RMs.
>
> > I just learned about the Azure Pipelines (
> >
> > https://azure.microsoft.com/en-us/services/devops/pipelines/)
> > offering,
> > which offers open source projects 10 parallel builds with unlimited
> > minutes. Assuming there's no other catch here, it might be worthwhile to
> > migrate our Windows CI jobs to Azure Pipelines.
>
> An alternative to consider is using Travis for Windows CI[1], too.
>
It's an option, but I think we're generally better off using multiple CI
platforms to increase the number of parallel builds we get.
Next to the builds we already have, I think it would be very good to also
have a macos builder (this is supported by both Travis and Azure Pipelines,
but needs someone familiar with the platform to set things up) and a 32-bit
builder (probably a -m32 build on x86_64 Linux). That would bring us to a
total of six builds, which would probably make the Travis queue somewhat
slow if we used it exclusively.
Nikita