Difference between revisions of "SAC Shared Building Services"

From OSGeo
Jump to navigation Jump to search
Line 14: Line 14:
 
On Mac Side
 
On Mac Side
 
* QGIS builds there own
 
* QGIS builds there own
* bottle.download.osgeo.org done by one individual does Mac packages for a bunch of OSGeo projects.
+
* bottle.download.osgeo.org Homebrew binary packages for a bunch of OSGeo projects
  
  

Revision as of 11:25, 6 June 2020

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

  1. Who are the interested parties and those willing to do the work of packaging?
  2. What options do we have for supporting the need
  • Windows cloud hosters - Hetzer, Atlantic.net, Microsoft Azure, other hosters
  • CI:
  1. https://circleci.com/build-environments/ (supports Windows and Mac)
  2. https://www.appveyor.com/ (supports Windows and Mac)
  3. 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?