This should solve continuous integration issues #119 and #120.
R CMD check workflows was splitted as suggested in #119.
R-CMD-check is the regular check. Differences with before:
no longer run on r-devel
no longer use ubuntugis-unstable PPA
no longer build R packages from source (CRAN), but use binaries from RSPM (lagged CRAN binaries)
use more liberal caching (allowing to use same cache for 7 days max; new branches depend on cache availability in their base branch)
only run on push (all branches)
macOS: pre-install udunits and gdal (unless version provided by homebrew is already present on machine)
R-CMD-check-latest keeps old approach (CRAN+PPA+r-devel+r-release+strict cache), with the above macOS patch added. Only run at more critical events:
PR to master
push to dev*
scheduled monthly
site-devel & site-deploy workflows were updated to no longer use ubuntugis-unstable PPA and no longer build R packages from source (CRAN), but use binaries from RSPM (lagged CRAN binaries). However uses strict caching in order to always build website using latest R packages from RSPM.
This should solve continuous integration issues #119 and #120.
R-CMD-checkis the regular check. Differences with before:udunitsandgdal(unless version provided by homebrew is already present on machine)R-CMD-check-latestkeeps old approach (CRAN+PPA+r-devel+r-release+strict cache), with the above macOS patch added. Only run at more critical events:masterdev*site-devel&site-deployworkflows were updated to no longer use ubuntugis-unstable PPA and no longer build R packages from source (CRAN), but use binaries from RSPM (lagged CRAN binaries). However uses strict caching in order to always build website using latest R packages from RSPM.