> On Apr 16, 2020, at 7:46 PM, Mateusz Loskot <mate...@loskot.net> wrote: > > On Fri, 17 Apr 2020 at 01:45, Mike Taves <mwto...@gmail.com> wrote: >> >> It seems that many projects have shifted from AppVeyor to AZP for >> performance benefits. > > Or GitHub Actions, which is an incarnation of AzP.
Having done both GitHub Actions and AzP, I think Actions has more convenient expressiveness of job flow, a big win of integration with GitHub's API, and large directory of user-contributed actions. We migrated PDAL to AzP last summer after our experience at the OSGeo Code Sprint in Minneapolis with AzP on the gdal.org <http://gdal.org/> refactor. A big benefit was to simply have *one* CI platform instead of two or three. It was also wall-time faster, more concurrent, and most importantly had no cost to get better performance for open source projects (you need to pay for that from Travis or AppVeyor, which the PDAL project had done). GitHub Actions takes it even a step further, and it would be my choice for GDAL if someone has the capacity to invest the time to bring it forward. Howard
_______________________________________________ gdal-dev mailing list gdal-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/gdal-dev
