A currently unstable CI?

Mark Anderson mark at macports.org
Fri Apr 3 21:43:32 UTC 2020

Considering that XCode 11.4 will only run on 10.15, we should probably do
that as soon as possible. We also might want to ditch travis. I barely pay
attention to it anymore. Does anyone else?

We also might want to consider github actions, which run on azure and can
link to what we do on Github more easily.


On Fri, Apr 3, 2020 at 5:21 AM Ryan Schmidt <ryandesign at macports.org> wrote:

> > On Apr 3, 2020, at 04:18, Christopher Jones wrote:
> >
> >
> >> No action necessary. Both builds failed because "Could not resolve
> host". Unfortunately we see these types of network errors rather frequently
> from Travis CI and we do not know how to get the Travis people to resolve
> it. It does not appear to be a very good service. We also use the Azure
> Pipelines service which as far as I know has not had these problems. Maybe
> we should stop using the Travis CI service altogether.
> >
> > Azure is more stable, but is currently limited in that it only seems to
> support 10.14 builds. 10.13 was recently removed, and support for 10.15 is
> missing. So if where where to use only azure we would be quite limited in
> terms of OS testing.
> True, but 10.15 is missing because we have failed to produce a 10.15
> version of MacPorts base for it to use. Short term, we should do that. Long
> term, we should fix it so that the CI systems can use the standard version
> of MacPorts base and don't need custom versions.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macports.org/pipermail/macports-dev/attachments/20200403/1491ee1e/attachment-0001.html>

More information about the macports-dev mailing list