Hi Nikita, I can't be helpful here at all, because (shamefully) allergic to and bad at windows, and no experience at all with azure.
But I would really like our CI to be restored to a thing that's useful, instead of running two jobs on travis, and more or less nothing on av (most of the time). I remember having CI on travis for many configurations, including the ones we actually develop with. Now we have two configurations and they don't include no-zts-dbg which is what most internal devs are actually running. Anything that restores anything like that former configuration, I'm a huge +1 on ... Anything that means we can run a useful windows CI, even if we can't move any of the jobs that should be on travis over to Azure, I'm still a +1 on ... Anything that means we have a mac build, the same +1 ... Cheers Joe On Sat, 2 Feb 2019 at 19:38, Stanislav Malyshev <smalys...@gmail.com> wrote: > Hi! > > > 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. > > Maybe also get Linux and macOS jobs there? We currently don't have CI > for macOS at all, AFAIK, and having different Linux environment probably > won't hurt either. > > -- > Stas Malyshev > smalys...@gmail.com > > -- > PHP Internals - PHP Runtime Development Mailing List > To unsubscribe, visit: http://www.php.net/unsub.php > >
