Migrate Travis builds

Travis is adjusting is payment tiers and a number of our free builds is going to shut off in early December (we cannot predict when).

We need volunteers to migrate travis builds, this can be done with a pull-request and does not require a great deal of commit access.

Travis Builds

What do we need to migrate:

• GeoServer → java 8, java 11, and QA builds

  Linux environment available in github actions so this can be migrated: https://github.com/geoserver/geoserver/pull/4581

• GeoTools → java 8, java 11, and QA builds

  Linux environment available in github actions so this can be migrated: https://github.com/geotools/geotools/pull/3236

  • backport to 24.x: https://github.com/geotools/geotools/pull/3242
  • backport to 23.x: https://github.com/geotools/geotools/pull/3241

• MS SQL Server master build: https://github.com/geotools/geotools/pull/3238

  • backport to 24.x: https://github.com/geotools/geotools/pull/3242
  • backport to 23.x: https://github.com/geotools/geotools/pull/3241

• Oracle master build: https://github.com/geotools/geotools/pull/3239

  • backport to 24.x: https://github.com/geotools/geotools/pull/3242
  • Travis does not run Oracle online tests for 23.x

• MySQL 5 and 8 master builds: https://github.com/geotools/geotools/pull/3237

  • backport to 24.x: https://github.com/geotools/geotools/pull/3242
  • Travis does not run MySQL online tests for 23.x

• GeoServer documentation build

  requires sphinx, so “not simple” https://github.com/geoserver/geoserver/pull/4581

• GeoTools documentation build

  Current build likely useless, as sphinx not installed

• GeoServer package build

  Should be “simple” to migrate as linux environment available https://github.com/geoserver/geoserver/pull/4581

• GeoWebCache builds

Options

• Pay Travis: We have budget, we could look at value for paying

• github Actions:

  Not useful for all database services, as an example postgis tests run against well-known service “postgis service”,is there an equivalent for Oracle, sqlserver and mysql 5/8?

  Also worried about using only one tool, and everyone is switching to them.

  Examples: GDAL migrated to GitHub Actions with https://github.com/OSGeo/gdal/pull/3194 and https://github.com/OSGeo/gdal/pull/3198

• Jenkins: build.geosever.org.

  The approach of adding a jenkins pipeline build to repository is important to allow anyone to work on this

• Circle CI, we have had mixed success with the Windows build, and there is a time limit (think 50 minutes). GeoNode is using CircleCI. Apparently we’d get 4 concurrent builds for Linux.

• Azure Pipelines is also an option.