Difference between revisions of "SAC Shared Building Services"
Jump to navigation
Jump to search
| Line 22: | Line 22: | ||
In order to get to that point we need to research the following | 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 a better way to how these keys should be shared across packagers. | |
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
Revision as of 12:23, 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 done by one individual does Mac 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 a better way to how these keys should be shared across packagers.