[GRASS-dev] OSGeo SAC Shared Building Services - windows and mac builds

fyi from a recent SAC discussion:

https://wiki.osgeo.org/wiki/SAC_Shared_Building_Services

-----
This page is to capture all the needs for Windows and Mac binary building

All OSGeo Projects have a need for building binaries for Windows and Mac OSX. Since these platforms are proprietary and need extra licensing, there is a bit more needed to satisfy than for Linux systems.

Right now each project kind of does their own thing and no position to easily share.

Current State

    OSGeo4W - builds QGIS and Grass binaries, largely funded by QGIS project at moment
    GeoServer was building binaries for windows - using their windows jenkins slavebot, but lost that
    PostGIS builds windows binaries for PostGIS and pgRouting and other PostGIS related extensions (ogr_fdw, pgpointcloud) using their windows jenkins bot

On Mac Side

    QGIS builds there own
    bottle.download.osgeo.org Homebrew binary packages for a bunch of OSGeo projects

Future State

Ideally have a set of resources shared by current Windows/Mac Builders. Costs funded via SAC budget. In order to get to that point we need to research the following

    Who are the interested parties and those willing to do the work of packaging?
    What options do we have for supporting the need

    Windows cloud hosters - Hetzer, Atlantic.net, Microsoft Azure, other hosters
    CI:

    https://circleci.com/build-environments/ (supports Windows and Mac)
    https://www.appveyor.com/ (supports Windows and Mac)
    GitHub package feature?

    Distribution - download.osgeo.org, repo.osgeo.org (we could conceivable do windows/mac distribution here and replicate this to a cloud offering for redundancy)
    Key Signing - OSGeo currently pays for and we'll need to discuss how these keys are shared

    How will we grant access to these resources?

-----

kind regards
Helmut

Hi,

Azure pipelines provides CI with Windows, MacOSX and Linux environments, with up to 10 parallel jobs for open-source projects (https://azure.microsoft.com/en-us/services/devops/pipelines/).
It might be a good option to set up only one CI server for all the builds.

Cheers,
Laurent

Le dim. 7 juin 2020 à 03:39, Helmut Kudrnovsky <hellik@web.de> a écrit :

fyi from a recent SAC discussion:

https://wiki.osgeo.org/wiki/SAC_Shared_Building_Services


This page is to capture all the needs for Windows and Mac binary building

All OSGeo Projects have a need for building binaries for Windows and Mac OSX. Since these platforms are proprietary and need extra licensing, there is a bit more needed to satisfy than for Linux systems.

Right now each project kind of does their own thing and no position to easily share.

Current State

OSGeo4W - builds QGIS and Grass binaries, largely funded by QGIS project at moment
GeoServer was building binaries for windows - using their windows jenkins slavebot, but lost that
PostGIS builds windows binaries for PostGIS and pgRouting and other PostGIS related extensions (ogr_fdw, pgpointcloud) using their windows jenkins bot

On Mac Side

QGIS builds there own
bottle.download.osgeo.org Homebrew binary packages for a bunch of OSGeo projects

Future State

Ideally have a set of resources shared by current Windows/Mac Builders. Costs funded via SAC budget. In order to get to that point we need to research the following

Who are the interested parties and those willing to do the work of packaging?
What options do we have for supporting the need

Windows cloud hosters - Hetzer, Atlantic.net, Microsoft Azure, other hosters
CI:

https://circleci.com/build-environments/ (supports Windows and Mac)
https://www.appveyor.com/ (supports Windows and Mac)
GitHub package feature?

Distribution - download.osgeo.org, repo.osgeo.org (we could conceivable do windows/mac distribution here and replicate this to a cloud offering for redundancy)
Key Signing - OSGeo currently pays for and we’ll need to discuss how these keys are shared

How will we grant access to these resources?


kind regards
Helmut


grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev